Fix/govee setup error#237
Conversation
Replaces deprecated call with async_forward_entry_setups() Resolves LaggAt#236
Replaces deprecated call with async_forward_entry_setups() Resolves LaggAt#236
Replaces deprecated call with async_forward_entry_setups() Resolves LaggAt#236
Big thanks! |
|
This PR is working as it should, please @LaggAt review and accept it. |
|
Duplicate of #235 ? |
no |
actually, seems yes to me! Looks like 4 PRs all addressing the same issue |
|
I'm starting to think it's time to start an official fork? |
Yup. I think we can consider it abandoned. Any volunteer on taking the lead? or at least can someone review all the PRs and choose one so others can use as a base? |
|
|
Duplicate #235 |
|
This has been resolved in the latest release. PR can be closed |
🔧 Fix: Replace deprecated async_forward_entry_setup with async_forward_entry_setups
🐛 Problem
Home Assistant Core (from version 2024.x) removed the method async_forward_entry_setup.
This caused the following error when setting up the Govee integration:
AttributeError: 'ConfigEntries' object has no attribute 'async_forward_entry_setup'. Did you mean: 'async_forward_entry_setups'?
✅ Solution
In custom_components/govee/init.py, the call was updated:
await hass.config_entries.async_forward_entry_setup(entry, component)
was changed to:
await hass.config_entries.async_forward_entry_setups(entry, (component,))
The method name is now correct.
component is passed as a tuple, as required by the updated API.
🔗 References
Fixes #236
Related to Home Assistant 2024.x API changes
🧪 Testing
Integration loads without error
Entities are set up as expected
No more warnings or crashes in the log