Is anyone having an issue with new Govee devices. I added 4 Smart Bulbs, a Presence Sensor, and a Motion Sensor this past weekend. None of those have appeared in Home Assistant, but I have full control in the Govee App. None of them have LAN control either. I requested a new API key, thinking that maybe they only authorize the connected devices at the time of request. Now, none of my non-LAN control are working in HA. I reached out to Govee Support, and they said, “We tested the API and everything is working as expected. This must be a Home Assistant issue.” I doubt it’s HA as the previous API had everything, except the new devices listed above, working perfectly. Now I get a “Failed to Set up” on the Govee integration. Anyone have any ideas?
I also have the problem that not all devices are displayed in HA. I have seen in the codebase that an outdated API is being used. I am currently rewriting the code so that many more devices will be supported in the future. Unfortunately, this will probably not happen this year. But I will keep you up to date here.
I agree with you 100% in principle, but it would be helpful to point out an example of a similar pre-made product that is non-proprietary, at a similar price, and (as a bonus) includes outdoor waterproofing.
Govee just released a pressure sensor. I believe this is the first pressure sensor from a mainstream smart home company.
I’m guessing this device could only be supported by the Govee Bluetooth integration right? Well if that’s the case I hope it happens soon because I’d like to have an excuse to get it just to play around with it.
Added two new string lights version 2. Got a new api key but still only showing the 2 Govee devices I already had last year? Any reason new devices aren’t populating in HA?
Hello there! Upon installing the extension via HACS, I get the following error: {"message":"Invalid handler specified"}
Right now, I use HASS in a container, version is reported as 2024.12.2 (frontend being 20241127.7).
Unfortunately, nothing seemed to pop up in the logs, unless I need to configure HACKS itself as the debug log target?
Thanks and kind regards,
Ingwie
Does anyone know how to turn on a single segment of a lamp (ie H6076) leaving others turned off? I need it for night lighting.
I can achieve it in Govee app, even saving as a “color”, but Govee2Mqtt can’t set segments to inactive.
Maybe some workaround by creating a scene and then calling it from HA? However, I found no option to create a static scene from a single-lit segment.
Even though the segments are exposed as entities, they cannot be controlled by Home Assistant.
I reckon the only way to do it would be to create a DIY scene in the Govee app that only turns on the LEDs you need and see if there is a way to call that scene in HA.
I’m using Govee2MQTT and I’ve created DIY scenes for the Govee string and icicle lights that once saved will appear in the effects list after a restart of the Govee2MQTT addon.
actually they allow changing a section colour. But it’s impossible to turn selected segment off even by setting zero to all colours.
Anyway thanks for suggestion. I’l try to create diy scene
Just installed this integration and its working great for my spotlights and permanent lights, but the Outdoor Deck Lights (H7067) do not show up. I guess they’re not included in the API
Govee to mqqt ?
Hey guys… Just a heads up but this integration breaks in 2025.1 (currently in beta) because it uses deprecated methods that have been removed. The integration needs an update, but hasn’t seen a release in a year.
Can you share the error, we can put in a PR or fork it if need be to fix it.
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
Registratore: homeassistant.helpers.frame
Fonte: helpers/frame.py:234
Prima occorrenza: 02:58:47 (1 occorrenze)
Ultimo accesso: 02:58:47
Detected code that calls async_forward_entry_setup for integration govee with title: govee and entry_id: 01JGQGHDCA7RYAVPS8P9S8V8KC, 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
Man, I wish I would have known about this break. 
Experiencing this 2025.1 issue as well.
yes it doesn’t work anymore after the core update
Is the issue not resolved with the latest govee2mqtt release of reverting the local API scene stuff? I haven’t updated to 2025.1 yet.
If there is still an issue, the maintainer isn’t responsive, doesn’t really comment on issues or engage with questions or PR’s about things for govee2mqtt, so idk how well another PR will go. I’m not trash talking, just my observation and experience with a previous PR.
We can fork and fix, but that’s it’s own mess of another docker registry repo, building images and making sure people know what image to use. Not great, but doable.
I’ll take a look at that error you most recently posted (not awaiting an async callback in setup, which should be as simple as adding an await) if it is still causing issues, but then you’ll need to build your own docker images and figure out how to load the forked add-on and disable the original.
Yeah switched everything over to govee2mqtt last night and it works perfectly.