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

Failed to update callback #22

Open
kordys opened this issue Dec 15, 2021 · 6 comments
Open

Failed to update callback #22

kordys opened this issue Dec 15, 2021 · 6 comments

Comments

@kordys
Copy link

kordys commented Dec 15, 2021

Hi,

I've just configured the integration and it looks like everything works as expected, but when checking the log I found several error messages:

2021-12-15 21:38:49 ERROR (MainThread) [custom_components.nuki_ng.nuki] Failed to update callback https://xxx.duckdns.org:xxxx/api/webhook/nuki_ng_bridge_hook_xxx Traceback (most recent call last): File "/config/custom_components/nuki_ng/nuki.py", line 268, in _update callbacks_list = await self.api.bridge_check_callback(self.bridge_hook) File "/config/custom_components/nuki_ng/nuki.py", line 129, in bridge_check_callback result = await self.async_json( File "/config/custom_components/nuki_ng/nuki.py", line 40, in async_json raise ConnectionError(f"Http response: {response.status_code}") ConnectionError: Http response: 400

Do you have any clue what should I check or where can be the issue? It looks like the webhook is created automatically by the integration os I don't know where and what to check.

Just for the record, I double-checked the bridge API token and it should be correct.

Thanks a lot.

@alexdelprete
Copy link
Contributor

I noticed you're using duckdns. The bridge doesn't support HTTPS, so it can't call back on an HTTPS url. I wonder how it seems to be working. Only polling...

@kordys
Copy link
Author

kordys commented Dec 16, 2021

Thanks for the reply. So the only chance is to use http optionally with local IP address only?

@kvj
Copy link
Owner

kvj commented Dec 16, 2021

@kordys yes, http url accessible by the bridge should be enough to resolve the issue

@dvdavide
Copy link

dvdavide commented Jan 8, 2022

Strange thing happened when configuring the integration from the external address. The integration would install normally, except I didn't get a field for "Home Assistant internal URL" in the config page, then the callback would fail and I would get an error in the log: "Failed to update callback https://192.168.0.20:8123/api/webhook/nuki_ng_bridge_hook_xxxxxx"

(note the https)

removed integration, tried installing again from local address, found the Internal URL field, corrected to http, and the callback now works fine. Leaving a note here in case someone finds themselves in the same situation, until this is fixed.

@alexdelprete
Copy link
Contributor

when configuring the integration from the external address. The integration would install normally, except I didn't get a field for "Home Assistant internal URL" in the config page

No strange thing: there's no field for internal/external, just the URL, it's up to you to pick the correct URL. Since the bridge doesn't support SSL, you need to choose the appropriate http URL.

@kvj
Copy link
Owner

kvj commented Jan 12, 2022

in 0.2.1 I've added hass URL pre-check, to avoid the confusion

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

No branches or pull requests

4 participants