adaptive-lighting
adaptive-lighting copied to clipboard
Tradfri GU10 bulbs cycle brightness in line with update interval
Version information:
1.0.1.4
Description:
Adaptive lighting integration includes hue pendant, Tradfri GU10 white balance and Tradfri GU10 RGB and white spectrum.
Happens regardless of adaptive lighting integration settings (e.g. rgb-colour, separate commands, variable levels for brightness and colour). Does not always happen though, and individual bulbs can be affected without others in same integration being affected.
GU10 colour bulbs drop down to brightness level 3 or so (as reported by entity info in developer). Then shortly return to previous brightness as set by adaptive lighting. This cycles in line with adaptive lighting update interval - e.g. drop down every 90 seconds then shortly return to normal brightness.
Appears adaptive lighting integration is sending a command for brightness level 3 and then shortly brightness in line with normal level which means there is a gentle fade between these two levels in line with update interval.
To add, Tradfri GU10 updated via Tradfri gateway but controlled routinely through hue hub. Only some bulbs exhibit this behaviour, notably the RGB bulbs, and usually particular bulbs
I just installed some TRADFRI E12 bulbs and noticed behavior like this. They are connected via Hue bridge.
This sounds super weird. Could you attach a debug log please? :)
If you're using these IKEA Trådfri bulbs with Adaptive Lighting: set the "Transition time when applying a change to the lights" to 0.
Bulbs themselves have some small transition time internally (at least mine do) so the Adaptive Lighting still transitions smoothly.
Now for more details:
I have the same issue with IKEA Trådfri E27 bulbs, connected to Sonoff Dongle-E w/ zigbee2mqtt. It starts happening when I enable "Adapt Color" switch, but doesn't happen when I only enable "Adapt Brightness". Nothing weird in AL or Z2M debug logs.
I dug deeper and found that I can reproduce this behavior manually by repeatedly sending the same light.turn_on
payload to the bulb. It has to include transition
and color_temp
value. Also, set the brightness to some lower value, as it will be more noticeable.
service: light.turn_on
data:
transition: 1
color_temp: 300
brightness_pct: 35
target:
entity_id: light.bedroom
If you remove transition
or color_temp
from the payload, then it stops happening. I guess that the bulb firmware has a bug in interaction of transition and color_temp, which affects the brightness somehow. Since Adaptive Lighting is often sending similar values, it exhibits the issue.
If someone else confirms that this is a Tradfri bug, then this issue can be closed, since it isn't related to Adaptive Lighting, but rather the firmware.
Thanks @VS-X - I never got round to looking into this more and just set it to update once only on turn on. Today I've changed my Gu10 specific integrations to have a 0 transition time and prefer rgb, seems OK so far. I had wondered if color-temp was part of the issue, I realised that I had hue bulbs and tradfri bulbs sharing integrations, with tradfri bulbs being asked to change to colour temps outside their possible parameters. Once I changed this, I thought this had helped too.
@RubenKelevra I suppose you can close this if there's no workaround here - unless it's not possible to eliminate transition time totally in current release...?
Sorry for all the links/unlinks here I've been getting confused on which issue is which.
This should be helped by #460 as it'll check if a transition is not 0 before appending any transition to the light.turn_on service data
I'm getting pulsing again with my Ikea GU10 bulbs, even using the recommended config of 0 Transitions and 5ms, 50ms or even 100ms, send_split_delay.
It did go away sometime ago, but I can't remember what I did, not do I know what happened to bring it back :D
I actually had two GU10s get killed yesterday, not sure if it was adaptive lighting but I believe it was a command that killed them rather than failure as they failed at exactly the same time following a light.turn_on command.
I'm also getting pulsing again on the other bulbs.
On Thu, 3 Aug 2023, 06:55 pqhf5kd, @.***> wrote:
I'm getting pulsing again with my Ikea GU10 bulbs, even using the recommended config of 0 Transitions and 5ms, 50ms or even 100ms, send_split_delay.
It did go away sometime ago, but I can't remember what I did, not do I know what happened to bring it back :D
— Reply to this email directly, view it on GitHub https://github.com/basnijholt/adaptive-lighting/issues/207#issuecomment-1663333107, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATQTKPRPF55PHKEUEPWNTGTXTM4MDANCNFSM5FXMD5UA . You are receiving this because you authored the thread.Message ID: @.***>
I'm also encountering this, although I have an older version of this plugin due to my old HA version. I've just set the transition time to 0, so will monitor if that fixes it for me. Rather obscure issue to figure out I suppose. Any ideas on what's causing this, as AL is not changing the brightness (AFAIK)?
@Bouke can you please share Screenshots of your config of AL?
AL does change brightnesses, if configured to do so. (there's a switch exported to HA to enable/disable brightness changes)
Do you use Z2M or HA's build-in ZHA or how do you address the Zigbee network?
I've ordered a Tradfri bulb to see what's going on. Will take 2-3 days until it's here.
@RubenKelevra the setting to change brightness is off:
Further settings of the configuration: (Note that I had what I think was default of 45 second transition time and 90 second interval)
I'm using deconz with a zigbee hardware module in my RPi.
[Copy pasting this message in a few recent open issues]
I just wanted to take a moment to express my heartfelt thanks to everyone that is active in this repo. Your contributions, from answering questions to addressing issues, have been invaluable. It's amazing to see how supportive and helpful our community is!
Adaptive Lighting is all about enhancing your living spaces with smart, sunlight-responsive lighting. We've had quite a few discussions and open issues recently, and I see this as a positive sign of our community's engagement and growth. If you come across anything in the documentation that's unclear or if you have suggestions for improvement, please don't hesitate to share!. Your feedback is crucial for making Adaptive Lighting better for everyone.
On a personal note, I've recently welcomed twin boys into my family, which has been an incredible and life-changing experience. As you can imagine, my time is now more limited, and while I'm doing my best to keep up with the project, there may be delays in my responses. I appreciate your understanding and patience during this time.
Rest assured, I'm fully committed to addressing any bugs, especially those related to new Home Assistant updates, as swiftly as possible. I understand that many issues may stem from hardware limitations or misunderstandings about things like Zigbee groups. Your continued support and collaboration in helping each other out not only strengthen our community but also enhance the Adaptive Lighting experience for all.
Thank you once again for your understanding, patience, and support. Let's keep our houses well lit and adaptive for maximal enjoyment of life! 🌞🏠🌙