LaggAt
Fix #234
Fixed by calling async_forward_entry_setups instead of async_forward_entry_setup, further changes to call inline with HA API changes to make it work under the new call, error logging for the call if it does fail
@LaggAt this should probably be picked up for review soon as the integration will break under HA 2025.6 without these fixes (or similar fixes if this isn't your preferred way of fixing this)
+1 - Can confirm it just broke the govee integration in 2025.6.0:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/govee/__init__.py", line 72, in async_setup_entry
await hass.config_entries.async_forward_entry_setup(entry, component)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ConfigEntries' object has no attribute 'async_forward_entry_setup'. Did you mean: 'async_forward_entry_setups'?
Is this repo still active? Looks like it's been over 5 months with no updates. Does an official fork need to be made with new maintainers?
Hello everyone. Just wanted to chime in and see what people think. I have forked the repo, and have made a PR to HACS to add my repo as the replacement for this one seeing as @LaggAt has only made one release here and hasn't been around since 6 months ago, and this issue was reported back in January. If this idea is fine with others, maybe comment on the PR, and also please sign up to be maintainers. I want to have an active community to keep the plugin stable and up to date. I am very active myself and can pull a lot of the weight for making sure merges and code review happens, but I am by no means well enough equipped to handle it on my own nor should the repo fall under a single maintainer again in case of absence.
This has been resolved in the latest release. PR can be closed https://github.com/LaggAt/hacs-govee/releases/2025.7.1
