The Govee API for segments can only specify brightness and color, rather than power state for the segment.
However, Home Assistant's Light entity assumes that there is a power state control for all lights, so when the entity is made available to Home Assistant it shows up with a power control.
Consequently, the power control for a segment does nothing and cannot be removed from the Home Assistant UI for the light entity.
Govee to MQTT merely passes your control requests on to the Govee device, and what happens next depends upon Govee. Some devices are more flexible than others. For example, some devices cannot set a segment brightness to 0, while others have their individual brightness bound to the brightness of the overall light entity.
Govee to MQTT has no way to control this device-specific behavior.
The Govee API doesn't support returning video effects, so they are not made available in the list of effects for a light.
What you can do to make video effects available in Home Assistant is to use the Govee Home App to create either a "Tap-to-Run" shortcut or a saved "Snapshot" that activates the desired mode for the device.
Then, go to the "Govee to MQTT" device in the MQTT integration in Home Assistant and click the "Purge Caches" button.
- Tap-to-Run will be mapped into Home Assistant as a Scene entity.
- Snapshots will appear in the list of Effects on the device itself.
This suggests that there is a problem with (re)registering the entity in Home Assistant.
There may be more information available in the Home Assistant logs. Look for
log entries that reference gv2mqtt or mqtt. Please make a point of
collecting that and reporting an issue.
You may also wish to try deleting the device(s) from the MQTT integration in Home Assistant, then going to the "Govee to MQTT" device and clicking the "Purge Caches" button to see how the situation evolves.
Check out this page for more details on supported devices.
As is explained in this page, there is little direct knowledge of specific devices in this software, which acts as a bridge into Govee's documented and undocumented APIs. There isn't anything practical that can be done here to directly control a device that isn't supported by Govee's APIs.
Some Govee lights support a speed control for some of their effects. For those devices, govee2mqtt will create an "Effect Speed" number entity alongside the light entity in Home Assistant. Set it to a value between 1 and the number of available speed settings while an effect is active to change its speed.
A few things to be aware of:
- The Govee Platform API has no way to set effect speed, so speed changes are sent via the LAN API when the device is reachable on your local network, falling back to the IoT API.
- Speed support is determined by the scene catalog that Govee publishes for each device model; if none of the scenes for your device advertise speed control, no "Effect Speed" entity will be created for it.
- The number of available speed settings varies from scene to scene; if you select a speed setting that exceeds the range for the active scene, the closest available setting is used.
- Not all device models use the scene parameter format that this feature understands; panels and other non-strip style devices typically won't expose the entity even if their scenes appear to support speed.
Govee device IDs are not network MAC addresses. For some devices the device ID is a superset of the BLE MAC for the device, but if you look carefully you'll see that the device ID is too large to be a MAC.
Look at this page for more details on the LAN API and things you can try.
This error appears to be returned from Govee when trying to use the Platform API with devices that are BLE-only and have no WiFi support. Please file an issue about this so that we can add an entry to the quirks database.