Lights do not always follow transition correctly with light.turn_on

[notownblues]

The problem

This is a very similar issue to #71076 but with light.turn_on rather than scene.turn_on.

Issue

I've had my Hue bulbs paired with Zigbee2MQTT but I decided to move them back to my Hue Bridge as the bulbs were making my Zigbee2MQTT network crash due to the repeater function on bulbs.

I've noticed that when I specify a transition in light.turn_on, the transition will work roughly 60-70% of the time but other times it will default to the 1s Hue transition. I'm not sure if it's an isolated issue specific to Hue or Home Assistant Core in general but I'm certain that the bulbs aren't at fault here as the transition was working perfectly fine with Zigbee2MQTT using groups.

Things I've tested to try fix the issue

1. I've tried to call light.turn_on with and without brightness including the transition - the issue persists with both
2. I tried to use scene.turn_on instead and the transition worked 100% of the time, but I don't want to use scenes for all my lights in this scenario as I use Adaptive Lighting
3. I tried to change the transition to another number (from 0.3 to 0.5) - issue persists
4. I tried to reboot Home Assistant - issue persists
5. I tried updating the Core - issue persists
6. I tried to turn off Adaptive Lighting - issue persists
7. I tried to reboot Hue Bridge - issue persists
8. I tried to change the Hue Bridge Zigbee Channel - issue persists
9. I tried to remove bulbs from the Hue App and re-add them - issue persists

I've ran out of other ideas to try solve this issue so I thought I'd report it as my guts are telling me this is a Home Assistant issue with the light service and transition not working consistently.

What version of Home Assistant Core has the issue?

core-2023.9.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Light.turn_on, Philips Hue

Link to integration documentation on our website

https://www.home-assistant.io/integrations/hue/

Diagnostics information

No response

Example YAML snippet

I use Node Red for all my automations and call HA services. Here's an example of a light.turn_on I have with the transition:

{ "brightness_pct":"100", "transition":"0.2" }

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @balloob, @marcelveldt, mind taking a look at this issue as it has been labeled with an integration (hue) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `hue` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign hue` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

hue documentation hue source _{^{(message by IssueLinks)}}

[blalor]

I'm having the same issue. I simply cannot get transition to work under any circumstances. At least with two different Wiz bulbs. I've attempted transitions to 100% with delays of 10, 30, and 100 seconds and the result is always that the light goes immediately to the target brightness with no transition. I can reproduce this with just the service call from the developer tools:

service: light.turn_on
data:
  brightness_pct: 100
  transition: 100
target:
  entity_id: light.sunroom_lamp

I also see nothing in the logs.

[marcelveldt]

You need to specify brightness if you want to use the transition parameter. Just tested and that works perfectly fine. What does not work is specifying transition without any (target) brightness, in that case the transition is completely ignored by the Hue bridge.

[notownblues]

@marcelveldt I do have the brightness specified when using the transition. The issue is that it doesn't work consistently, probably about 60-70% of the time. Please try to turn on a couple of times and you'll see the transition gets completely ignored sometimes.

[jim-edwards]

I am having the same issue with zwave devices. It worked perfectly fine previously, but stopped working in the last few months.

[marcelveldt]

I tried reproducing this issue many, many, times and not a single time the transition was not respected.

I notice that you are running the (custom) Adaptive Lighting component. Please disable that component and test again.

[notownblues]

Hi @marcelveldt

That's interesting, thanks for confirming. Will check by disabling the component ASAP.

[marcelveldt]

Thanks, let me know your findings after you've done that.

[jim-edwards]

At least for the zwave case I am reproducing this issue with, I don't have adaptive lighting plugin installed.

[marcelveldt]

At least for the zwave case I am reproducing this issue with, I don't have adaptive lighting plugin installed.

This issue is about Hue lights. Maybe create your own issue for the z-wave related issue. If these 2 issues are somehow related on a global level, we can connect them later.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jim-edwards]

This is still an issue described above for z-wave based devices