mighty hound
Bit of a weird issue here. I recently switched from using the Phillips Hue integration for my lights since they are requiring a login. I added the lights back through Matter and they work as they did before besides one weird issue I'm having in an automation. Basically at 5pm every day I check the temperature outside and automate the colors of my lights accordingly. I used to use scenes as it was the simplest way to get all of the lights to be the right colors consistently between activations.
After I switched from the Hue integration to Matter (yes I replaced the entities in the scene) those Hue lights no longer get triggered from the automation triggering the scene. Whats weird is when I activate that same scene manually, they behave on as expceted.
To troubleshoot I tried switching the automation to use light.turn_on service with the same as settings the scene but that produced the same results. All of the lights in that light.turn_on action come on as expected except these Hue lights. Weridly again - manually triggering the "run action" command within the automation editor produces the expected behavior.
You can see in my screenshots that the trace-timeline says the light.turn_on action did run. light.top_hue_play, light.middle_hue_play & light.bottom_hue_play should have been activated. But when I look at the logbook for the time when the automation triggered, I see all of the other lights turn on except these.
Any ideas? Thanks
