Search the Community
Showing results for tags 'new webapp'.
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. June 19th, 2019 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.14.0 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 2.5.0 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: New WebApp: the Domotz Pro WebApp has been completely redesigned and new endpoints have been created to accommodate the changes. The user interface have been completely redesigned to make it more friendly and easier to find the features that users are looking for. The major benefits brought by the new WebApp can be summarized in the following items: New Navigation Bar which highlights the Domotz Agent selected Direct Links to the main functionalities available in the Portal for Account Administration purposes Device List direct access to functionalities such as grouping, sorting, searching, filtering, multi-select and other features Device Details direct access to the latest events, remote connections and logging Single Agent Dashboard restructure New Mobile App: a new Mobile App to align with the changes performed on the Web version of the Domotz Pro App. A new Logo and splash-page will welcome the users Cisco TelePresence SX20 Support: a new type of devices have been added to the list of drivers available in Domotz. The Cisco SX20 (and similar) is recognized as a Unified Communication device. After configuring credentials, Domotz Pro agent will be able to software reboot the device and extract information about the codec (people presence, people count, conference info, call info, camera devices and more). Data will be stored for reporting and analytical purposes Improvements: Public API - Read and Configure Device authorization status: it is now possible to retrieve the authorization status of devices or set device credentials (for specific driver support) Public API - Power Action on devices: it is now possible to retrieve power capabilities on devices and trigger power and reboot controls (e.g. devices connected to PDU outlets or PoE switch interfaces, or devices offering software reboot capabilities) Email notification on IP Changes: email notification on device IP changes has been enriched with all the information already available in similar notifications (agent name, site owner, device name, vendor, model, etc) Niveo PoE Switches: it is now possible to control PoE status of Niveo PoE switches Remote Connections - Traffic consumption: the traffic consumed on a specific Domotz Agent for the month is now reported in the Connection tab for each device of that Agent (so that users know exactly how much traffic can still be used on that specific plan for the month). Fix: Team Member Eyes alerts (TCP and SNMP) were not correctly retrieved and configured Ruckus Un-leashed Controller driver support for multi-AP configuration have been fixed SnapAV Wattbox driver support have been fixed Hi-Flying power switch control have been fixed Known limitations: Crestron PDU driver is triggered only when CTP port is enabled on the Crestron PDU 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 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