You’ll need to use a custom device type handler that exposes the parameters.
If you haven’t used custom code in smart things before, basically you’re going to copy the authors code and paste it into your account. Here’s the step-by-step FAQ:
The original FAQ information in this thread refers to the original smartthings architecture, which was in place through the end of 2022 and a little beyond. Custom code was written in the groovy programming language and ran in the smartthings cloud.
As of May 2023, you can no longer add new Groovy DTH‘s or smartapps to your smartthings account. So if you came here because of a link in an old forum thread, or on another site, I’m afraid the Groovy information is no longer usable.
All of this was replaced by a new architecture. Cloud to cloud integrations use the smartthings API. Hub connected devices, mostly Zigbee and zwave, now use “Edge Drivers,” written in the LUA programming language. Here’s the official announcement on those:
The process for using a custom Edge Driver in the new …
In this case, I think the following is the code you need, but it may depend on the exact model number.
I have been waiting about 2 years for a Fibaro Dimmer to reach the US. Now that it is here and I have my hands on one, I have to say that I am not disappointed. This is the in-wall dimming device that I have been waiting for.
[image]
Anyway, the SmartThings handler “Fibaro Dimmer” didn’t seem to work and I couldn’t find a community handler that worked with the US version so I put this together. It is also setup with the “button” capability and can send button commands. You have to enable the “Scene Activation Functionality in the device preferences”. The mappings will be posted below.
This device has 50 configurable settings. I have included what I thought were the most relevant ones, but if anyone thinks there should be more, just let me know. A description of them can be found in the…