Good, it looks like we are making progress. We are now getting multi channel encapsulated commands that can actually be differentiated by which button is pressed, and it looks like we’ve accomplished what was written about in this post now - How to set Multichannel Associations to endpoints of a device - #8 by zcapr17
The destination endpoint is changing based on each button you press so the different button presses can now be differentiated. It looks like we have to make changes to the code in defzwaveEvent(physicalgraph.zwave.commands.multichannelv3.MultiChannelCmdEncap cmd) between lines 202 and 233 to properly decode this. Instead of the sourceendpoint changing the destination endpoint is changing with each button press. I think that is because we are actually seeing the code from the hub which is the destination now instead of the source.
Hopefully this doesn’t mess up other parts of the code process here, but just to try it out, lets try and replace references related to source endpoint with destination endpoint. Try making these changes in that section of code around lines 202-233 to say the following and see what happens now:
def zwaveEvent(physicalgraph.zwave.commands.multichannelv3.MultiChannelCmdEncap cmd) {
def map = [ name: "switch${cmd.destinationEndPoint}" ]
def encapsulatedCommand = cmd.encapsulatedCommand([0x32: 3, 0x25: 1, 0x20: 1])
log.debug "MultiChannelCmdEncap called - ${cmd.inspect()}"
if (encapsulatedCommand && cmd.commandClass == 50) {
zwaveEvent(encapsulatedCommand, cmd.destinationEndPoint)
} else {
switch(cmd.commandClass) {
case 32:
case 37:
if (cmd.parameter == [0]) {
map.value = "off"
}
if (cmd.parameter == [255]) {
map.value = "on"
}
log.debug "MultiChannelCmdEncap mapped - ${map}"
if (cmd.sourceEndPoint == 1) {
sendEvent(name: "switch", value: map.value)
} else {
def childDevice = childDevices.find{ it.deviceNetworkId == "$device.deviceNetworkId-ep$cmd.destinationEndPoint" }
if (childDevice) {
childDevice.sendEvent(name: "switch", value: map.value)
}
}
break
}
}
}