Govee Cloud Integration: Scene A/B variants resolve to the same scene

Third party integrations
1

Hi,

I’m running into a limitation with the Govee Cloud integration that makes scene-based automations unreliable.

Many built-in Govee scenes exist in A/B variants in the Govee app (for example Volcano A / Volcano B).
However, in Home Assistant both variants resolve to the same scene.

What happens:

  • Selecting Scene A triggers Scene B (or vice versa)
  • It’s impossible to reliably select a specific variant
  • Advanced automations (sports goal effects, alerts, intros) become unpredictable

This appears to be an API limitation:
Either the A/B variants share the same internal ID, or the Cloud API does not expose enough metadata to distinguish them.

Setup:

  • Device: Govee TV Backlight 3 Lite (H6097)
  • Integration: Govee Cloud Integration (latest)
  • Home Assistant Core: current version

Questions:

  • Is this a known limitation of the Govee API?
  • Has anyone found a workaround?
  • Is there any plan to expose unique identifiers for scene variants or allow DIY scenes to be triggered via the API?

I’ve also reported this directly to Govee support.

Thanks in advance.

2

If this is the custom integration you are referencing, you might want to ask here… Govee integration

1 Like