Integration is broken in HA 2025.1

[alsFC]

Version of the custom_component

2023.11.1

Configuration

Configured in UI

Describe the bug

Loading and unloading of the integration and entities fails

Debug log

2025-01-04 00:23:54.614 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'govee' calls `device_registry.async_get_or_create` referencing a non existing `via_device` ('govee', 'Govee API (cloud)'), with device info: {'identifiers': {('govee', 'govee_govee_00:AF:DA:08:64:A6:37:EA')}, 'manufacturer': 'Govee', 'model': 'H6072', 'name': 'Lyra-Floor-Lamp', 'via_device': ('govee', 'Govee API (cloud)')} at custom_components/govee/light.py, line 67: async_add_entities(. This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/LaggAt/hacs-govee/issues
2025-01-04 00:23:54.614 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.govee.light.GoveeLightEntity'>) does not set supported color modes, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/LaggAt/hacs-govee/issues
2025-01-04 00:23:54.615 ERROR (MainThread) [homeassistant.components.light] 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
2025-01-04 00:23:54.638 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration govee with title: govee and entry_id: b2052361c79c7eb6f33d30ea0de69a8b, 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
Stack (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 227, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 707, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 678, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2033, in _run_once
    handle._run()
  File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2353, in async_forward_entry_setup
    _report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1199, in _report_non_awaited_platform_forwards
    report_usage(
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 234, in report_usage
    _LOGGER.warning(msg, stack_info=True)

Logger: homeassistant.config_entries
Quelle: config_entries.py:855
Erstmals aufgetreten: 10:24:31 (1 Vorkommnisse)
Zuletzt protokolliert: 10:24:31

Error unloading entry govee for govee
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 855, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/govee/__init__.py", line 83, in async_unload_entry
    await asyncio.gather(
          ~~~~~~~~~~~~~~^
        *[
        ^^
    ...<2 lines>...
        ]
        ^
    )
    ^
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 884, in gather
    fut = ensure_future(arg, loop=loop)
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 742, in ensure_future
    raise TypeError('An asyncio.Future, a coroutine or an awaitable '
                    'is required')
TypeError: An asyncio.Future, a coroutine or an awaitable is required

[Kri72]

Same issue here..

[tescophil]

I assume that's the end of this integration since there have been no updates in the past 2 years...

[Maurizion]

Same issue here. I tried by changing API key from Goove without any effect.

[ajouxie]

Same

[dietzi]

Same problem

[AlexisHutin]

Same problem

[lifecooler]

Same here

[shaybyrne-automate]

Time to ditch govee and switch to full WLED control, I think. This integration is really unstable.

[bj61251]

If people look into fixing this issue, either by forking this repository or whatever, might I recommend switching to using the LAN API for Govee products? This would obviously make them way faster, and remove the issue of limited API calls.

https://app-h5.govee.com/user-manual/wlan-guide

[dietzi]

The local API ist not supported by all products. So we have to use this integration

[bj61251]

Ah, yeah I see that it is limited, luckily I think it will work for me. I didn't even know it was added last year because I was using this custom one.

[KN0WLEGEND]

I knew this day would come. 😞

Until I find a permanent fix (local will not work) I’ve set up an input Boolean for each group of lights and then set up an automation that uses Google assistant SDK with the text “Turn on (device name in Google)”. It’s a hack but keeps the complaining down and continues to allow me to use HomeKit.🤷‍♂️ Unfortunately I use a lot of Govee smart lights with FP2 presence sensors😬

[craigo1975]

I knew this day would come. 😞

Until I find a permanent fix (local will not work) I’ve set up an input Boolean for each group of lights and then set up an automation that uses Google assistant SDK with the text “Turn on (device name in Google)”. It’s a hack but keeps the complaining down.🤷‍♂️ Unfortunately I use a lot of Govee smart lights with FP2 presence sensors😬

I'd really appreciate any more info to copy your hack please 🙏

[KN0WLEGEND]

I knew this day would come. 😞
Until I find a permanent fix (local will not work) I’ve set up an input Boolean for each group of lights and then set up an automation that uses Google assistant SDK with the text “Turn on (device name in Google)”. It’s a hack but keeps the complaining down.🤷‍♂️ Unfortunately I use a lot of Govee smart lights with FP2 presence sensors😬

I'd really appreciate any more info to copy your hack please 🙏

Steps

1. Link Govee Devices to Google (in Govee app profile > voice assistant > follow user guide for Google assistant

2. Add Google SDK to home assistant

3. Create input Boolean for device/group of devices

4. Create automations
   A) turn on
   i)when entity (select created input Boolean as entity) turns from any state to on THEN DO Google SDK: Send Text Command “Turn on (device name in Google)
   B) turn off
   i)when entity (select created input Boolean as entity) turns from any state to off THEN DO Google SDK: Send Text Command “Turn Off (device name in Google)

5. In devices navigate to HomeKit bridge (reload)

Voila

note the input Boolean will be available as a switch in HomeKit (not a light of any other entity)

[dietzi]

I knew this day would come. 😞
Until I find a permanent fix (local will not work) I’ve set up an input Boolean for each group of lights and then set up an automation that uses Google assistant SDK with the text “Turn on (device name in Google)”. It’s a hack but keeps the complaining down.🤷‍♂️ Unfortunately I use a lot of Govee smart lights with FP2 presence sensors😬

I'd really appreciate any more info to copy your hack please 🙏

Steps

1. Link Govee Devices to Google (in Govee app profile > voice assistant > follow user guide for Google assistant
2. Add Google SDK to home assistant
3. Create input Boolean for device/group of devices
4. Create automations
   A) turn on
   i)when entity (select created input Boolean as entity) turns from any state to on THEN DO Google SDK: Send Text Command “Turn on (device name in Google)
   B) turn off
   i)when entity (select created input Boolean as entity) turns from any state to off THEN DO Google SDK: Send Text Command “Turn Off (device name in Google)
5. In devices navigate to HomeKit bridge (reload)

Voila

note the input Boolean will be available as a switch in HomeKit (not a light of any other entity)

So you don't have the state of your LED's when activated by google or app or something else

[KN0WLEGEND]

I knew this day would come. 😞
Until I find a permanent fix (local will not work) I’ve set up an input Boolean for each group of lights and then set up an automation that uses Google assistant SDK with the text “Turn on (device name in Google)”. It’s a hack but keeps the complaining down.🤷‍♂️ Unfortunately I use a lot of Govee smart lights with FP2 presence sensors😬

I'd really appreciate any more info to copy your hack please 🙏

Steps

1. Link Govee Devices to Google (in Govee app profile > voice assistant > follow user guide for Google assistant
2. Add Google SDK to home assistant
3. Create input Boolean for device/group of devices
4. Create automations
   A) turn on
   i)when entity (select created input Boolean as entity) turns from any state to on THEN DO Google SDK: Send Text Command “Turn on (device name in Google)
   B) turn off
   i)when entity (select created input Boolean as entity) turns from any state to off THEN DO Google SDK: Send Text Command “Turn Off (device name in Google)
5. In devices navigate to HomeKit bridge (reload)

Voila
note the input Boolean will be available as a switch in HomeKit (not a light of any other entity)

So you don't have the state of your LED's when activated by google or app or something else

Correct just basic on/off control. It’s a hack to maintain usability until there’s a permanent solution. The hack I laid out is by no means a replacement.

[EvanWasHere-zz]

I literally have the worst luck.

I finally find time yesterday to spend about 5 hours programming Home Assistant for my new home with 30 or so Inovelli Blue Switches and 50 Govee 6" ceiling lights. I had each room/zone configured, could easily turn on/off rooms, dim lights, and change lighting of the rooms.

This morning I see the update for HA, install it, and it breaks everything.

Govee has not made Lan API an option on these ceiling lights and this integration hasn't been updated in 2 years.

I'm so screwed. My family, who was so impressed with all the features of the lighting yesterday, is back to yelling that the light switches dont work.

I'm just gonna break out some flashlights and candles and go into hiding for a while.

Edit: Restored to previous version by going to shell and inputting:
ha core update --version=2024.12.5

Everything works again after downgrading but my family has lost their trust. Still considering moving into that cave.

[dietzi]

You can restore your backup before Update and all will work fine again

[KN0WLEGEND]

You can restore your backup before Update and all will work fine again

Thank you for reminding me of this simple solution. All functionality restored in less than 2 minutes. tips cap

[zhvial]

Same issue. TV light doesn't work anymore :(

[JiriBalcar]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

[zhvial]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

Thank you. That worked for me!

[calielc]

Amazing @JiriBalcar , It did work for me as well.
Are you going to open a Pull request with the code?

[JiriBalcar]

Amazing @JiriBalcar , It did work for me as well.
Are you going to open a Pull request with the code?

Yes, but I would like to clean up the integration little bit. Is the Maintainer still active so the PR can be merged?

[JimBuzbee]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

Thanks! Works for me too. I'm not well-versed in HA integrations - will these changes to light.py survive HA updates?

[JiriBalcar]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

Thanks! Works for me too. I'm not well-versed in HA integrations - will these changes to light.py survive HA updates?

Yes it should

[cimeson]

I have switched my integrations over to a different integration. Supports both Local API (where available) and Platform API. Happy with the results, so far.

https://github.com/wez/govee2mqtt

[L00PERY]

If people look into fixing this issue, either by forking this repository or whatever, might I recommend switching to using the LAN API for Govee products? This would obviously make them way faster, and remove the issue of limited API calls.

https://app-h5.govee.com/user-manual/wlan-guide

LAN API is not an option for their smart switches. Personally using the integration for some H5080 switches.

[ur7x]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

Mostly works for me...Big THANKS!

Though there seems to be a bug on setting Kelvin Temp on my H6008 Bulbs.. As soon as you try to change the Kelvin Temp, the light.py crashes and no longer responds to any inputs. Reboot of HA brings it back. But a great stop gap solution.

If it helps here is the error
"Failed to perform the action light/turn_on. cannot access local variable 'color_temp_kelvin' where it is not associated with a value"

[Pacoboyd]

I moved to govee2mqtt today and it's working well as a replacement. Can use both LAN API for those devices that support it, but also API key for lights that don't.

https://github.com/wez/govee2mqtt

[KN0WLEGEND]

I literally have the worst luck.

I finally find time yesterday to spend about 5 hours programming Home Assistant for my new home with 30 or so Inovelli Blue Switches and 50 Govee 6" ceiling lights. I had each room/zone configured, could easily turn on/off rooms, dim lights, and change lighting of the rooms.

This morning I see the update for HA, install it, and it breaks everything.

Govee has not made Lan API an option on these ceiling lights and this integration hasn't been updated in 2 years.

I'm so screwed. My family, who was so impressed with all the features of the lighting yesterday, is back to yelling that the light switches dont work.

I'm just gonna break out some flashlights and candles and go into hiding for a while.

Edit: Restored to previous version by going to shell and inputting: ha core update --version=2024.12.5

Everything works again after downgrading but my family has lost their trust. Still considering moving into that cave.

Govee2MQTT is the answer. More functionality than this integration. Easy to set up. Up in 5 minutes after a restart.

[KN0WLEGEND]

I knew this day would come. 😞
Until I find a permanent fix (local will not work) I’ve set up an input Boolean for each group of lights and then set up an automation that uses Google assistant SDK with the text “Turn on (device name in Google)”. It’s a hack but keeps the complaining down.🤷‍♂️ Unfortunately I use a lot of Govee smart lights with FP2 presence sensors😬

I'd really appreciate any more info to copy your hack please 🙏

Steps

1. Link Govee Devices to Google (in Govee app profile > voice assistant > follow user guide for Google assistant
2. Add Google SDK to home assistant
3. Create input Boolean for device/group of devices
4. Create automations
   A) turn on
   i)when entity (select created input Boolean as entity) turns from any state to on THEN DO Google SDK: Send Text Command “Turn on (device name in Google)
   B) turn off
   i)when entity (select created input Boolean as entity) turns from any state to off THEN DO Google SDK: Send Text Command “Turn Off (device name in Google)
5. In devices navigate to HomeKit bridge (reload)

Voila
note the input Boolean will be available as a switch in HomeKit (not a light of any other entity)

So you don't have the state of your LED's when activated by google or app or something else

Officially moved to Govee2mqtt as my solution.

[MarkRMonaco]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

Thank you. I originally reverted back to 2024.12.5, but after replacing my light.py, I was able to go back to 2025.1.0 w/o issues.

[Noack1978]

With govee2mqtt my H6008 works again without problems

[Andurilll]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

This fixed it for me for now. Thanks you very much!

I have only a H605C TV Backlight. How to Check of it works with govee2mqtt?

[calielc]

Here you can find the list of Lan supported devices https://app-h5.govee.com/user-manual/wlan-guide

[Av4K100]

If anyone has Homebridge (i have to use it to implement my Govee fan into homeassistant) their integration of Govee doesn't seem to have been affected by the changes in Homeassistants January update and switching to using that for my tv lights seems to have fixed the issue temporarily if anyone else needs a workaround

[yvoictra]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

Nice! That worked for me also :-)

[TheS1ngularity]

Thanks guys for the support here!
I had the same issue and going through this thread, I wasn't aware of the govee2mqtt integration. I saw that it has more functionality so I decided to switch to it. Setup was ok, and my devices were discovered and were updating to the states I was changing from the govee app, however controlling was not working for them. I have no idea why, I can only assume it's because I'm using old H6163 strips - they don't have LAN functionality, older hardware.
Trying to turn them on/off was just not doing anything and I didn't see any error in the govee2mqtt log (after enabling tracing).

So I switched back to the old govee integration + the lights.py update by @JiriBalcar - Thank you very much!

If you want to troubleshoot my govee2mqtt issue, let me know what I should provide (I'm a bit lost when it comes to logs in HA tbh, there's the Log area in system, but only some integrations show up there, then there's the add-on Log view, so let me know where you'd like logs from).
Cheers!

[Mr-Wicket]

I moved to govee2mqtt today and it's working well as a replacement. Can use both LAN API for those devices that support it, but also API key for lights that don't.

https://github.com/wez/govee2mqtt

I only have the T2 TV Backlights so this was a easy switch for me. I am much happier with the MQTT integration as well since it gives me more options. Wish I had tried this a long time ago, thanks!

[LaggAt]

hey, long time no see ...
just trying to get my dev environment up, anyone here wants to step in as a developer? I really do not have the time.

[manuveli]

@LaggAt any chance for you to at least implement the quickfix that was provided above? Would really love to keep my automations. I used your integration a lot :-) Would like to avoid switching since this one was working perfect

[LaggAt]

still updating my dev environment - could you point me to the fix you mean?

[manuveli]

#199 (comment)

this is the comment I'm talking about. Seems like it worked for some.

[LaggAt]

#199 (comment)

this is the comment I'm talking about. Seems like it worked for some.

thanks, I'll add that to my todo list. Thanks @JiriBalcar for providing that. I also invest some time to look over the dependencies, to get them to the same version home assistant uses.

In the long term I need to find other developers who want to contribute - or - if this is working well - I could discontinue here and we switch all to the https://github.com/wez/govee2mqtt extension.
--> if someone did look into that - is there a disadvantage?

[buskeyl]

I did a quick fix, just replace /config/custom_components/govee/light.py with this: https://pastebin.com/SsqHmFQe

This integration would need some refactoring, it still throws some warnings in HA log.

Also worked for me! Big thank you. Don't know what you did, but glad you did it and shared!

Lee

[tescophil]

RE The MQTT extension, my experience of it was it was unreliable, which is why I switched back to this integration. Plus the fact that you have to run two addons (Govee MQTT plus the Broker) and the integration using several hundred megabytes of memory is kind of ridiculous just to turn a couple of LEDs on and off...

[LaggAt]

ok, understand. Then let's try to get this fixed for now.

[Dillton]

Hi @LaggAt.
I have tried several months ago govee2mqtt but switched back to your integration. Yesterday as a hotfix I did the same but my experience is basically the same as I tried the first time.
Simply the command execution or communication with the devices is at least on my side extremely slow. Not sure what takes so long what is the add-on doing I don't have much time to deep dive into it currently but it takes 2-3 seconds to simply turn on or off the device. With your integration this is a matter of miliseconds.
So yeah would be nice if someone could contribute here actively to keep the integration alive.

[JiriBalcar]

I also tried the Govee2Mqtt but I was not happy with slow responses. I prepared PR with that fix for @LaggAt (#200)

[mvoto]

Hey @JiriBalcar thanks for putting up a fix so fast!
@LaggAt can we have a new release for this fix?
What is the process of having a new release for this repo? Let me know if there's anything I could do to help

[LaggAt]

Hi, yea thanks to you all, I did miss this completely.
If I did anything right, this should push this out:
https://github.com/LaggAt/hacs-govee/releases/tag/2025.1.1

[JiriBalcar]

Yes @LaggAt it is out and working. Still complains in the logs for two issues. One I have prepared fix for, but it can wait. For the second one, I will try to look into it.

[mvoto]

UPDATE: I was able to pull out and test the local changes, if I didn't miss anything, my LED strips are working as expected, however my Aura Table lamp is not.
I configured the LOCAL API for the LED strip lights, the Aura lamp does not have this option and it's apparently not functioning(showing as unavailable).
A minor thing that I've also noticed from LED strip lights: when changing the color, it's not always reflecting the most recent color in the light indicator UI(the bar where you see the color and control the percentage)

[LaggAt]

Hm, code shoudn't change something for a single light. The second sounds like the issue, Govee changed how they rate limit there api on the way, when using the slider we try to send more requests as allowed very quickly. Also the rate limiting informations we show are garbage. Try to increase the pull interval to a higher value - i e.g. use 200 seconds interval for status update requests. This is one of the things never fixed.

@JiriBalcar your code changes are reasonable - are you interested in collaborator access?

[Mr-Wicket]

I'll see how the MQTT one holds up. I really only have the TV backlight automated ON/OFF when TV ON/OFF. This integration worked flawlessly for that since Govee's own built in "detect" doesn't seem to work. 🤷‍♂️ Anyways, I'll gladly switch back since the quick fix worked for me and I see you already pushed an update.
thanks for doing the awesome things everyone involved. 🤜🤛

[James62370]

Currently, this is the only addon that works with my aging Govee H6159 Lights. Govee claims that it supports the lan API, however after setting up govee2mqtt, I can confirm that it does not. Thank you for keeping this updated!