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-work]

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