You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every other time or so, a light is not dimmed to XY% but instead turned on to 100%. It does not matter if Siri is used to set the XY% brightness or if it is done manually via the slider in the Home App. However, the latter works much more reliable than the former to set the XY% right in the first place.
Also, when dimming the light via an automation and/or shortcut, e.g. wake-up light starting at 5% brightness and increasing every 2 minutes, sometimes the light instantly turns to 100% instead 5% at the beginning.
Log output
No errors in the log.
While searching to solve this issue, I read in other homebridge plugin issue sections (and also in ones regarding HomeAssistant), that it might have something to do with how HomeKit handles commands and that the „on“ and the „XY%“ command are being sent at the same time which results in sometimes the one and sometimes the other gets executed first, leading to the results I described above. Some said removing the „on“ command and only use brightness might help but as I have no clue regarding how coding is done here, I just wanted to make you aware and ask for support.
Environment:
Shelly device: Shelly Dimmer 2
Plugin version: 0.19.1
Device running homebridge: Raspberry Pi 4B, Raspberry Pi OS Bookworm
The text was updated successfully, but these errors were encountered:
Describe the bug
Every other time or so, a light is not dimmed to XY% but instead turned on to 100%. It does not matter if Siri is used to set the XY% brightness or if it is done manually via the slider in the Home App. However, the latter works much more reliable than the former to set the XY% right in the first place.
Also, when dimming the light via an automation and/or shortcut, e.g. wake-up light starting at 5% brightness and increasing every 2 minutes, sometimes the light instantly turns to 100% instead 5% at the beginning.
Log output
No errors in the log.
While searching to solve this issue, I read in other homebridge plugin issue sections (and also in ones regarding HomeAssistant), that it might have something to do with how HomeKit handles commands and that the „on“ and the „XY%“ command are being sent at the same time which results in sometimes the one and sometimes the other gets executed first, leading to the results I described above. Some said removing the „on“ command and only use brightness might help but as I have no clue regarding how coding is done here, I just wanted to make you aware and ask for support.
Environment:
The text was updated successfully, but these errors were encountered: