Double events with dualband dimmer (4.0.5)

[bsobel]

I'm still seeing double events for dualband dimmer v.38

 

Sun 09/15/2013 12:27:41 PM : [iNST-SRX ] 02 50 18.00.B2 00.00.01 C7 11 00 LTONRR (00)

Sun 09/15/2013 12:27:41 PM : [std-Group ] 18.00.B2-->Group=1, Max Hops=3, Hops Left=1

Sun 09/15/2013 12:27:41 PM : [ 18 0 B2 1] DON 0

Sun 09/15/2013 12:27:42 PM : [VAR 2 6 ] 5

Sun 09/15/2013 12:27:45 PM : [iNST-SRX ] 02 50 18.00.B2 21.30.4B 41 11 01 LTONRR (01)

Sun 09/15/2013 12:27:45 PM : [std-Cleanup ] 18.00.B2-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sun 09/15/2013 12:27:45 PM : [ 18 0 B2 1] DON 0

 

I can reproduce this 100% and it always seems to be 4 seconds between the original button press and the phantom second one. Does the cleanup code trigger the second (false) DON? Can you kindly reopen this bug as I believe it was assumed fixed in this version.

 

Thanks,

Bill

[LeeG]

The traced messages are correct for a button/paddle press. First is the Group Broadcast message followed by a Group Cleanup Direct message.

 

Is a Program being triggered twice by that? I don't think so since these messages are standard Group protocol. If a Program is triggered twice that would be a bug but I doubt that is happening.

[bsobel]

The paddle press events that I subscribe to are getting double DONs sent to it by the ISY.

[LeeG]

As is seen in this trace of a SwitchLinc paddle press the Group Cleanup Direct normally comes very quickly. A 4 second delay either means the SwitchLinc is a Controller of a very large Scene or there is a device that is not responding forcing the SwitchLinc into recovery for that device before it gets to the Group Cleanup Direct for the PLM.

 

Is this a very large Scene or is there a device response problem?

 

With such a long delay between the Group Broadcast and the Group Cleanup Direct it may be impossible for the ISY to determine that the Group Cleanup Direct belongs to the previous Group Broadcast.

 

 

Sun 09/15/2013 10:16:30 PM : [iNST-SRX ] 02 50 1D.38.00 00.00.01 CB 11 00 LTONRR (00)

Sun 09/15/2013 10:16:30 PM : [std-Group ] 1D.38.00-->Group=1, Max Hops=3, Hops Left=2

Sun 09/15/2013 10:16:30 PM : [ 1D 38 0 1] DON 0

Sun 09/15/2013 10:16:30 PM : [ 1D 38 0 1] ST 124

Sun 09/15/2013 10:16:30 PM : [ 20 29 9C 1] ST 255

Sun 09/15/2013 10:16:30 PM : [iNST-SRX ] 02 50 1D.38.00 22.80.0B 41 11 01 LTONRR (01)

Sun 09/15/2013 10:16:30 PM : [std-Cleanup ] 1D.38.00-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sun 09/15/2013 10:16:30 PM : [iNST-DUP ] Previous message ignored.

[arw01]

Following on Lee's suggestions, what's the link table of the device that is "sending" the duplicate reply so much later?

 

I've got a dual band switch that is like 97% responsive, maybe a little higher, even though an access point is 5' away in open air and another one is 8' away straight above it in the hallway. I don't think Smarthome quite got their RF nailed down before it left the lab! They should have included a sequence number or something with the data, even an 8 bit one that would roll over would be preferable, you could know which device is always late for 100% certainty.

 

Alan

[bsobel]

The paddle is a controller for a scene with two other member (both kpl buttons on two different kpls). Their doesn't appear to be a comms issue as the other kpls respond immediately to the key press. I cant see any other reason the cleanup would come so late.

[LeeG]

Do a Show Device Links Table of the SwitchLinc. It sounds like it has a link to a device that no longer exists if the expected devices are responding as expected. You would be looking for a link record that starts with an E2 (controller link) with a device address other than the PLM and two devices linked as responders.

[bsobel]

Do a Show Device Links Table of the SwitchLinc. It sounds like it has a link to a device that no longer exists if the expected devices are responding as expected. You would be looking for a link record that starts with an E2 (controller link) with a device address other than the PLM and two devices linked as responders.

 

That was it. Had links to two devices I had swapped out. I recall the ISY console had locked up during a couple such 'replace with' operations, looks like the side effect was the links were not removed. A restore device fixed it (the restore said there were unknown links and removed them automatically)

 

Thanks!