Closed sommer closed 2 weeks ago
Any update on this issue as it already drafts a solution?
I did some fix of the on off behavior with this PR https://github.com/openhab/openhab-addons/pull/14373. Since this change you can control the the brightness with a percentage value of 0 or via a switch. If the light blub is conctoled via fritz box gui or app its also showed in openhab in a way that it brightness is 0 when its off. I reccomend to cloase this bug.
(Fixed with openhab 4.0 or later)
From what I understand, the FRITZ!DECT 500 Color LED lightbulb has two separately controllable parameters:
Changing either is done using separate commands sent to the AHA HTTP interface.
As of version 3.2.0, the openhab-addons expose both as a single channel and, depending on which command is sent to the channel (on/off vs. a new brightness) either parameter is changed.
This does not mesh very well with the way OpenHAB seems to think (a light that is "off" has zero brightness; a light that has nonzero brightness is "on").
Expected Behavior
From my limited understanding, I can think of two ways to work around this:
Current Behavior
OpenHAB UIs show lights that have been switched "off" as "on" (because they still have nonzero brightness). Dimming a light to 0% in OpenHAB UIs does not switch the light "off" but only reduces its brightness to zero, confusing other apps controlling the same bulb.
Possible Solution
To illustrate the second option (single channel control of bulb), the following (crude) code seems to achieve this:
Steps to Reproduce (for Bugs)
avmfritz:HAN_FUN_COLOR_BULB
, make sure to use AIN that ends in-1
(the one without seems to be a dummy device, as also evidenced by itsfunctionbitmask=1
(no functions outside of, well, being a HAN-FUN device)Switch
andDimmer
items to itscolor
channelContext
Your Environment