Anomaly between light (switchlinc) and ISY admin console

[wwat]

Firmware/UI 4.0.3

 

Not sure what's going on here. There is a difference between the physical light (Switchlinc) and ISY Admin console display.

 

After getting triggered by a motion sensor the light remains off to look at but the ISY admin console reads 45%.

If I right click the node and select 'Query' it goes back to the off state.

 

I tested whether the physical light would turn on from the console and it does.

 

21.C1.86 - Motion Sensor

13.1A.E2 - Switchlinc

 

Many Thank, Wayne.

 

Wed 04/17/2013 08:37:54 : [iNST-SRX    ] 02 50 21.C1.86 00.00.01 CB 11 01    LTONRR (01)

Wed 04/17/2013 08:37:54 : [std-Group   ] 21.C1.86-->Group=1, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:37:54 : [  21 C1 86 1]      DON   1

Wed 04/17/2013 08:37:54 : [  13 1A E2 1]       ST 114

Wed 04/17/2013 08:37:54 : [13 1A E2 1  ] Link    1 : 0FF0 [A20121C186721F01] Saving  [..........72....]

Wed 04/17/2013 08:37:54 : [iNST-SRX    ] 02 50 21.C1.86 00.00.01 CB 11 01    LTONRR (01)

Wed 04/17/2013 08:37:54 : [std-Group   ] 21.C1.86-->Group=1, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:37:54 : [iNST-DUP    ] Previous message ignored.

Wed 04/17/2013 08:37:54 : [All         ] Writing 1 bytes to devices

Wed 04/17/2013 08:37:54 : [13 1A E2 1  ] Link    1 : 0FF0 [A20121C186721F01] Writing [..........72....]

Wed 04/17/2013 08:37:54 : [iNST-SRX    ] 02 50 21.C1.86 11.00.01 CB 06 00           (00)

Wed 04/17/2013 08:37:54 : [std-Group   ] 21.C1.86-->11.00.01, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:37:54 : [iNST-TX-I1  ] 02 62 13 1A E2 0F 28 0F

Wed 04/17/2013 08:37:54 : [iNST-ACK    ] 02 62 13.1A.E2 0F 28 0F 06          SET-MSB(0F)

Wed 04/17/2013 08:37:54 : [iNST-SRX    ] 02 50 21.C1.86 11.00.01 CB 06 00           (00)

Wed 04/17/2013 08:37:54 : [std-Group   ] 21.C1.86-->11.00.01, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:37:54 : [iNST-DUP    ] Previous message ignored.

Wed 04/17/2013 08:37:54 : [iNST-SRX    ] 02 50 13.1A.E2 19.75.00 2B 28 0F    SET-MSB(0F)

Wed 04/17/2013 08:37:54 : [std-Direct Ack] 13.1A.E2-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:37:54 : [iNST-TX-I1  ] 02 62 13 1A E2 0F 2B F5

Wed 04/17/2013 08:37:55 : [iNST-ACK    ] 02 62 13.1A.E2 0F 2B F5 06          PEEK   (F5)

Wed 04/17/2013 08:37:55 : [iNST-SRX    ] 02 50 13.1A.E2 19.75.00 2B 2B 72    PEEK   (72)

Wed 04/17/2013 08:37:55 : [std-Direct Ack] 13.1A.E2-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:38:44 : [iNST-TX-I1  ] 02 62 13 1A E2 0F 19 00

Wed 04/17/2013 08:38:44 : [iNST-ACK    ] 02 62 13.1A.E2 0F 19 00 06          LTSREQ (LIGHT)

Wed 04/17/2013 08:38:45 : [iNST-SRX    ] 02 50 13.1A.E2 19.75.00 2B 0B 00           (00)

Wed 04/17/2013 08:38:45 : [std-Direct Ack] 13.1A.E2-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:38:45 : [  13 1A E2 1]       ST   0

Wed 04/17/2013 08:38:45 : [13 1A E2 1  ] Link    1 : 0FF0 [A20121C186721F01] Saving  [..........72....]

Wed 04/17/2013 08:38:45 : [  13 1A E2 1]       OL 255

Wed 04/17/2013 08:38:45 : [  13 1A E2 1]       RR  31

Wed 04/17/2013 08:38:45 : [All         ] Writing 1 bytes to devices

Wed 04/17/2013 08:38:45 : [13 1A E2 1  ] Link    1 : 0FF0 [A20121C186721F01] Writing [..........72....]

