Search the Community

TLDR:: Change the appliance from dhcp to static. Historically, I have, almost exclusively, run the Domotz agents on a simple Ubuntu install (or container). For the most part, all of those installs when fine with no major issues other than those that were user generated. In my new position, I, as always, started spreading the Domotz gospel. After making sure that my new boss was at least slightly receptive to the idea, I took that as a go ahead. This go around, I decided to try something a little different. We have a decent dev-ops/testing ESXi setup with plenty of spare resources. Domotz even has a pre-built ESXi appliance, making this a match made in heaven. After getting the image fired up (this is a dual-homed VM, BTW), I dropped a line to support asking them to swing my agent from the test setup to this new MAC address. Once confirmation was received, I pulled up the agent's web portal, hit "resume," and waited for magic to happen... and waited... and waited... The new agent would work through the resume checklist, arrive at done, and then just sit there, thinking. No error message (which might be something that needs to be looked into), just stuck. I switched over to the Domotz Web App, but it showed no change. The new agent had never checked in. I ran through this several times. Restarted the VM, I even restarted the host (just in case something got hung up in one of my vSwitch/vPort/vNIC setups). No luck. Just to stop any questions which may be coming, yes, ESXi showed good data for the appliance, IPs were registered in the dashboard. I dropped to the console of the appliance to verify connectivity, everything there was also good (local pings, remote pings (by IP and DNS)). Anyway, after going round and round, support asked for some log files. I didn't really think it was a Domotz problem and I really don't like passing along log files so someone else can try to fix my problem. That isn't a knock against Domotz, that is a pride problem on my part. Finally, as a last ditch effort before trying a different type of agent install, I changed the interface settings in the appliance from DHCP to static. Rebooted the VM, hit resume, and success. Not sure why the appliance was having an issue with the dhcp setup, connectivity was good from the moment it first came on, but switching to true static (in the appliance, not a MAC reservation) instantly cleared things up for me. Hopefully this helps someone else.

Hi All, Here you can find a link to Download our Hyper-V prebuilt image based on Ubuntu Server 20.04: https://domotz-vm-images-temp.s3-eu-west-1.amazonaws.com/Ubuntu_20.04_Domotz_Agent_2.5.9-3.1.0-b001_HyperV.zip To import the image and activate the agent do the following: 1. Open the Hyper-V Manager > Click on Action > Import Virtual Machine...: 2. Select the folder where you Downloaded and extracted the Image above: 3. Select the VM found: 4. Import it using a new unique ID: 5. Select the place where you want to save the VM and its virtual Disk: 6. Click on finish. 7. Once the VM is imported make sure the VM is connected to the correct virtual switch configured in bridge mode, so the VM will get a valid IP Address on the network: 8. Start the VM. To login and see the current IP address use the following credentials: User: domotz Password: domotz 9. At the command prompt run command "ifconfig", the current IP Address will be shown. 10. Activate the agent from a browser access the VM IP address on its port 3000 (e.g. http://192.168.1.104:3000). If you need assistance, please do not hesitate to answer to this thread or contact our Support team: support@domotz.com. Henrique Salvador Domotz Support

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

Hi, I'm trying to configure a scan of my 2nd subnet, but i'm not able to enter it. My subnet is 192.168.24.0/255.255.252.0 When i try to enter the network mask i get an error, is there really no way to add such subnet ?

Hi, I thought the agent would update automatically. However I see the following in the Domotz Portal under "Subscriptions": Agent Version:1.8.5, Package Version: 2.1.5-0354 The latest release notes say that the agent version is 2.0.5? Any idea anyone? Thanks // Tom BTW: I have a Raspberry Pi running the agent here. Looks as if automatic updates are not supported for such devices. If this is true, then how do I upgrade to the lastest agent version? Thanks // Tom

https://portal.domotz.com/portal/hardware/instructions/debian I am running Debian version 8.10 (x64) and my Domotz agent recently stopped working. I tried to reinstall the agent using the instructions on the previously mentioned Web page. The agent ran for a minute or two and then stopped reporting shortly thereafter. Based on the version number, domotz-debian-x64-1.0-2.1.5-0354.deb seems really old to me. Is there a newer one i can try? Please advise, thank you.

Hello, my Domotz agent (installed on a Qnap NAS) is down. the license expires in 2019 Mar 20. I just ordered a Domotz Box from the Krika dealer. How do I transfer credits / licenses from my old agent to the Domotz Box (new agent) ? thanks Regards,

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.

I am looking to use domotz in an environment like a motel to monitor the wifi access points, router etc. As it is a motel there are a large number of devices that are connected for a short period of time and then leave. I understand no making them interesting or monitored and not enabling the alerting for new devices but how are these short term devices removed from the device list?

Hi, I'm new to Domotz. I have it running on my synology and on a raspberry pi. Now I want to reset the agent on the raspberry pi because i'm going to bring it to a different location/network. In the dashboard it keeps saying it's online while it's disconnected . What do I need to do?

Has anyone created a vm appliance in vmware or any other virtual image agent?

Is there a Domotz agent for DS216j? It doesn't appear in package center.

I haven't been able to find an answer on this. I know that the Domotz Pi will auto update the agent but I don't see any info on updating a non-Domotz Pi's agent. Thanks!

We have been notified by two different users that Banana Pi works with the Domotz agent, without any issue. Note that this is not an officially supported platform, but as long as you run a Debian based OS, it seems to be working fine. We will continue testing our solution on as many as possible different maker's boards, so that you can enjoy the Domotz experience as you prefer.

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 <link_removed>, 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.