Select.Scene returns "None" when light is turned off with a Scene active

[Crazypkr]

When turning a light off with a scene selected, select.scene will return "None". This is an issue as when you turn the light back on, the scene is still on but the select shows that its not.

[lasswellt]

This should be fixed in v2026.3.1. The integration now preserves the active scene in the selector when the light is powered off, so it correctly reflects the scene that will resume when the light is turned back on.

Could you update to v2026.3.1 and let us know if the scene selector behaves as expected?

[Crazypkr]

I am amazed how quickly you fixed this. Thank you so much.

Another problem I've noticed is that if I set a scene and then select "None", it still has the scene selected, it doesn't revert back to the original state before the scene. Is there a way to fix this?

Currently I have home assistant automations to do it, but it's tedious to create an automation for each light.

Thanks again for your hard work!

[lasswellt]

v2026.3.2 addresses the follow-up: selecting "None" in the scene dropdown now actually stops the scene on the device.

What changed

Previously, selecting "None" only cleared HA's internal state — the scene kept running on the device. Now it sends a color or color_temp command to exit the scene, since brightness commands alone don't override a running scene on Govee devices.

Restore behavior:

• If you had a color set before activating the scene, it restores that color
• If you had a color temperature set, it restores that
• If neither is available, it defaults to the midpoint of the device's color temp range (or white)
• Chaining scenes (Scene A → Scene B → None) restores the color from before Scene A

This works the same way for both regular scenes and DIY scenes.

To update: HACS → Integrations → Govee Cloud Integration → Update, then restart Home Assistant.

Please test and let us know how it works! Keeping this issue open for feedback.

[Crazypkr]

Hey! Thanks for trying to fix it quick. Unfortunately it doesn't set it back to the color, it only sets it to black.

Do you happen to have a discord channel?

[Crazypkr]

Hopefully these screenshot help with troubleshooting.

[lasswellt]

A fix for this has been released in v2026.3.4. The root cause was two bugs:

1. last_color lost during API poll — the coordinator created a fresh state object every poll cycle (~30s) without preserving the saved pre-scene color, so it was lost before the user could select "None".

2. Black fallback in async_clear_scene() — when rejecting RGBColor(0,0,0) (which the API returns during scenes), the code fell back to None instead of last_color.

Both are now fixed. Please update to v2026.3.4 and let us know if the issue persists — keeping this open for confirmation.

[Crazypkr]

Thanks again! Hopefully this will be the last bug I find.

If you are using group lighting (helper group light) and you switch the light, add a scene and then select scene None, it reverts to RGB(0,0,0)

Other than that, everything seems to be working!

[Crazypkr]

Just noticed that if that a color doesn't have a previous, it still doesn't select a middle ground light, it will automatically set it to 0,0,0.