My Govee integration had been working fine with two lighstrips but then stopped controlling the lightships for no obvious reason. I deleted the devices, reinstalled, deleted the integration and also tried deleting the lightships from the Govee app and reinstalling but they won’t work with HA now. After reinstalling the Govee integration the two lighstrips show up as devices in the integration but there are no entities so nothing to turn on or off. So they no longer work. Just wondered if anyone had any ideas how to resolve?
Same issue… its been working fine for years now last few days broken
Same for me. Mine quit working with HA core update
Seem to have the same issue. Was surprised to find out how recent your posts were. Devices but no entities.
Edit 2025.1 caused this
from RG3:
There is an error and a warning after updating to 2025.1. Here is the error:
Logger: homeassistant.components.light
Source: helpers/entity_platform.py:608
integration: Light (documentation, issues)
First occurred: 4:02:59 PM (1 occurrences)
Last logged: 4:02:59 PM
Error adding entity None for domain light with platform govee
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 608, in _async_add_entities
await coro
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 825, in _async_add_entity
capabilities=entity.capability_attributes,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/light/init.py”, line 1116, in capability_attributes
if LightEntityFeature.EFFECT in supported_features:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type ‘int’ is not iterable
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:234
First occurred: 4:02:59 PM (1 occurrences)
Last logged: 4:02:59 PM
and here is the warning:
Detected code that calls async_forward_entry_setup for integration govee with title: govee and entry_id: 03253c8412f4fcfa451933ab0b9ef227, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1, please report this issue
Has this been reported already? Are we at least expecting an imminent fix?
No word on that, but people seem to know about it.
Same Boat here, I have 8 govee Light bulbs. they were working fine, now since the update they are broken. Hopefully they get it fixed soon. I have a lot of Automations set up with these. 
Same problem here with the TV Lights H6199. I deleted the integration and replaced it with this slighty newer one “GitHub - wez/govee-lan-hass: Control Govee lights via the LAN API from Home Assistant”. After the configuration with the API, the TV Light is working again with HA.
2 Likes
I haven’t made any changes except the recent HA updates but the entities are now back and this is working again.
1 Like
I strongly suggest to use govee2mqtt
As mentioned on gitgub page above, the author moved development forces to govee2mqtt.
The biggest benefit is it’s independent from HA evolution. Also it supports all possible Govee protocols