New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SmartThings light brightness not changing #21173
Comments
This fix worked for me although I noted the original value in my DTH was
Thank you! |
Parent issue resolved! |
Thanks for this quick and dirty solution, worked perfectly for my custom device handler controlling ESP8266s flashed with WLED. |
Home Assistant release with the issue: 0.87.x
Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.): All
Component/platform: smartthings.light
Description of problem:
Some users have reported an inability to set/change the brightness of certain lights in HASS using the SmartThings integration. When the user changes the brightness, no error is logged in HASS, but the brightness of the light does not change. At the same time, an error will be logged in the SmartThings Groovy IDE similar to the following:
The problem is related to devices that use the following Device Type Handlers (DTH):
Additional information:
The root cause of the problem is that the affected DTHs do not properly implement the
switchLevel
capability. Specifically, they do not have asetlevel
overload that accepts 2 parameters, which is expected. An issue has been opened with SmartThings: SmartThingsCommunity/SmartThingsPublic#3986.Based on the outcome of the issue, an enhancement can be implemented in component dependency
pysmartthings
to maintain a list of non-confirming DTHs and invokesetLevel
with a single parameter.Please report additional DTHs that experience this issue.
Still experiencing issues? Here's the workaround:
A temporarily workaround is as follows (performed in the SmartThings Groovy IDE):
def setLevel(level)
method and modify it to:def setLevel(level, rate=0)
The text was updated successfully, but these errors were encountered: