Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on HA restart - async_forward_entry_setup #52

Open
ScrewLooseDan opened this issue Sep 22, 2024 · 0 comments · May be fixed by ScrewLooseDan/apex-ha#1
Open

Error on HA restart - async_forward_entry_setup #52

ScrewLooseDan opened this issue Sep 22, 2024 · 0 comments · May be fixed by ScrewLooseDan/apex-ha#1

Comments

@ScrewLooseDan
Copy link

I'm using the latest version (1.15) via HACS, and I'm getting the following errors on restart of HA:

Detected that custom integration 'apex' calls async_forward_entry_setup for integration, apex with title: Apex Controller (192.x.x.x) and entry_id: xxxbfb85034cxxxca1b7876137a72xxx, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/apex/__init__.py, line 63: hass.async_create_task(, please create a bug report at https://github.com/itchannel/apex-ha/issues

Detected code that calls async_forward_entry_setup for integration apex with title: Apex Controller (192.x.x.x) and entry_id: xxxbfb85034cxxxca1b7876137a72xxx, 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.

My HA versions:

Core 2024.9.2
Supervisor 2024.09.1
Operating System 13.1
Frontend 20240906.0

I didn't see this reported elsewhere, my apologies if I missed it.

If you need more information, let me know.

@ScrewLooseDan ScrewLooseDan linked a pull request Oct 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant