Anyone with shelly (dimmer) devices seeing weird behaviour like this ?
I have written an appdaemon app that changes the brightness of a shelly bulb according to some criteria that is out of scope here.
The problem at hand is when I change the BRI from x to y on the shelly bulb then it decides to turn itself off for a few seconds or so and then turn itself back on with the expected new brightness value.
This only happens periodically
Today I witnessed it first hand.
appdaemon app logs:
2021-02-25 10:24:54.823219 dimmable light light.bathroom_spots found at bri=234
2021-02-25 10:24:54.908820 adjusting light 'light.bathroom_spots' to bri level='245'
2021-02-25 10:24:55.660187 on_light_turned_off called. old='on', new='off', attrib='state', entity='light.bathroom_spots'
2021-02-25 10:24:55.684743 on_light_brightness_changed. old='234', new='None', attrib='brightness', entity='light.bathroom_spots'
2021-02-25 10:24:57.270723 on_light_brightness_changed. old='None', new='244', attrib='brightness', entity='light.bathroom_spots'
2021-02-25 10:24:58.631870 on_light_turned_on called. old='off', new='on', attrib='state', entity='light.bathroom_spots'
So I intially log the current BRI level of the shelly dimmer 2 bulb, which is 234
Then I call : await self.call_service(âlight/turn_onâ, entity_id = âlight.bathroom_spotsâ, brightness=244)
obviously in order to set the BRI level to 244
this results in the bulb visually turning itself off for a few seconds, then only to turn it on again and settle for BRI=244.
all this happens within a few seconds
This can be seen in the logs as well.
Iâm using a shelly dimmer 2 with beta FW 20210122-155640/v1.10.0-rc1@00eeaa9b
cloud turned off.
using shellyforhass integration vers. 0.2.2 beta 2
is it a CoAP bug ? if then where? in shelly codebase or in shellyforhass ?
Is MQTT any better I wonder ?
Or maybe the bultin integration in hass ?