Hi, I’m a current Smart Things and Hue owner but I’ve just been sent a whole pile of Devolo’s Home Control gear to test for a website review. There’s a Starter Pack, Smoke Detector, Motion Sensor, Wall Switch, Radiator Thermostat, Room Thermostat, Key fob switch. It’s all Z-Wave stuff AFAIK.
I’m certainly no developer but if there’s anything I can do to help check out compatibility between Smart Things and Home Control, let me know. I’ll be having a tinker myself, but I’m not experienced in the development side of things.
Just a quick update…my review of the Devolo Home Control is here:
Overall, it’s a good first attempt with a few rough edges.
I don’t cover cross-platform compatibility but so far I’ve not had much luck - while everything pairs, typically SmartThings doesn’t quite know what it’s paired with. For example, the motion sensor came across as a door open/close sensor that was permanently open. Themostat worked as a thermometer but didn’t pick up the target temperature. Stuff like that.
For me, it kind of illustrates what’s broken with home automation. Stuff might be Z-Wave but unless your controller knows about the device, you seem to be a bit screwed. I kind of feel that each Z-Wave device ought to be able to publish what its capabilities are, say, like an XML schema. I’m certainly no expert in the technical side so if I’m talking nonsense, feel free to educate me.
Actually, the devices already do. In addition, when any Z wave device is certified, a “conformance statement” is published on the official Z wave alliance website that lists exactly which commands it can both receive and send.
So the issue is down to each controller as far as which commands they want to support. The zwave standard only requires that A controller be able to send a “basic” (that’s an official Z wave term) command, which basically means an on/off.
For example, there are several zwave command sets that SmartThings does not support, including controller replication. There are other zwave command sets that the SmartThings controller can receive, but it doesn’t do anything with them. So you have to write your own device handler to process them. Central scene commands are a good example of this.
The devolo wall controller, for example, will not work out of the box with smartthings because it uses central scene commands. However, @AdamV has written a custom device handler which works very well with it.
First, the FAQ on how custom device Handlers work in the SmartThings system:
And here, a link to the custom code that would make the DeVolo wall controller work with SmartThings:
So while SmartThings may not support as many Z wave devices straight out of the box as some other systems, it offers customers a really unusual degree of flexibility to add their own device handlers, thus significantly extending device choice.