Search the Community
Showing results for tags 'reports'.
Found 3 results
Hello, I am evaluating using the Domotz Pro and it seems to fit the bill in many aspects. Admittedly I do not have one yet, but it is on order as such I will have more hands-on comments coming. But in the evaluation "to buy or not to buy" I am coming short on the following... I have scoured the domotz.com website and done general internet searches. So if the information is available, apologies for not finding it, but at the same time... it is thus hard to find and maybe should be made more accessible. I have also tried the demo site, to see if I could get answers out of it, but the “demo” limitations do not permit me things like… seeing a report (email disabled) I’m looking for a sample report…. What is the report that you can have emailed to you at the end of the month? In what format does it come? Can a template be applied? How in depth is it? Is there an Installer version and customer version? Does the report outline device performance over time? Does the report outline device usage over time? Does the report outline specific functions usage (extracted from SNMP calls or alike) On the features page (https://www.domotz.com/remote-network-monitoring-features/) it talks about Network Mapping Please explain? What kind of network mapping? I see no network Topology page.. does it exist? Is there a visual layout of the network? A Map of devices connected per switch? Switch / Router / Firewall / WLAN layouts? Trunk size / performance? VLANs visualisations? Am I even understanding what the feature Network Mapping is about? (In your vision) Under Alerts it mentions - Intruder/New Device Is this outlined in the report? Does an alert get send when a new device tries to gain access? Does this alert allow you to respond with a Allow/Disallow function? Are there login alert/intrusion protection into the Domotz box itself? Is there a summary/log analysis for repeated attempts of a device to connect over period? Is there a repeat offender function for blacklisting needs (note.. repeat offenders does not have to be a user willingly trying to ‘get in’ but could be a device simply misbehaving.. having a bug.. or even a virus!!) Under Network Diagnostics you mention - Ethernet Port Monitoring Please elaborate!? Will the Domotz Agent identify which port on a switch devices are connected to? How does this get represented? (Network map? Report? On the device page?) If (for switch reason) it cannot be retrieved, can the information be added manually? On a point of personal feedback.. I did visit you at the ISE2018 on the hope that a conversation could be struck up and I could get answers to some of my doubts, but I seemed to get a little of a cold shoulder from you guys. I clearly understand that an event as such is tiring, and I came relatively late in the day, it’s just a shame to have missed an opportunity there. Hope you can clarify the issues outlined above, or at least give indication where you are on the roadmap to achieve this? Thank you, Tim.
Hello all, I really like the ability to generate basic reports with Domotz and I think with a few tweeks they could be made even better. I'd like to offer some suggestions and would appreciate feedback from others if you think these features may benefit you or if you think they would be a bad idea and why. Automated reports that can be set to automatically email at a specific frequency/on a specific day It would be nice if the WAN performance line chart in the report could display internet disconnects/drops as a red dip on the graph to make them easier to identify Important device up/down history Ability to edit agent addresses (probably more of an Domotz portal feature) but it's on the report Report naming - Instead of just naming the generated report "report" when emailed, why can't Domotz change it so that the file name is something like [Agent Name]-Report-YYYYMMDD? Downloading multiple reports at once becomes confusing when all of them are named "report," and for customers that may have multiple sites, it would make it easier for them to distinguish which report goes to which property Speaking of customers with multiple properties/agents, it would be nice if we could group agents and generate one report with all the information for each agent site in a single report The ability to set custom dates for the reports would be nice (though if report generation were automated then this wouldn't be necessary). If I want to send my customer a report of the past 30 days, I need to make sure the report is generated exactly at the end of the 30 days report cycle. This is an unnecessarily burdensome. Even if you limit the report length to 30 days, it would still be nice to be able to set a start/end date and generate something 30 days from/before that date. These are just some of the things I've noticed in the very short time I've been using Domotz. Keep up the good work!
This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud APIs, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. 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.2.4 Domotz Agent: check on Domotz Portal under the license tab. Latest version as per today is 1.1.5 Domotz Pro WebApp is already updated to the latest version. July 28th, 2016 Domotz Pro App: 1.2.4 - Domotz Agent: 1.1.5 New Features: · Wake-on-LAN support · Automatic Wake-on-LAN Support · Monthly Agent report generation (Beta) · Zigbee Diagnostics via Control 4 (Beta). Only available for users having 5+ licences · TUI tool to assist with network interface configuration - User Guide available upon request · Reboot button on Device Manager · Field Operator user type: Team masters can now create this new type of user. By default these users can only access the Agents they install. Team masters can then add/remove visibility for specific Agents. · ‘Zone’ field added to Device Details Improvements and fixes: · Improved speed test execution and reliability · Other minor fixes