Switch/Fan device sends 2 button pressed packets

Switches Firmware Discussion
, , ,
1

v1.36

Associations: Group 1 only, endpoint 1

The device is only being used as a scene controller with no loads. So in this case I am pressing and releasing the bottom button and toggling another switch via the event notification that is generate.

From the HomeSeer4 log it appears that on a single button press a MultiChannel V3 packet is received, which HS4 translates to a Central Scene V2, which then trips by “Button was pressed” event. Then a Central Scene V2 packet is also received from the device, which of course trips the same event again. It happens that the second event comes in fast enough that the state of the switch being toggled has not yet changed, so both events tell the switch to do the same thing. But obviously such fortune cannot always be relied on. Can this be remedied with some alternate association?

Log:

ApplicationCommandHandler from Network: F255241A Node: 154 HANDLING: COMMAND_CLASS_MULTI_CHANNEL_V3 Frame(7)=13

Payload1: 5B-03-3F-80-01-B1-00-42

Frame: 60-0D-00-01-5B-03-3F-80-01-B1-00-42

Payload1 zd is not nothing

Set_New_Level_Real: Initial device is Main Floor Library Central Scene

Set_New_Level_Real called for Main Floor Library Central Scene, Type=COMMAND_CLASS_CENTRAL_SCENE_V2, EndPoint=0

Set_New_Level, Parent: Main Floor Library Scene.Root, Child:Main Floor Library Central Scene

Setting device Central Scene to value 1000 Network: F255241A Node: 154 Device Ref: 1890

Event Trigger “Main Floor Library.Cabinets - Toggle”

Payload1: 5B-03-3F-80-01-B1-00-42

Payload1 zd is not nothing

Set_New_Level_Real: Initial device is Main Floor Library Central Scene

Set_New_Level_Real called for Main Floor Library Central Scene, Type=COMMAND_CLASS_CENTRAL_SCENE_V2, EndPoint=0

Device: Main Floor Library Cabinets to Off (0) by/from: CAPI Control Handler

Set_New_Level, Parent: Main Floor Library Scene.Root, Child:Main Floor Library Central Scene

Setting device Central Scene to value 1000 Network: F255241A Node: 154 Device Ref: 1890

Event Trigger “Main Floor Library.Cabinets - Toggle”

2

Still hoping to get a resolution on this issue. It seems that maybe the new super duper 2-button switch sends a V3 packet, and then to remain compatible sends a V2 packet. Except that HomeSeer receives both and produces 2 events, one for each packet received.

3

Tagging @EricM_Inovelli for visibility. Listing it as a bug until resolved.

4

I feel like I answered this somewhere else recently. If you remove the association from group 1 to the Homeseer node ID then it will only send the multi-channel report. In the end you should have:

Group 1 - endpoint 1 - to Homeseer node id
Group 1 - endpoint 2 - to Homeseer node id

5

Or I just use Group 1 - endpoint 0 - to HomeSeer node id, and receive the COMMAND_CLASS_CENTRAL_SCENE_V2 and not the additional COMMAND_CLASS_MULTI_CHANNEL_V3, apparently with another embedded COMMAND_CLASS_CENTRAL_SCENE_V2, which works for me.

1 Like