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

Nuki is not working after updating to 2023.4 #90926

Closed
javiermartingonzalez opened this issue Apr 6, 2023 · 6 comments · Fixed by #90927
Closed

Nuki is not working after updating to 2023.4 #90926

javiermartingonzalez opened this issue Apr 6, 2023 · 6 comments · Fixed by #90927
Assignees

Comments

@javiermartingonzalez
Copy link

The problem

After updating this morning to Home Assistant 2023.4, the Nuki integration is Unavailable, and the log is showing the following error:

2023-04-06 12:58:13.567 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 1B3EE11A for nuki
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/nuki/__init__.py", line 155, in async_setup_entry
    hass_url = get_url(
  File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 167, in get_url
    request_host = _get_request_host()
  File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 206, in _get_request_host
    raise NoURLAvailableError
homeassistant.helpers.network.NoURLAvailableError

What version of Home Assistant Core has the issue?

core-2023.4.0

What was the last working version of Home Assistant Core?

core-2023.3.X

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Nuki

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nuki/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Apr 6, 2023

Hey there @pschmitt, @pvizeli, @pree, mind taking a look at this issue as it has been labeled with an integration (nuki) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nuki can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign nuki Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


nuki documentation
nuki source
(message by IssueLinks)

@pree
Copy link
Member

pree commented Apr 6, 2023

I've created a bugfix PR. Thanks for reporting!

@javiermartingonzalez
Copy link
Author

javiermartingonzalez commented Apr 6, 2023

Hello, with new update I’m getting the following message:

Error registering URL for webhook a6a0046a94b06810092f87f14f064b20: HomeAssistant URL is not available

It seems something with new webhook options added, but it’s something wrong in my installation. It was working until new 2023.4 update released.

I have an HTTPS SSL installed to access it using a public domain, and it is added as external URL in the settings (internal URL is not available because internal URL have to be in the same domain as SSL). Is there any option to use the previous config or how can I fix it?

@pree
Copy link
Member

pree commented Apr 7, 2023

I created a seperate PR to be able to fall back to polling in case webhook registration fails.
If you're using a reverse proxy in front of HomeAssistant you should be able to mark the webhook path to not redirect to HTTPs, since the NukiBridge doesn't support SSL.

@javiermartingonzalez
Copy link
Author

Thank you, will test in next update.

I have in SSL folder a private key about a certificate for X domain, and I’m able to acess to HA using that domain but not the localhost (because if installed SSL, all conection need to be through that domain, otherwise SSL error is showed in browser)

It was working from years without no issues, so if the new implementation use both systems (old and new deppending of enviroment), I think it will work again.

Thank you for your effort!

@javiermartingonzalez
Copy link
Author

Tested adding your last PR code to custom_components to override core integration and working perfect with last changes!

Waiting next update to be added into core

Thank you for your work and fast solution!

@github-actions github-actions bot locked and limited conversation to collaborators May 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants