Schneider/Merten wall switch buttons to differentiate somehow

[manfred-mp]

All buttons are with same value so impossible to distinguish which one was pushed. These switches are using groups to identify different buttons but cannot see that info in HA side. Tried both integrations Z-Wave JS and Z-Wave JS to MQTT.

Any possibility to make these working?

This what logs are showing (2-button: top left, bottom left, top right, bottom right):

Log Level changed to: Debug
2021-09-13T15:45:36.400Z SERIAL « 0x010b00040004032001ffbf0096 (13 bytes)
2021-09-13T15:45:36.411Z SERIAL » [ACK] (0x06)
2021-09-13T15:45:36.416Z DRIVER « [Node 004] [REQ] [ApplicationCommand]
└─[BasicCCSet]
target value: 255
2021-09-13T15:45:36.421Z CNTRLR [Node 004] treating BasicCC::Set as a report
2021-09-13T15:45:36.423Z CNTRLR [Node 004] [] [Basic] currentValue: 0 => 255 [Endpoint 0]
2021-09-13T15:45:38.244Z SERIAL « 0x010b0004000403200100bc006a (13 bytes)
2021-09-13T15:45:38.248Z SERIAL » [ACK] (0x06)
2021-09-13T15:45:38.252Z DRIVER « [Node 004] [REQ] [ApplicationCommand]
└─[BasicCCSet]
target value: 0
2021-09-13T15:45:38.256Z CNTRLR [Node 004] treating BasicCC::Set as a report
2021-09-13T15:45:38.258Z CNTRLR [Node 004] [] [Basic] currentValue: 255 => 0 [Endpoint 0]
2021-09-13T15:45:40.198Z SERIAL « 0x010b00040004032001ffbf0096 (13 bytes)
2021-09-13T15:45:40.202Z SERIAL » [ACK] (0x06)
2021-09-13T15:45:40.206Z DRIVER « [Node 004] [REQ] [ApplicationCommand]
└─[BasicCCSet]
target value: 255
2021-09-13T15:45:40.211Z CNTRLR [Node 004] treating BasicCC::Set as a report
2021-09-13T15:45:40.213Z CNTRLR [Node 004] [] [Basic] currentValue: 0 => 255 [Endpoint 0]
2021-09-13T15:45:41.338Z SERIAL « 0x010b0004000403200100be0068 (13 bytes)
2021-09-13T15:45:41.341Z SERIAL » [ACK] (0x06)
2021-09-13T15:45:41.345Z DRIVER « [Node 004] [REQ] [ApplicationCommand]
└─[BasicCCSet]
target value: 0
2021-09-13T15:45:41.350Z CNTRLR [Node 004] treating BasicCC::Set as a report
2021-09-13T15:45:41.352Z CNTRLR [Node 004] [] [Basic] currentValue: 255 => 0 [Endpoint 0]

More details here: home-assistant/core#56192

Edit: Good info here, especially instanceId part. https://forum.z-wave.me/viewtopic.php?p=60255&sid=c3892001be0dba5c00c6912a980bccef#p60255

[AlCalzone]

Please make a driver log, loglevel debug or silly and attach it here as a file.

I'm suspecting that you need to create associations from different endpoints, but I can't see that from the information you've provided.

[manfred-mp]

Thanks for prompt reply. Log attached.
zwavejs_2021-09-13.log

[manfred-mp]

Yes, first it fails as device was sleeping. There is successful update also in the log

[AlCalzone]

Weird - the driver shouldn't even be sending any messages if the node is asleep. Have you removed all associations before trying to add the ones to target endpoint 0?

[manfred-mp]

Yes, empty group settings before added those two. Log was from 2nd button group adjustment. Can ofc try again and closer to usb stick.

[AlCalzone]

I found this while looking for a manual: https://www.tronika.no/support/downloads/zwave/Merten_bpd.pdf

While it is desirable in the case of the 2-gang Merten transmitter to use both transmitters [...]
for the status change features, this is not possible [...] the Association Command Class sends an
operational (On or Off) signal to the associated device, [...] but does not
include any information on which transmitter the signal was sent from. Therefore, HomeSeer cannot
differentiate one transmitter’s signal from the other

I'm not sure if that considers using multi channel associations, but if the device won't change those, I fear we're out of luck here.

[manfred-mp]

Thanks a lot for helping. I hope these can be returned to shop 'cause weren't cheap. Also tried OpenZWave and result is the same.

Oh well, back to drawing board... and maybe 433MHz Nexa next victim ;)