Thanks for the shout, but the zigbee swap wasn’t my hack, I just linked to the project report from the community member who’d done it. (In the other thread I linked to)
As far as the Wayne dalton gateway device, you can find out what command sets any certified Z wave device uses by checking its conformance statement on the official Z wave products website.
It’s really important to understand that with zwave, you could have two Devices that look physically identical on the outside, but that use completely different methods to communicate with the network. And that method is set in the firmware of the device, there’s no way for us to change it.
In the case of devices with buttons, there are three typical methods and it’s really important to know which one the particular device you are considering is using.
Association. This is what the minimote uses. There’s a whole bunch of technical stuff I’m not going to go into in this post, but the main point is that you can set it up so that when you press a button on the minimote, the hub gets told about it. From there, you could have a smartapp that can capture that button press and then do something. Turn on a switch, change the mode, run a routine, whatever. But this only works because the hub knew about the button press to begin with.
Central Scene Commands. Love this. This is the newest method of this type and it only came in a couple years ago. With this, when you press a button on the device, it sends a scene number to the hub. ( that’s what the “central” means – – note that this is different than the older “scene controller” command sets.) It’s then up to, again, a smart app to decide what to do with that scene number. But again, you can do pretty much anything SmartThings can do, turn on a switch, change the mode, etc.
Why is this so much better than association? Again, a couple of technical reasons, but mostly because it gives you much more precise information. It’s what enables a homeseer wall switch, for example, to do single tap, double tap, and triple tap for both top and bottom of the switch.
Three) Basic commands without Association. This is the oldest method and it is what the Wayne dalton device uses. As soon as you see “controller replication” on a handheld remote but you don’t see Association, you can be pretty sure it’s not going to work very well with SmartThings. Why?
Because devices using this method don’t tell the hub when the button is pressed. They tell some other device directly to perform its “basic” command. (That’s a Z wave term in this context). There’s no way for the hub to know that the message was sent.
The other device must be zwave and must have a basic command which is useful to you. That’s pretty limited. So, yes, You can use it to get toggle a nearby zwave device on and off–but when you do, the SmartThings hub won’t know that you did it, so your statuses will all get out of sync.
Anyway, all of that is to say that you cannot make the Wayne dalton device work like a minimote. They don’t use the same Z wave command sets. In fact, you can’t really do anything with the Wayne dalton device at all from SmartThings except add it to your network. After that, depending on the capabilities of the device, you might be able to set it up to toggle some nearby Z wave devices on and off, but if you do, SmartThings won’t get the status of them. And you might not be able to set it up at all, there’s some complicated technicalities regarding that.
So… It’s basically a third-generation device and we’re now in the fifth generation of zwave and on top of that SmartThings is a multiprotocol platform. There may be some people who will find a use for it, but you won’t be able to make it work like a minimote or other button controller, it just doesn’t do the same things.