Search the Community
Showing results for tags 'auto-discovery'.
This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. May 8th, 2018 In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 1.7.5 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as per today is 1.9.1 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.6.7 Domotz Pro WebApp and Portal are already updated to the latest version What's new: App and WebApp in Demo Mode: it is now possible to use the Domotz Pro App in Demo Mode (or via Web App) in order to understand and show all the features available through Domotz. The Demo Mode also works when the mobile is in offline mode Disable Device Auto Discovery: the Device Auto Discovery performs a network scanning every 30 seconds. It is now possible to disable the automatic discovery of new devices, in order to allow the monitoring system to monitor only the existing devices at a certain date Domotz Users can be invited on a FingBox: all the Domotz Pro users can be invited by a FingBox user to monitor their network. A new Agent is created in the Domotz Pro list of agents and it performs Remote Monitoring and Managing activities by leveraging the FingBox hardware Domotz on Luxul Router - Epic 5: Domotz Agent is now available on the Luxul Router - Epic 5 series SNMP Templates: for some devices, OiD are suggested to the user during an SNMP sensor setup CyberSecurity Features (Beta on request): TCP Open Ports scanner (WAN), Default Credentials Scanner and UPNP Port Forwarding Scanner (Router/Modem security issue) CleanUp Agent Data: user can now clean-up completely the data of an Agent, and start scanning a new network (without requiring the re-configuration of the Agent). This now allows users to Configure the Agent in a network, then ship or relocate on a different network, and start scanning from scratch Denon and Marantz integration: new 2018 models (both Denon and Marantz) can now be managed remotely through an intuitive interface available in the Domotz Pro App and WebApp. Network and Device reboots, Zone Info and controls on the Zones, System Info, Streaming Services list and more is now available Blacklist of devices: some Devices may have problems when scanned with network monitoring tools. Although not common, this is typically related to scanned devices that have legacy firmware. It is now possible to blacklist a Device from being monitored by Domotz Pro agent Improvements: Device Rediscovery: it is now possible to delete an online device, to allow the Domotz Pro service to re-discover it. This is very useful if the user want to clean-up all the previously discovered data for a specific device Power activity logs: Reboot, on/off and software restart activites of supported devices (through PDUs, PoE and supported drivers) are now tracked and listed into the "Reports & Logging" tile Ruckus - new firmware support: Ruckus Zone Director with firmware 10.1+ is now supported with Advanced Plan Remote Connections on Public Hostname/IP: it is now possible to create Remote Connections/TCP Tunnel to Public Hostname/IP using the Domotz Agent (Advanced Plan) TCP Tunnel Endpoints: When creating an Open TCP Tunnel, random endpoints (host:port) can be copied directly from the App/WebApp Dummy Device removal: it is now possible to remove Dummy devices Important Devices can be blocked: it is now possible to configure an Important Device as "blockable" by an end-customer (through Violet - Customer Facing App) See Blocked Devices: Domotz Pro user can now see if a device has been blocked or if it has a scheduled block configured in Violet - Customer Facing App Serial Number: some devices are now reporting the Serial Number directly into Domotz Pro FIX: Control4 firmware version was not retrieved for some newer versions Dummy Devices could not be controlled through Violet Long Community String (SNMP) could not be edited from the Mobile App Known limitations: Eyes configured for deleted devices affect the total counting of Eyes Devices with multiple network interfaces (multiple MAC address) can't be merged into single device Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring) Static IP address on the Domotz Box cannot be configured before configuring the Agent External monitoring of public and private subnets might not work properly on Raspberry Pi installations Multiple Devices logically connected to a Managed Switch Port: in case of WiFi AP connected to a switch port, the information is not available at the WiFi AP info