Jump to content

Event 255 status (On) does not match responder's actual status


Recommended Posts

I have a remotelinc (2440) that controls three lamps.  Two responders are models 2456S3 and one is a 2466S.  I use the Admin console with ISY 994i.  The third lamp using the 2466S has always been intermittent.  Sometimes it would work and sometimes not.  Looking in the Event Viewer for device communications I see nothing for any of the three devices, even the two that work.  I decided to remove the RemoteLinc and the three responders.  Factory reset them and then add them back into the admin console.  I have added the two 2456S3 devices.  I now see communication events for both.  One (living room lamp) works fine.  Turns off and on in response to the remotelinc buttons.  The other is not working.  This is what I don't understand.  In the admin console when I press the ON button on Remotlinc I see the status change to ON.  The event viewer at level 1 shows:

[address of remotelinc   2]  DON 0

[address of 2456S3   1]        ST 255

[address of remotelinc    2]   ST 255

But the lamp does not turn on.  If I go to the admin console and click the "ON" button the lamp turns on.  The event viewer shows:

[address of 2456S3 1]  ST 255       and the lamp goes ON.

This is the event viewer level 3 when using remotelinc:

Wed 03/28/2018 14:30:45 : [INST-SRX    ] 02 50 21.D8.BC 00.00.02 CF 11 00    LTONRR (00)
Wed 03/28/2018 14:30:45 : [Std-Group   ] 21.D8.BC-->Group=2, Max Hops=3, Hops Left=3
Wed 03/28/2018 14:30:45 : [D2D EVENT   ] Event [21 D8 BC 2] [DON] [0] uom=0 prec=-1
Wed 03/28/2018 14:30:45 : [  21 D8 BC 2]      DON   0
Wed 03/28/2018 14:30:45 : [D2D EVENT   ] Event [A B8 DB 1] [ST] [255] uom=0 prec=-1
Wed 03/28/2018 14:30:45 : [   A B8 DB 1]       ST 255
Wed 03/28/2018 14:30:45 : [INST-SRX    ] 02 50 21.D8.BC 00.00.02 CB 11 00    LTONRR (00)
Wed 03/28/2018 14:30:45 : [Std-Group   ] 21.D8.BC-->Group=2, Max Hops=3, Hops Left=2
Wed 03/28/2018 14:30:45 : [INST-DUP    ] Previous message ignored.
Wed 03/28/2018 14:30:45 : [INST-SRX    ] 02 50 21.D8.BC 41.E8.0D 41 11 02    LTONRR (02)
Wed 03/28/2018 14:30:45 : [Std-Cleanup ] 21.D8.BC-->ISY/PLM Group=2, Max Hops=1, Hops Left=0
Wed 03/28/2018 14:30:45 : [INST-DUP    ] Previous message ignored.

 

What am I missing here?  The responder is saying it is turning on (ST 255) but it does not.   

My UD994 firmware version:  v4.4.6

UD994 UI version   v4.6.2

 

 

Link to comment
1 hour ago, Lightyears said:

I have a remotelinc (2440) that controls three lamps.  Two responders are models 2456S3 and one is a 2466S.  I use the Admin console with ISY 994i.  The third lamp using the 2466S has always been intermittent.  Sometimes it would work and sometimes not.  Looking in the Event Viewer for device communications I see nothing for any of the three devices, even the two that work.  I decided to remove the RemoteLinc and the three responders.  Factory reset them and then add them back into the admin console.  I have added the two 2456S3 devices.  I now see communication events for both.  One (living room lamp) works fine.  Turns off and on in response to the remotelinc buttons.  The other is not working.  This is what I don't understand.  In the admin console when I press the ON button on Remotlinc I see the status change to ON.  The event viewer at level 1 shows:

[address of remotelinc   2]  DON 0

[address of 2456S3   1]        ST 255

[address of remotelinc    2]   ST 255

But the lamp does not turn on.  If I go to the admin console and click the "ON" button the lamp turns on.  The event viewer shows:

[address of 2456S3 1]  ST 255       and the lamp goes ON.

This is the event viewer level 3 when using remotelinc:

Wed 03/28/2018 14:30:45 : [INST-SRX    ] 02 50 21.D8.BC 00.00.02 CF 11 00    LTONRR (00)
Wed 03/28/2018 14:30:45 : [Std-Group   ] 21.D8.BC-->Group=2, Max Hops=3, Hops Left=3
Wed 03/28/2018 14:30:45 : [D2D EVENT   ] Event [21 D8 BC 2] [DON] [0] uom=0 prec=-1
Wed 03/28/2018 14:30:45 : [  21 D8 BC 2]      DON   0
Wed 03/28/2018 14:30:45 : [D2D EVENT   ] Event [A B8 DB 1] [ST] [255] uom=0 prec=-1
Wed 03/28/2018 14:30:45 : [   A B8 DB 1]       ST 255
Wed 03/28/2018 14:30:45 : [INST-SRX    ] 02 50 21.D8.BC 00.00.02 CB 11 00    LTONRR (00)
Wed 03/28/2018 14:30:45 : [Std-Group   ] 21.D8.BC-->Group=2, Max Hops=3, Hops Left=2
Wed 03/28/2018 14:30:45 : [INST-DUP    ] Previous message ignored.
Wed 03/28/2018 14:30:45 : [INST-SRX    ] 02 50 21.D8.BC 41.E8.0D 41 11 02    LTONRR (02)
Wed 03/28/2018 14:30:45 : [Std-Cleanup ] 21.D8.BC-->ISY/PLM Group=2, Max Hops=1, Hops Left=0
Wed 03/28/2018 14:30:45 : [INST-DUP    ] Previous message ignored.

 

What am I missing here?  The responder is saying it is turning on (ST 255) but it does not.   

My UD994 firmware version:  v4.4.6

UD994 UI version   v4.6.2

 

 

Your firmware and UI should always be the same version. Update the firmware and see if that corrects your problem.

Link to comment
2 hours ago, Lightyears said:

I updated the firmware.  Both are 4.6.2.  Cleared the Java cache.  Reloaded the admin console.  Same behavior.  

The 2456 ApplianceLinc was discontinued and replaced with the dual band on/off module which is more reliable.

What type of bulb and wattage is connected to the module you're having problems with?

 

 

 

Link to comment

19w CFL.  It is interesting to note that this particular lamp and 2456S3 worked flawlessly for a long time.  The trouble started when I deleted all links and did a factory reset on the three responders connected to the remotelinc trying to get the 2466S to work reliably. The 2466S is still intermittent.  The 2456S3 is now doing the same thing the 2466S has been doing for a longtime.  

The 2456S3 in question is also part of a scene that turns on inside lights at sunset.  The scene ran at sunset and the ISY shows current state as ON but the lamp is not ON.  Going to the 2456S3 in the admin console had clicking ON turns the lamp on.  It looks like turning the lamp on via the admin console works fine.  Trying to do so via a scene or another controller does not work even though status shows the action completed. 

 

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...