It’s hard to say. That appears to be a discontinued model, the manufacturer no longer lists it on their website and I can’t find a zwave conformance statement for it.
Looking at the most current similar model, the MHS412, I’m pretty sure the one switch model will pair as a binary switch, but the 2 and 4 switch models aren’t multiple relays, they’re one device with multiple end points.
The device is using multichannel association to identify each endpoint (that is, to be able to control each switch separately) and I’m not sure ST has an official device handler that supports that, or indeed if it supports it at all.
@duncan@jim Can SmartThings use a device handler that has zwave multichannel association? The documentation discusses association groups but not multiple endpoint association. Thanks!
If it’s the glass panel form factor you like, Aeotec has one now that works with their micro relay. And they’ve promised a standalone with similar form factor for release this year.
This is the first generation model that requires the micro relay, but you can see the form factor. It also comes in white.
If it’s the two controls in one gang box you like, there are dual relays that can do that.
So ST staff have confirmed multichannel association should work.
So as long as the zwave frequencies and electrical specs are compatible, there’s a starting place.
I have now tested the Dual MCO switch however only one switch of the two can be automated as the multichannel support crashes when activated in Smartthings I have reported the problem to them and I am awaiting resolution
Yes, the issue the ZWave multichannel default driver which would need modification to support a second channel. The MCO Switch is very cool bit without the driver modification then you can only control one channel (and one switch). You can download the file as a template, when I have time I will look into modifying it.
I have now tested the Dual MCO switch however only one switch of the two can be automated as the multichannel support crashes when activated in Smartthings I have reported the problem to them and I am awaiting resolution
I’m also getting the crash on activating the second channel.
Support wrote back saying it was an unsupported device. Fair enough…
The Z-Wave Multi-Channel Device is a very complicated handler and it installs an app and child devices for which the code is not published… so trying to find out what it’s doing or why it’s crashing is next to impossible.
I did hack together a handler for the switch though. The main problem with the multi-channel handler is that it associates association group 1 to the hub node id. However for these switches, group 1 is button 1, group 2 is button 2 and the last group is the group that will send back encapsulated commands. So I removed the hub from group 1 association and added it to group 3 (for a two button switch). After this it magically sent back encapsulated commands with endpoint ids in it.
in the IDE simulator for device types, I attached it to the switch device and hit the “Configure” button on the bottom right. This will do the setup.
This works well for this one switch but this device type could definitely be improved.
I would like it to behave so that turning the “switch” device on an off turns on and off all endpoints of the switch. This is possible because the switch supports the “switch all” command set.
I would also like it to work on 3 and 4 button switches. I could do this by querying the number of endpoints and then setting the association on the last association group. At the moment it is hard-coded to 2.
Finally, I would like it to automatically install the app when it installs the device type. Not sure if this is possible or not.
Anyway, I’m going to be buying more of these switches over the next few months, so I will improve this as I get more switches. But for now the switch is working awesomely, so I’m not going to play with it for a while.