Association Groups for ZMNHDA2 Qubino dimmer 2nd switch?

[Kjamsek]

Looks as though there is a “hack” way to get messages from I2 and I3 via endpoints 2 and 3 , so Qubino devices should be getting their device handlers made in the following weeks.

You can give it a shot yourself in your device handler if you use the snippet i pasted here:

How to set Multichannel Associations to endpoints of a device

Hah! Looks like it can be hacked to work with unimplemented command classes also. For future reference, it is possible to set a Multichanel Association Lifeline association (with RAW Z-Wave bytes) on a device via it’s Device Handler if you use Configuration capability and make the configure method like this: def configure() { def assocCmds = [] assocCmds << zwave.associationV1.associationRemove(groupingIdentifier:1, nodeId:zwaveHubNodeId).format() assocCmds << new physicalgraph.device.HubAction("8E0101000101") return delayBetween(assocCmds, 1000) } In the string passed to HubAction “8E0101000101” you can modify the last two byte values in the string 8E0101000101 to fit your controller setup. My example is for Multichannel NodeId 1 with endpointId 1. For Multichannel NodeId 2 and en…