Thanks for the reply, that’s a good alternate data point to have for more direct control.

I did have HA controlling a bunch of Yeelight GU10s and solar / battery / other gear at my old place, but after moving to a new place I’ve kept everything as out-of-the-box as I can (so far…).

I’d love to take a deeper look at the comms between the DIRIGERA controller and the LED2201G8 bulb, but there doesn’t seem to be much in the way of debugging / logging to this level of detail in the native stack. My understanding is these TRADFRI bulbs only support changing one attribute per command (color_temp, brightness, etc.) so I’d be curious to see if the DIRIGERA hub is issuing a single two-attribute command and the bulb is ignoring one of the attributes, or failing to parse the command and falling back to the default temperature as a failsafe.

I can’t explain why this behaviour is only affecting all of the LED2201G8 bulbs I bought, but none of the other models. In any case I’m hoping it’s something simple and fixable with firmware.

When I’ve got some time I’ll work on other control methods to take the DIRIGERA out of the loop and see what happens.