Hey guys! I have never done this but am interested in learning how to write/modify a device handler. I started getting my feet wet last year with a little bit of smartapp development so now it’s time to get more up on the device handler side of things. Where are your recommendations for me as far as things to read/watch that could help me start down this road? I am currently interested in the Zigbee, Zwave side of devices. I have looked at the SmartThings Documentation that is available in the IDE thus far.
When you say you’ve looked at the documentation in the IDE, do you mean the developer docs? They’re available from a link on the top right of the first page of the forum, so from here, click on community in the upper right of the page, then on developer docs in the upper right of that page.
Is there Something specific you weren’t sure about, because those are pretty detailed.
Anyway, I’m sure the experienced coders will have much more to add, but here’s just a quick list of some of the resources for people just starting out:
I know I’ve mentioned this one before, but the following is my favorite thread as an example for how someone who didn’t have much experience with zigbee devices was able to write a zigbee device type handler with the help of the community. You can see each individual step they took any information they gathered at each point.
And here’s a doc listing all the zigbee home automation clusters.
Z wave is somewhat simpler because you don’t have to look at the raw data and it’s easy to look up the commands that any particular certified Z wave device supports by checking the official Z wave alliance products site:
So you can often write a device type handler for Z wave device without actually owning the device. That’s generally not true for zigbee.
The easiest way is to just start from an existing device type handler that uses the same command sets as the new device, and then modify as needed.
(And I know I say this a lot, but for the record, Zwave does not have “clusters.” That’s a zigbee term. Z wave has “command sets.” “Supported” command sets are the ones that the device can receive and act on. “Controlled” command sets are the ones that the device can transmit.
SmartThings decided that in their multi-protocol world they would call everything clusters. Drives me crazy every time. )
Official zwave public specification listing all the commandsets:
Note there’s no way to add support for a commandset to a device that doesn’t have it without flashing the firmware on that device. So it’s always best just to start with the official Z wave alliance description of the device and look at the commandsets that are listed there. Then you know what commandsets your DTH has to process.
And @zcapr17 has just released a “tweaker” DTH which can be used to discover the endpoints, associations, and supported zwave commandsets for any mains-powered zwave device. Very cool.
Official Developers Website
There’s also an official developers website, but I don’t know how many people use it. It’s mostly just pointers into the developer docs.
SmartThings did a presentation at the 2016 Samsung developers conference on how a device manufacturer would “onboard” their device to SmartThings. Which basically means creating a device type handler for it.
If you’re a visual learner and you like slides and pictorial representation, this might be helpful. It’s basically the same information as is in the developer docs, but, you know, with pictures.
Part 1: Z-Wave and Zigbee devices
Part 2: LAN devices
@slagle or @jim might have more suggestions for official resources.
Based on your link, it says to now use defaultState:true. I did a search now on “defaultState” to see examples to see it being used and what this means and the only thing that comes up is the description which is vague. The couple examples from SmartThings is using the old method
PS- I must have been working too late, I have no idea why the search didn’t hit on this? I tried “search” on it again this morning and it’s the first thing up.
Note that smartthings is in the process of moving to a new platform, new app, and new hub, so a lot is going to change. No timeline for when everything will be switched over, but it will be eventually. See the following thread for discussion of the new platform: