tmorse305 Posted September 18 Posted September 18 (edited) This issue is very similar to another thread but my issue does not include a node server, just an Insteon device. See screen shots. Thank you @Javi Edited September 18 by tmorse305
Javi Posted September 20 Posted September 20 Is this for a single device or all devices? If a single device does it work from Admin Console? Based on the screenshot It does not look like no devices are showing status besides programs. Is this true? What is your firmware?
tmorse305 Posted September 20 Author Posted September 20 Hi @Javi, yes all of the devices are affected. The program are also affected, the states shown in the screen shot are not correct. I tried a reboot to eisy but no improvement. eisy is at 5.8.4. I have another eisy that is working correctly running 5.8.3
Javi Posted September 20 Posted September 20 Do you get errors when opening the Admin Console? Does the Admin Console show changes to device state (not initial status, but state changes)? It looks like the event subscription is not working for some reason. Possible the firmware upgrade did not complete, may require forcing the upgrade to reinstall. Did this start after the firmware upgrade?
tmorse305 Posted September 21 Author Posted September 21 Hi @Javi, No errors opening the AC. The AC is showing the state changes, it seems to be working correctly. I'm not sure when it started. I just tried to sync this eisy to UD and got an error, see attached. I have 2 eisy eisy #1 has a UUID - that ends in 44 eisy #2 has a UUID - that ends in 8a eisy #1 is the one I'm having trouble with. eisy #2 is working correctly in UD. It also syncs successfully When I tried to sync eisy #1 the error message suggests that it is getting my 2 eisy mixed up somehow.
Javi Posted September 22 Posted September 22 Very likely the Local IP Address is incorrect. Tip: reserve IP addresses in your router if you have more than one eisy, then use the numerical IP address in UD Mobile, not eisy.local.
Solution tmorse305 Posted September 22 Author Solution Posted September 22 Hi @Javi, I figured it out. The 2 eisys are on different networks (in different states). I shut off WiFi on my phone and could immediately access eisy #1 correctly (it's the remote one). I deleted the local credentials for eisy #1 forcing it to use a remote connection. All good now even with WiFi enabled The wierd part of this is that it has been working fine for months and suddenly stopped. I haven't made any configuration changes. As always thank you very much for your help!! 1
Recommended Posts