Indigo Domotics

IP address confirmed in mobile application

Hub software version 4.15.280

App version is 5.7.7

Interesting. I have two hubs set up, one worked fine (the one we use every day) and the other gave the error when I restarted it. I checked, the first had XMPP enabled as expected, the second did not. The second one also has a Cloud Access option that the first one does not. Hmm. I enabled XMPP and disabled Cloud. And then it started to work.

Joe,

I have 26 triggers and actions that use the hub plugin. If I delete and reinstall the hub device these will all have to be reconfigured.

Is it worth doing that?

Mike

Just disabled cloud access and left XMPP enabled. No change

Try disabling XMPP, restarting the hub, then enabling it again.

If you're still getting the error, disable the device, then create a new one with the correct IP address. DON'T delete the old one. See if the new one works.

Was not sure how to disable the the existing hub device without deleting it. So I just erased it's IP setting.

Created new Hub device with the correct IP address. Reloaded plugin. Same errors.

Disabling XMPP restarting hub and reinabling XMPP produced same error.

This is probably a dumb question, but are you able to ping the hub from the Mac?

If so, and if you have 'nc' (NetCat) on your Mac, you could try 'nc -zv ipaddress 5222' and see if the XMPP port is listening. Success will look like this:

% nc -zv 192.168.0.118 5222
Connection to 192.168.0.118 port 5222 [tcp/jabber-client] succeeded!

Also, how many NICs are active on the Mac, and are they all connected to the same network?

Again, probably dumb questions. Apologies if so.

ping to hub reports no route to host host is down.

Not sure what you meant by 'nc ipaddress 5222 and how to do that.

If the ping fails you have a network problem.

Sure looks that way. I'll track it down and let you know what I found.

Thanks for your patience and support

Mike

So....
After unplugging hub for 30 seconds and replugging it in.

DHCP assigned a new IP address. After updating the hub device to than new address and reloading the plugin Is started working again.

Not quite sure what went on to cause the problem but I'll definitely reserve that address for the hub.

Again, thanks for your support Joe.