Thank you for the pointers @krlaframboise. I have fully implemented this feature and it’s working well. The way I implemented it, the feature can be enabled and disabled for each button. I also made sure it wasn’t enabled by default so the existing behavior would be preserved during an update. Finally, I incremented the version number and release notes and submitted it as a pull request here.
It depends on the app, some ignore duplicate commands and others don’t. Another reason for having separate on and off actions is that not all electronics use the same button on the remote to turn the device on and off.
The device has the custom commands “pushButton1”, “pushButton2”, etc. which can be used with custom SmartApps like WebCoRE.
The built-in SmartApps don’t support custom commands so I also mapped the button numbers to dimmer levels. (button 1 = 10%, button 2 = 20%, etc.) If you want to push button 6 using Smart Lighting you can select the device as the light and set the dimmer level to 60%.
I’m pretty sure WebCore lists all the device’s custom commands as actions so if you select the device you should see options pushButton1, pushButton2, etc. It doesn’t matter how you select the device in the action so I’d probably just use the switch option.
Setting the dimmer level like I explained above should also work with WebCoRE.
I am using this to control my ZXT-310 and it works very well with the legacy app. In the new app, it does not work. I can see the device but it does not have any buttons. I just received an email from Smartthings is phasing our the legacy App. Do you plan on revising this so it works with the new App?
The device should be functional using SmartApps in the new mobile app as-is, but you won’t be able to program it or push the buttons from the device details screen.
They just released the documentation for custom capabilities and the new mobile app which would allow me to support that functionality, but that feature isn’t fully supported by the new mobile app yet so it will probably be a couple of months before I start implementing it.
Unfortunately this isn’t a popular device, I’m no longer using it in production, and I didn’t write it as an official handler for Remotec so I probably won’t get to it for a while…
They haven’t announced a date yet and the new mobile app needs to fully support the custom capability feature before they can get rid of classic.
The documentation for that feature was posted less than 2 weeks ago and it still says “NOTE: This CLI is currently considered an alpha release. It has currently has only a few specific features implemented and is a work in progress.” so I doubt the new mobile app will be ready until at least 1st quarter of 2021.
I’m hoping they’ll wait until it’s ready, but if they want to get rid of the classic before holiday shopping begins then I’m thinking they’ll do it around the beginning of November.
That’s pure speculation so for all I know it could happen a lot sooner.
There might be some tweaks I can provide you that would provide the basic functionality you need, but it depends on your answers to these questions:
How many buttons do you have programmed?
Are you using more than one endpoint? If so, are you using the companion app that creates a child device for each endpoint?
Are you just trying to push the buttons with the automations feature or do you also need to program them and/or push them from the device details screen?