Wed 04/17/2013 08:38:45 : [iNST-TX-I1  ] 02 62 13 1A E2 0F 28 0F

Wed 04/17/2013 08:38:45 : [iNST-ACK    ] 02 62 13.1A.E2 0F 28 0F 06          SET-MSB(0F)

Wed 04/17/2013 08:38:45 : [iNST-SRX    ] 02 50 13.1A.E2 19.75.00 2B 28 0F    SET-MSB(0F)

Wed 04/17/2013 08:38:45 : [std-Direct Ack] 13.1A.E2-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:38:45 : [iNST-TX-I1  ] 02 62 13 1A E2 0F 2B F5

Wed 04/17/2013 08:38:45 : [iNST-ACK    ] 02 62 13.1A.E2 0F 2B F5 06          PEEK   (F5)

Wed 04/17/2013 08:38:46 : [iNST-SRX    ] 02 50 13.1A.E2 19.75.00 2B 2B 72    PEEK   (72)

Wed 04/17/2013 08:38:46 : [std-Direct Ack] 13.1A.E2-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Wed 04/17/2013 08:39:04 : [iNST-TX-I1  ] 02 62 13 1A E2 0F 13 00

Wed 04/17/2013 08:39:04 : [iNST-ACK    ] 02 62 13.1A.E2 0F 13 00 06          LTOFFRR(00)

Wed 04/17/2013 08:39:04 : [iNST-SRX    ] 02 50 13.1A.E2 19.75.00 2B 13 00    LTOFFRR(00)

Wed 04/17/2013 08:39:04 : [std-Direct Ack] 13.1A.E2-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

[LeeG]

For the ISY to mark the SwitchLinc on at 45% the SwitchLinc is a Responder in a Scene with the Motion Sensor as Controller. The fact that the SwitchLinc does not actually turn On is either the result of a link record problem in the Motion Sensor or the SwitchLinc, or the Motion Sensor is not able to communicate with the SwitchLinc.

 

Right click the SwitchLinc, select Diagnostics | Show Device Links Table. When all the link records are displayed click Compare. The ISY will compare the link records read against what it thinks should exist in the SwitchLinc.

 

Repeat the process with the Motion Sensor being sure to put the Motion Sensor into linking mode with its Set button before running the Show Device Links Table.

 

If the link records are wrong in either device a Restore Device will rebuild the link database in the respective device. If all the link records are correct there is a communications problem between the Motion Sensor and the SwitchLinc

[wwat]

Thanks Lee,

 

The records in the Switchlinc were missing, all 5 records were there the other day because I checked. Any ideas how records can suddenly disappear?

[LeeG]

That is difficult to answer. I have seen devices lose a link database after a power outage but it is very rare. Something like a very short drop in power where the device power supply does not fully discharge before power is restored. Almost like the device treats it as a factory reset.

 

Could be a factory reset was done accidently if the air gap was pulled and restored past the frame level.

 

May never know if it does not happen again. If the situation reoccurs the device itself may be malfunctioning.

[wwat]

That is difficult to answer. I have seen devices lose a link database after a power outage but it is very rare. Something like a very short drop in power where the device power supply does not fully discharge before power is restored. Almost like the device treats it as a factory reset.

 

Could be a factory reset was done accidently if the air gap was pulled and restored past the frame level.

 

May never know if it does not happen again. If the situation reoccurs the device itself may be malfunctioning.

 

Hi Lee,

 

There was no intentional/accidental human initiated factory reset for sure. I've been through something similar with a previous version of the switchlincs (some years ago) and Smarthomes replace them all because they found some bug in the switchlinc that caused the problem but this is the newer version that they replaced it with so unless something has happened to it then it should be okay. I'll keep an eye on it but after 6 years I'm almost about to pull the plug in Insteon, it appears that its just not ever going to be stable enough for my nervous system to handle. The only thing is I'm not sure what can replace it, if anything.

 

Many thanks for your help, Wayne

[LeeG]

You are very welcome.

 

I have looked at the alternatives a few years back and was not satisfied with any of the other options at the time. With more focus on ZigBee and Zwave these days there may be viable options now. Spent some time looking for alternatives to the EZIO2X4 which monitors and controls my detached garage. Have not found a good substitute. I could live without the remote monitor/control but have gotten very use to it over the 5+ years for the garage.