Search the Community

Agent re-installed in QNAP (after long time "dormant"). Retrieved old data through account, but not updated as expected.... wrong mixed IP/MAC devices. Even if I disconnect the wrongful devices, delete and plug back again... it comes back wrong (like having "bad memory"). Everything identified correctly through Fing, though... but not through Domotz. It's there a way to force the agent to re-scan the whole network, or reset? Thanks, Xant

It appears that the Raspberry Pi image of the Domotz Agent also works on the Beagle Bone Black according this this post http://community.domotz.com/index.php?/topic/92-agent-for-linux-based-routers-android/&do=findComment&comment=314 Note that this is unsupported from our side, but it adds another potential hardware platform to run the Domotz Agent on.

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

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.0 (will be available in 24-36 hours on Apple Store) Domotz Agent: check on Domotz Portal under the license tab. Latest version as per today is 1.1.2 Domotz Pro WebApp is already updated to the latest version. June 23rd, 2016 Domotz Pro App: 1.1.9 - Domotz Agent: 1.1.2 New Features: · Domotz Pi on Store has been upgraded, we are now shipping Raspberry Pi 3 devices · Device details: new Audio Player type added · Device details: display discovered 8000 and 8080 ports · Improved User Experience on account info view · Agent reset procedure now unbinds licence from MAC address; the licence can be reused with a different device · Added support for Tripp-Lite PDUMV20NET PDU · Added support for Edimax SP-2101 Smart Plug · Cisco SG and Catalyst switches now supported · Improved Remote Connect support (devices using IP within WSS - e.g. Ubiquiti and TP-Link routers) Bugfixes: · Page scrolling issues on some desktop browsers · Handling status changes on devices with dual-IP address · Counter for device up/down events displaying improper values · Glitch editing device detail on iOS · PoE switch displayed wrong outlet number on associated device detail · Panamax outlet custom user info disappearing · Minor device discovery logic improvements · Other minor fixes

The android app tells me: "ONLINE, but some services are down. Please restart your local agent" I have restarted twice with no luck. It seems like the Network Health Analysis tools does not work. Does anyone know what could be wrong?

