Schneider connect 2 paddle switch (4 button controller)

[taneli.kaukoranta]

Hello, I'm back at it again.
I am now able to create a childDevice but i have no idea what to do now. I have tried to associate with its nodeID but i haven't had any luck with that. I have tried several types of nodeID:s for the childDevice like: 4F-1, 14F and so on. I've even tried to give the child id 100 and then tried to associate with that, but i think the association doesn't even go through. I can how ever associate with "zwaveHubNodeId", then I can use the right button but it just does the same as the left one. And noticed that I can associate straight with a node id of a physical relay, with the nodeID given in the hub?!
Also I somehow managed to put the switch in a multicast mode, and got parsed messages like this:

parse description: zw device: 51, command: 2001, payload: FF , isMulticast: false

parse description: zw device: 51, command: 2001, payload: FF 1D 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 , isMulticast: true

parse description: zw device: 51, command: 2001, payload: 00 , isMulticast: false

parse description: zw device: 51, command: 2001, payload: 00 1D 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 , isMulticast: true

[taneli.kaukoranta]

Ok, I ain't getting nowhere with this.

Is there a way to distinguish the commands sent from the group 1 and group 3?

What should the groups be associated with?

This is the switch i'm trying to get working.

[taneli.kaukoranta]

@bcopeland Hey!

Do you know if MultiChannelAssociation v1 supports endpoints?
Becouse if not I think my efforts to get these things working through the hub are effortless.

Or there is something I'm missing here.

[bcopeland]

@taneli.kaukoranta

MultiChannelAssociation

The whole point of multi-channel is endpoints.. So yes

[bcopeland]

And the endpoints will be identified in multi-channel encapsulation

[taneli.kaukoranta]

Ok, thanks again!
I will dig in to that topic next.
There is just SO much info out there so it is very hard for me to find the right info pieces.

[taneli.kaukoranta]

Ahh yes, my device doesn't support multi-channel. Or atleast it isn't mentioned in and out clusters:

• nClusters: 0x72,0x86,0x70,0x85,0x8E
• outClusters: 0x85,0x20,0x26,0x50

Or is it included in the MultiChannelAssociation V1 class?

[bcopeland]

If it supports multi-channel association.. It has to support multi-channel encapsulation..

[taneli.kaukoranta]

Ok, great!

Just making sure I don't bang my head against the wall next couple of days

[taneli.kaukoranta]

Interesting, I modified your parent driver to set the associations to my switch and now it has endpoints set to group 2 and 3. So, now i have to figure out how to use the encapsulation. Now the left paddle turns on the parent driver and the right can be configured to set the child driver.
And apparently the switch uses multi-instance rather than multi-channel:

skip: MultiInstanceCmdEncap(command:1, commandClass:32, instance:2, parameter:[0])

parse description: zw device: 53, command: 6006, payload: 02 20 01 00 , isMulticast: false

[taneli.kaukoranta]

Uhhoh, I just can't wrap my head around this.
What are the commands for the parent to turn the child componen switch on and off?

[taneli.kaukoranta]

def zwaveEvent(hubitat.zwave.commands.multichannelv3.MultiChannelCmdEncap cmd)
{
def result
if (cmd.parameter == 0) {
result = getChildDevice("53-1").createEvent(name: "switch", value: "off")
} else {
result = getChildDevice("53-1").createEvent(name: "switch", value: "on")
}
return result
}

Is this even close?

@bcopeland Sorry to bother you again

[bcopeland]

No problem.. See this post:

Writing parent-child driver for a 2-gang light switch

Yes, then you can use the switch command in the parent as an all on, all off. Yes Component devices use a special form of parse. That way the child logging options are respected. From the parent, cd.parse([[name:"switch", value:value, descriptionText:descriptionText]]) Where the parameter to parse is a list of maps, so you can send multiple events in one shot. The parent implements methods for each child capability command in the form: void componentOn(d){ sendHubCommand(new HubAct…

[taneli.kaukoranta]

Finally got it working!!
Thanks a million times @bcopeland

[bcopeland]

anytime

[UGON]

@taneli.kaukoranta
I also have this Schneider switch, but I don't know anything about these programming things. Is it possible to share your driver?

[taneli.kaukoranta]

Hello ugon,

I can share it, but it's not "consumer ready" for I just stiched it together and got it barely working. It's combination of two drivers, an alteration of @bcopeland s driver and one of my own. First you must use the copeland driver to associate and create the child devices. then you change the driver of the parent device and child device to my schneider driver.

@bcopeland Is it ok to share your driver with my alterations here, for I don't know how this works?

[bcopeland]

Yes

[FinTR]

Hi Taneli,

Is it possible to share the driver and a short conclusion here in forum as a result of the topic.

As Ugon, I also have the switch and just switching into Hubitat from Zipato. Since 90's I haven't been in touch with a code, so the result might help me (and the rest of newbies) to understand the code flow.