Thanks. That worked. I never would have figured that out and don’t recall reading that in documentation anywhere.
Now I have three “Button Controller” SmartApps installed, all with the same name. Too bad you can’t rename the SmartApp – I have to click into each one to see which NanoMote it is controlling. Now that they are all set up, it isn’t a big deal. Just a slight complication to maintenance ce down the road.
I used this device handler but used Webcore to program the remote instead. Seems to work more reliably than ABC and much more customization. I was able to create custom commands for a z-wave shutter controller and send these through WebCore when a button is pushed on the remote. Thanks alot!
This handler works with the 1 button model and the 4 button model so it uses the manufacturer information to determine which model it is. The manufacturer report sometimes fails to get reported during inclusion which is why it’s not aware it’s the 4 button model, but it should request the report the next time it wakes up and fix the number of buttons attribute.
Thank you for DTH. I ran into the problem after installation, old smartthings app I use didn’t show an option for push or held button in smartapps and seemed to assign action randomly. Looking into the code I saw that capability “Holdable Button” was missing from the code. After adding it to DTH everything was fixed. I recommend adding it to the guthub code.
Which apps were you using because I’ve written handlers for several button devices and I’ve always just used “Button”. (Hubitat apps require Holdable Button for the held command, but their button implementation is completley different.)
Holdable button has also been deprecated and is not listed as a capability in the new documentation…
I’m having the 4 button issue also, however it won’t update in the new app. In the classic app, as well as my SmartThings IDE, it does show as 4 button.
On the current app, it only shows one button, and does not give any options to define even what that button does, and under the log, no matter what button was pushed, it just say button pushed, instead of which one.
It looks like the new mobile app requires additional meta data and it also uses the new attribute “supportedButtonValues” so I just released a new version that has those things.
Unfortunately that doesn’t solve the problem of the button number not being displayed in the Activity History or the inability to set actions within the device details for a specific button number.
That functionality doesn’t appear to work in any of the built-in handlers either so I’m assuming ST doesn’t support it, but you can still assign actions for each button using the built-in SmartApps like Smart Lighting and Button Controller.
If you know of a built-in handler that supports assigning actions for each button within the device details of the new mobile app and/or displays the button number in the Activity History, let me know.