Faulty Switchlinc?

[apostolakisl]

This is a 2477D.  The on level is set to 72% and it used to work.  Now, when manually controlled, it goes to 100%.  Also, the admin console for a split second shows 72%, then it reverts to "off".  A query corrects that to 100%.  If I use the admin console to turn it on, it goes to 72% and shows 72%.

 

Of course I did a factory reset and restore device.

 

The switch used to go correctly go to 72% when manually controlled.  I noticed it going to 100% maybea few weeks ago but didn't look into it until today.  Here is the ISY comm log.  I am starting in the off state, clicking the on paddle, then a few seconds later clicking the off paddle.

 

 

Tue 12/12/2017 06:55:04 AM : [iNST-SRX    ] 02 50 43.D2.76 00.00.01 CB 11 00    LTONRR (00)

Tue 12/12/2017 06:55:04 AM : [std-Group   ] 43.D2.76-->Group=1, Max Hops=3, Hops Left=2

Tue 12/12/2017 06:55:04 AM : [D2D EVENT   ] Event [43 D2 76 1] [DON] [0] uom=0 prec=-1

Tue 12/12/2017 06:55:04 AM : [  43 D2 76 1]      DON   0

Tue 12/12/2017 06:55:04 AM : [D2D EVENT   ] Event [43 D2 76 1] [sT] [184] uom=100 prec=0

Tue 12/12/2017 06:55:04 AM : [  43 D2 76 1]       ST 184 (uom=100 prec=0)

Tue 12/12/2017 06:55:05 AM : [iNST-SRX    ] 02 50 43.D2.76 00.01.01 CB 11 01    LTONRR (01)

Tue 12/12/2017 06:55:05 AM : [std-Group   ] 43.D2.76-->Group=1, Max Hops=3, Hops Left=2

Tue 12/12/2017 06:55:05 AM : [D2D EVENT   ] Event [43 D2 76 1] [DON] [1] uom=0 prec=-1

Tue 12/12/2017 06:55:05 AM : [  43 D2 76 1]      DON   1

----->>>>>Tue 12/12/2017 06:55:05 AM : [D2D EVENT   ] Event [43 D2 76 1] [sT] [1] uom=100 prec=0<<<<<----  ? is this the problem?

Tue 12/12/2017 06:55:05 AM : [  43 D2 76 1]       ST   1 (uom=100 prec=0)

Tue 12/12/2017 06:55:05 AM : [iNST-SRX    ] 02 50 43.D2.76 11.00.01 CB 06 00           (00)

Tue 12/12/2017 06:55:05 AM : [std-Group   ] 43.D2.76-->11.00.01, Max Hops=3, Hops Left=2

Tue 12/12/2017 06:55:05 AM : [iNST-INFO   ] Previous message ignored.

Tue 12/12/2017 06:55:08 AM : [iNST-SRX    ] 02 50 43.D2.76 00.00.01 CB 13 00    LTOFFRR(00)

Tue 12/12/2017 06:55:08 AM : [std-Group   ] 43.D2.76-->Group=1, Max Hops=3, Hops Left=2

Tue 12/12/2017 06:55:08 AM : [D2D EVENT   ] Event [43 D2 76 1] [DOF] [0] uom=0 prec=-1

Tue 12/12/2017 06:55:08 AM : [  43 D2 76 1]      DOF   0

Tue 12/12/2017 06:55:08 AM : [D2D EVENT   ] Event [43 D2 76 1] [sT] [0] uom=100 prec=0

Tue 12/12/2017 06:55:08 AM : [  43 D2 76 1]       ST   0 (uom=100 prec=0)

Tue 12/12/2017 06:55:08 AM : [iNST-SRX    ] 02 50 43.D2.76 00.01.01 CB 13 01    LTOFFRR(01)

Tue 12/12/2017 06:55:08 AM : [std-Group   ] 43.D2.76-->Group=1, Max Hops=3, Hops Left=2

Tue 12/12/2017 06:55:08 AM : [D2D EVENT   ] Event [43 D2 76 1] [DOF] [1] uom=0 prec=-1

Tue 12/12/2017 06:55:08 AM : [  43 D2 76 1]      DOF   1

Tue 12/12/2017 06:55:08 AM : [iNST-SRX    ] 02 50 43.D2.76 13.00.01 CB 06 00           (00)

Tue 12/12/2017 06:55:08 AM : [std-Group   ] 43.D2.76-->13.00.01, Max Hops=3, Hops Left=2

Tue 12/12/2017 06:55:08 AM : [iNST-INFO   ] Previous message ignored.

 

 

EDIT:  I changed the ramp rate, and now the switch is behaving correctly (local on paddle press - > 72%).  However, the admin console still flashes "72%" for a split second and then goes back to "off".

[stusviews]

If you originally selected a 9 min ramp rate, then that may be the problem. That ramp rate is to accommodate older devices and does not exist for current devices.

[apostolakisl]

If you originally selected a 9 min ramp rate, then that may be the problem. That ramp rate is to accommodate older devices and does not exist for current devices.

No.  1/2 second.  I changed to 2 seconds, then it worked.  Changed back to 1/2 second and that part at least still works (turning on to 72% rather than 100%)..

 

However, it still appears to be sending two status updates, the second one with a status level of "1", meaning 1/256 or effectively 0%

 

The first status update it sends is 184.  Or 184/256=72% . . . correct.  But the second one comes less than a second later and is wrong.  I don't know why it is sending two at all, let alone why the second is wrong.

[apostolakisl]

I fixed it.

 

I had to completely delete it from ISY, factory reset it, then re-add it and re-build the scene and switch attributes.  I don't know how that fixed this problem, but it did.

[stusviews]

A factory reset is often all that's needed when you come across an errant device.

 

BTW, you usually don't need to delete the device. Try a factory reset, then use the ISY to rebuild the links (scenes) and programs, right click, then Restore Device often followed by Write Updates to Device.

[apostolakisl]

A factory reset is often all that's needed when you come across an errant device.

 

BTW, you usually don't need to delete the device. Try a factory reset, then use the ISY to rebuild the links (scenes) and programs, right click, then Restore Device often followed by Write Updates to Device.

Please see post 1.