I went ahead and created an initial device handler for this. It’s nothing fancy at this stage, and simply maps the available 15 buttons on the One Touch as momentary buttons and associates them with the SmartThings hub. Both push and held states are supported for the buttons. I did not attempt to map the buttons as toggle or temperature controls.
I’ve posted a few device images and a quick mini-evaluation of the device here.
For some reason, the buttons don’t always work immediately after pairing, but in my testing, if you go back into the Z-Wave menu on the One Touch after pairing, this resolves the issue. This only needs to be done once.
Unfortunately, I was not able to get the device handler to change the button names on the controller itself. The One Touch appears to use the Z-Wave Screen Metadata Report, but from what I can find in the SmartThings Z-Wave Reference page, the current API appears to be a bit limited. Is there more to the API that I am missing, or does anyone have experience with setting device display fields and attributes using screen metadata?
It’s actually not a bad little device, but its $99 price tag might be more than a little questionable, especially when compared to running SmartTiles on a cheap Fire. It would have a bit more utility than standard button controller if I could get the button naming to work. Hopefully, this will at least be useful for those that have one of these controllers on hand after migrating over from Nexia