-
Notifications
You must be signed in to change notification settings - Fork 37
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
async_forward_entry_setup stop working in HA 2025.1 #193
Comments
Same in the logs. Posted below. entity_id is omitted by me.
|
Any chance to get this fixed @kvj? |
THat would be great if it could be fixed |
Hi, I have been looking at how this was solved in other integrations and this might do the job. I haven’t tested it though, but happy to install a beta any time. In for p in PLATFORMS:
hass.async_create_task(hass.config_entries.async_forward_entry_setup(entry, p))
return True by await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
return True |
@kvj do you continue Development here or should we fork and take over? |
Hey there, I've drafted a new release here: https://github.com/kvj/hass_nuki_ng/releases/tag/0.5.3 Please check that it's working as expected (I have no suitable hardware in hand at this moment). |
I am on 0.5.3 -> no logs errors encountered and also devices are shown correctly. I am using the Bridge and Opener. |
All good here too, using a Nuki Bridge and a Keypad. Thanks for the effort! |
HI, updated on 0.53 the previous error is gone i now get only this one: `This error originated from a custom integration. Logger: custom_components.nuki_ng.nuki Failed to update callback http://192.168.1.179:8123/api/webhook/nuki_ng_bridge_hook_01J4BHXPZ08WQ44V3TSHSBWTC0 During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
It says something about timeout. Can the lock or bridge be reached at all? |
The bridge is dropping randomly sometimes offline... I dont know whether this is an integration issue or a network/wifi issue...Right now it is reachable |
Hi @kvj I can also confirm that updating to 0.5.3, clears the log errors and appears to be working correctly. Thank you |
@kvj I am encountering some connection errors with the new beta, they were not existent in previous versions:
|
I get the exact same errors, brigde with lock gen 4 , lock gen 2 and fingerprint reader |
@kvj any update here? |
It doesn't look as if development is still taking place here. So you have to fix it yourself or switch to the core integration. |
Core integration has no automatic bridge webhook handling. |
@dm82m any update on what? You experience http connections timeouts to your bridge, which is kind of expected, as Nuki bridge is quite poor devices in terms of hardware inside. I don't see any reason how this could be relevant to the changes introduced in 0.5.3. |
I have not seen this issue before the changes but if you say it is not related I take that. Then you could release it? |
0.5.3 is the latest version. |
https://github.com/kvj/hass_nuki_ng/releases/tag/0.5.3 has been released last week |
Okay then we can close this issue here |
Home Assistant Log Warning:
Detected code that calls async_forward_entry_setup for integration nuki_ng with title: xxxxxx and entry_id: yyyyyyy, 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.
The text was updated successfully, but these errors were encountered: