Govee matter lights unreliable with HA scenes?

Configuration
1

I’m trying to get a bunch of Govee matter downlights working with HA and facing frustrating inconsistency. When I interact with the bulbs one at a time through the entity UI (the thing with the big slider for brightness and the color disc for selecting your color) it’s quite reliable. When I put multiple bulbs into a scene they all update reliably when activating live edit mode,

The frustrating bit is when using the scene day to day, application of the scene is very hit or miss. Often lights will switch to the new state for brightness, but stay the color they were. Sometimes neither update.

More confounding is that when I look in the logs, it appears that the matter integration thinks that the update applied:

2026-01-04 22:19:08.605 DEBUG (MainThread) [homeassistant.components.matter] Got brightness 21 for light.downlight_studio_east_corner
2026-01-04 22:19:08.606 DEBUG (MainThread) [homeassistant.components.matter] Got color temperature 370 for light.downlight_studio_east_corner
2026-01-04 22:19:08.606 DEBUG (MainThread) [homeassistant.components.matter] Got color mode (hs) for light.downlight_studio_east_corner
2026-01-04 22:19:08.606 DEBUG (MainThread) [homeassistant.components.matter] Got hs color (0.0, 100.0) for light.downlight_studio_east_corner
same four lines per light in the scene…

My logs are full of all these seeming success messages when clearly the lights are staying white during this entire time (the scene should have them turning red to be in nightlight mode.

Has anyone else had problems with Govee matter lights like this? Any workarounds? I explored using a script to force apply and re-apply the values one at a time and had some success, however the approach had issues with either saturating my network during the application, or taking too long if I added enough delay. None of my other matter lights seem to have this problem - it just the difficult-to-replace downlights I just spent far more on than I want to give up on.

Interested in any sort of feedback or pointers on how to get this working.

2

I’m having the same issue with my gu10 matter light bulbs from govee. I have an automation which runs periodically to update the brightness and white temperature to match the day cycle. The automation makes one single light.turn_on call with the two attributes, brightness and temperature. As you, they only apply (chosen randomly) one of the attributes but report the entire operation successful. I asked ai some insight (so take it for what it is), it replied that some bulbs have a low budget chips which have a shot buffer and can handle few actions at a time.

I was able to fix the issue by splitting the turn on call into multiple ones (one per attribute) delayed by 100ms each. Now everything applies smoothly and reliably (but yes, you can slightly notice that one effect starts applying before the other).

I also reported the issue to govee, let’s see where it goes.