RGBW Controller 2 Z-Wave Association

jonathanb · August 25, 2021, 11:42am

I am using openhab 3.1.0 stable release and I have two RGBW Controller 2 that I want to keep the RGBW in sync with each other.

I have them both pair to the controller with security and I am using group 2 association to pair them. I am setting:

group_2:
    - node_21_2

I have also tried:

  group_2:
    - node_21_2
    - node_21_3
    - node_21_4
    - node_21_5

Debug log snippet:

2021-08-25 12:33:53.312 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Handler disposed. Unregistering listener.

2021-08-25 12:33:53.330 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 21: Serializing to file /var/lib/openhab/zwave/network_cd606d63__node_21.xml

2021-08-25 12:33:53.372 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:512:node21.

2021-08-25 12:33:53.374 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Controller status changed to ONLINE.

2021-08-25 12:33:53.375 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Controller is ONLINE. Starting device initialisation.

2021-08-25 12:33:53.382 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Updating node properties.

2021-08-25 12:33:53.384 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Updating node properties. MAN=271

2021-08-25 12:33:53.385 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Updating node properties. MAN=271. SET. Was 271

2021-08-25 12:33:53.387 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Properties synchronised

2021-08-25 12:33:53.449 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Update ASSOCIATION group_ZWaveAssociationGroup [index=1, name=Lifeline, profile1=0, profile2=1, associations=[node_1_1]]: Adding Controller (node_1_1)

2021-08-25 12:33:53.460 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Update ASSOCIATION group_ZWaveAssociationGroup [index=2, name=RGBW Sync, profile1=32, profile2=0, associations=[node_22_2, node_22_3, node_22_4, node_22_5]]: Adding node_22_2

2021-08-25 12:33:53.461 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Update ASSOCIATION group_ZWaveAssociationGroup [index=2, name=RGBW Sync, profile1=32, profile2=0, associations=[node_22_2, node_22_3, node_22_4, node_22_5]]: Adding node_22_3

2021-08-25 12:33:53.462 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Update ASSOCIATION group_ZWaveAssociationGroup [index=2, name=RGBW Sync, profile1=32, profile2=0, associations=[node_22_2, node_22_3, node_22_4, node_22_5]]: Adding node_22_4

2021-08-25 12:33:53.463 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Update ASSOCIATION group_ZWaveAssociationGroup [index=2, name=RGBW Sync, profile1=32, profile2=0, associations=[node_22_2, node_22_3, node_22_4, node_22_5]]: Adding node_22_5

2021-08-25 12:33:53.464 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Configuration synchronised

2021-08-25 12:33:53.558 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.

I have a full debug logfile.

But no matter what when I tell one to turn on from the GUI the other doesn’t replicate the level of each channel. Has anyone got this working?

jonathanb · August 31, 2021, 1:19pm

I have tried looks around and I haven’t found a solution as yet not sure what part of it is failing.

mstormi · August 31, 2021, 2:48pm

You must not try to directly sync the devices with each other, that’s not possible.

I have the same requirement and use a (color) item with two channels (one to each device) and the follow profile.

jonathanb · August 31, 2021, 3:01pm

Markus thanks for the pointer.

Ohh that is odd as the manual states that is possible via associations. So are you creating a group or just putting both device channels into the same item.

mstormi · August 31, 2021, 3:04pm

really? I love to be proven wrong.

as I wrote, a single item with two channels

jonathanb · August 31, 2021, 4:30pm

Or have I missed something?

mstormi · August 31, 2021, 4:35pm

No I don’t think so.
Didn’t know this is available, on my -441 it is not.
Have you tried to sync to node_21_0 ? That’s the device itself, not a channel as you tried.
I’d think that would be the primary choice to try. Might be without _0.

jonathanb · August 31, 2021, 4:55pm

I have tried node_21 but not node_21_0 so just tried it and no dice. This is my first Fibaro device but when reading up they do seem biased towards their own controller. However, I am sure this is a simple z-wave alteration.

chris · August 31, 2021, 8:28pm

Just chiming in here - maybe there is an exception for this device, but in most cases this doesn’t work. Associations report the state change of a device if it’s controlled locally, but not if it’s controlled remotely. This is done to avoid a reporting loop where one device is changed - it reports state change to another device, which reports to another device, which reports to the original device, and around we go. I’ve not seen any device do this, but again, maybe there is an exception here

jonathanb · August 31, 2021, 9:20pm

Chris,

Thank you this is an interesting point. I am not controlling this locally apart from a light switch to cut power. I would strongly suggest that your right. MCOhome light switches do association when controller signals a state change it does repeat to the other group. But through testing Fibaro seem to behave as you describe.

Your point is most likely the case and Markus way is the best path for this to work.