I have been using finbox installed on my pc, and noticed the new partnership with Domotz. I liked that fact that I could install the client on my NAS (Qnap TS-251 Intel based). The domontz app didn't show up in the app store, so installed it manually which worked fine. The problem I'm having is that it is very very slow detecting all the devices (doubt that it's working correctly). After 2 hours it detected 2 devices, now after 4 hours it has detected 4 of out 25+ devices. Rebooted the QNAP, didn't make a difference. Anybody a suggestion to speed this up?

I know this is a fairly low-priority item but it would be useful for those of us with RasPis (and maybe others in structure). The ability to get the Domotz agent to login without a web browser by allowing a command-line submission of email address and password. We already are doing a number of steps to install (or upgrade) the agent in command line (regardless of whether it is headless or not). This would allow a person to just continue following steps (easily copied from the Domotz Portal's instructions) to complete the entire process. No other windows or browser needed. This would allow the steps to be more easily automated. Related to this, if the Domotz agent can be downloaded the same every time (example, in the future you could always go to: wget https://portal.domotz.com/download/agent_packages/latest/raspi.deb) the entire process could be a single script and would never change IF someone wants the latest. Such a structure works for any of the releases (with different end file names) and could readily be altered for future betas that you might not want accessible to everyone (by making it .../agent_packages/betas/... and having user/password restrictions based on portal access). Then someone could actually LOGIN to get the beta software also easily added to the wget command.

Hi. I have had a couple of times when the agent hasn't been reachable from the web-portal. It shows as offline in the iOS app and portal. The Pi itself is still alive in this instance, but a reboot is required to bring the agent back online. (Perhaps there's a console command that would do the same?). Where should I look for logs to troubleshoot why this is happening? Thanks

A new version of Agent and App have been released. Please: • Download the app from the Apple Store or Google Play. • Download and install the agent from the Domotz portal. App - Release notes: • Connection status history is now available under the Network panel. • Multiple VLANs can now be properly monitored. Note: VLAN support is only supported on the Raspberry Pi version of the Agent. This thread in the Raspberry Pi sub-forum explains how to configure VLAN support. • Devices that support SNMP will now include detailed information about their network interfaces and status • The list of available agents can now be refreshed with pull-to-refresh on the side-menu. • Visual notifications when new agents are available. • General bug fixes and performance improvements Agent - Release notes: • Multiple VLANs can now be properly monitored. Note: VLAN support is only supported on the Raspberry Pi version of the Agent. This thread in the Raspberry Pi sub-forum explains how to configure VLAN support. • Current connection status displayed on agent info page • General bug fixes and performance improvements VLAN support is fully implemented in the latest Domotz Agent across all platforms, but due to some platforms lacking native VLAN support, or a simple way of enabling it, Domotz is not officially supporting it on any other platform than the Raspberry Pi for the time being.

Smartthings would tell me I was down, piper would tell me I was down. domotz was silent.

Agent is running on a RaspberryPi2 and accessed using Firefox running on Windows 10. Cursor hovering over the agent's menu is text insert bar rather than a pointer Agent Info could include platform information (hardware version, OS version, IP address) as well as agent version Network Info shows the platforms network information; if router settings have been changed, this information is not updated (until ...) Speed Test using PREGINET shows a speed of 3.7 Mbps (on a Gigabit connection) I suggest to embed a link in the Domotz icon to www.domotz.com or Domotz support page

I swapped the router, but the agent still thinks it is the old router and shows the wrong name and MAC address. I assume the agent pings the IP address of the gateway, but does not check the MAC address. I guess this is true for all devices.

We have a report that the Udoo Neo works with the Domotz agent - http://community.domotz.com/index.php?/topic/103-easy-way-to-transfer-license/&do=findComment&comment=327 Note that this is not an officially supported platform, but as long as you run a Debian based OS, it seems to be working.

It looks like the Marvell Armada 375 package will work on the Annapurna Labs based models from Netgear. So far we've only tested it on the RN204, but it seems to be working just fine. This is unsupported, but if you have a recent ReadyNAS, please give it a go and report back here.

The Domotz Agent has the following system requirements. If your hardware doesn’t meet or exceed them, the Domotz Agent will most likely not work with your hardware. QNAP QTS 4.3 or later. Minimum 512MB of RAM Any x86/x64 processor Annapurna Alpine Unfortunately QNAP has recently discontinued range of devices, so if your NAS doesn't support QTS 4.3, it won't be able to run Domotz. QNAP offers a product status list here https://www.qnap.com/en/product/eol.php Please contact QNAP support if you don’t know what processor is used in your NAS or what OS it runs. Raspberry Pi Raspberry Pi Model B, Raspberry Pi Model B+, Raspberry Pi 2 model B and Raspberry Pi 3 model B. Note that the Raspberry Pi Model A, Raspberry Pi Model A+ and the Raspberry Pi Zero are not recommended due to hardware limitations. ReadyNAS OS 6.x or later. Minimum 512MB of RAM Any x86/x64 processor The following ARM based processors: Marvell Armada 370 and Annapurna Alpine. Synology DSM 5.x or later. Minimum 512MB of RAM Any x86/x64 processor The following ARM based processors: Marvell Armada 370, 375 and XP. We also anticipate to support the following ARM based processors: Annapurna Alpine, Freescale QorIQ LS1024A/ Mindspeed Comcerto 2000. Note that Marvell Kirkwood processors are not supported, nor are any PowerPC based processors, such as the Freescale PowerQUICC or QorIQ P-series. No models prior to the x10-series are supported. Synology lists the CPU used in their various models on their website, although for older models you might have to contact Synology's support.

Note that when you update the Domotz Agent, due to the fact that at the moment, the old Agent has to be uninstalled first, you'll be able to resume when you install the new Agent by simply logging in with the same account again. The new Agent will detect the data from the previous installation and resume where you left off. You'll see a screen that asks you to resume once you've logged in and it'll then take a little while for the Agent to resume and detect any new devices on the network.