polo2883 Posted March 21 Posted March 21 I upgraded my old 994i to eisy. Since the upgrade, my insteon device status is usually not accurate when I one the UD app. It might show the fan controller on but it actually off. My garage door sensor doesnt update the status so it wont trigger the garage lights to come on. Is this something that is a known issue?
paulbates Posted March 21 Posted March 21 Questions You mention the UDM app, but its also true on iox? You're using the PLM you had on your ISY? I would start with the event viewer in level 3 and repeat steps that fail, like opening the garage and repost.
bloodyd Posted March 21 Posted March 21 I had a similar issue when I did my upgrade from 994i to EISY. Are you using a new PLM in your system? I used a new USB PLM in my scenario and physically flipping any switches or lights on the wall units would not update the IoX status in the admin console. My fix was creating a new scene and adding the troubled device as a controller to that scene. I then right click on the device on the admin console and restore the device. Once EISY finish writing to the device, I delete the scene. This restored functionality to the device. Repeat this for all your devices that are having issues. The steps listed above did not worked for the IOlinc garage controller though. I had to remove the device from the system and re-add it for it to work correctly.
polo2883 Posted March 22 Author Posted March 22 On 3/21/2024 at 9:31 AM, paulbates said: Questions You mention the UDM app, but its also true on iox? You're using the PLM you had on your ISY? I would start with the event viewer in level 3 and repeat steps that fail, like opening the garage and repost. Yes, its showing the wrong status on both UDM App and iox. I am using the same PLM I had with my ISY. As of now, it will show the master bedroom fan on but it actually is not. I have to tap it twice if I wanted it on.
polo2883 Posted March 22 Author Posted March 22 20 hours ago, bloodyd said: I had a similar issue when I did my upgrade from 994i to EISY. Are you using a new PLM in your system? I used a new USB PLM in my scenario and physically flipping any switches or lights on the wall units would not update the IoX status in the admin console. My fix was creating a new scene and adding the troubled device as a controller to that scene. I then right click on the device on the admin console and restore the device. Once EISY finish writing to the device, I delete the scene. This restored functionality to the device. Repeat this for all your devices that are having issues. The steps listed above did not worked for the IOlinc garage controller though. I had to remove the device from the system and re-add it for it to work correctly. If that device status does not update, I dont think re-creating the scenes will help. Right now if the garage door is open, the app and IoX shows its closed. I have to manually trigger a query and then it will update the status to show its open. Or I just have to tap the icon twice.
paulbates Posted March 22 Posted March 22 Without event viewer info, there is something that might/might not work: One at a time, right click on each Device in iox and select restore device. This possibly could solve one of the things it could be
polo2883 Posted March 22 Author Posted March 22 The logs just show: I went into the room and the lights were on. The app showed it was off. Turned off the light then back on and the app never updated the status. I even relaunched the app. Looks like the two entries there are when I turned the light on and off from the app. Did not register any of the physical on and offs from the switch itself.
Solution paulbates Posted March 22 Solution Posted March 22 (edited) The event viewer, set to level 3, is different than the log and will show detailed Insteon traffic (or lack of it) to help figure out what's going on. Tools->Diagnostics->Event Viewer ... set to level 3 at the bottom and repeat your tests, post that back here by Saving the Log to File with a description of what part you were doing each test Did you try the "restore device" on one of the problem devices? Edited March 22 by paulbates 1
polo2883 Posted March 23 Author Posted March 23 Fri 03/22/2024 09:53:32 PM : [ Time] 21:53:32 1(0) Fri 03/22/2024 09:54:01 PM : [D2D EVENT ] Event [n003_controller] [CPW] [958] uom=73 prec=0 Fri 03/22/2024 09:54:01 PM : [n003_controller ] CPW 958 (uom=73 prec=0) Fri 03/22/2024 09:54:02 PM : [ Time] 21:54:02 1(0) Fri 03/22/2024 09:54:25 PM : Create REST U7 [/rest/nodes/51%20F8%20DB%201/cmd/DON] Fri 03/22/2024 09:54:25 PM : U7 Rest: submitCmd([51 F8 DB 1],[DON],[<NULL>]) Fri 03/22/2024 09:54:25 PM : [INST-TX-I1 ] 02 62 51 F8 DB 0F 11 FF Fri 03/22/2024 09:54:25 PM : [INST-ACK ] 02 62 51.F8.DB 0F 11 FF 06 LTONRR (FF) Fri 03/22/2024 09:54:25 PM : [INST-SRX ] 02 50 51.F8.DB 34.E7.24 2F 11 FF LTONRR (FF) Fri 03/22/2024 09:54:25 PM : [Std-Direct Ack] 51.F8.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 03/22/2024 09:54:25 PM : [D2D EVENT ] Event [51 F8 DB 1] [ST] [255] uom=100 prec=0 Fri 03/22/2024 09:54:26 PM : [51 F8 DB 1 ] ST 255 (uom=100 prec=0) Fri 03/22/2024 09:54:27 PM : Create REST U7 [/rest/nodes/51%20F8%20DB%201/cmd/DOF] Fri 03/22/2024 09:54:27 PM : U7 Rest: submitCmd([51 F8 DB 1],[DOF],[<NULL>]) Fri 03/22/2024 09:54:27 PM : [INST-TX-I1 ] 02 62 51 F8 DB 0F 13 00 Fri 03/22/2024 09:54:27 PM : [INST-ACK ] 02 62 51.F8.DB 0F 13 00 06 LTOFFRR(00) Fri 03/22/2024 09:54:27 PM : [INST-SRX ] 02 50 51.F8.DB 34.E7.24 2F 13 00 LTOFFRR(00) Fri 03/22/2024 09:54:27 PM : [Std-Direct Ack] 51.F8.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 03/22/2024 09:54:27 PM : [D2D EVENT ] Event [51 F8 DB 1] [ST] [0] uom=100 prec=0 Fri 03/22/2024 09:54:27 PM : [51 F8 DB 1 ] ST 0 (uom=100 prec=0) Fri 03/22/2024 09:54:32 PM : [ Time] 21:54:32 1(0) Thats from the event viewer. I turned the fan on from the switch and the app and IoX shows off. Tapped on the fan in the app and the status updated to on. Tap it again and it turned off.
polo2883 Posted March 23 Author Posted March 23 6 hours ago, paulbates said: The event viewer, set to level 3, is different than the log and will show detailed Insteon traffic (or lack of it) to help figure out what's going on. Tools->Diagnostics->Event Viewer ... set to level 3 at the bottom and repeat your tests, post that back here by Saving the Log to File with a description of what part you were doing each test Did you try the "restore device" on one of the problem devices? Thanks for the advise. A restore of the switches worked.
Recommended Posts