Open 6iorgio opened 1 year ago
Same here, ever since I've upgraded to 2023.3. I think it might be related to a change done with Python, upgraded to 3.11, but urllib3 still refers to 3.10
I had a similar issue. It just worked today…
Same here, ever since I've upgraded to 2023.3. I think it might be related to a change done with Python, upgraded to 3.11, but urllib3 still refers to 3.10
Hi gshlomi, do you still have the problem?
Same here, ever since I've upgraded to 2023.3. I think it might be related to a change done with Python, upgraded to 3.11, but urllib3 still refers to 3.10
Hi gshlomi, do you still have the problem?
No, my Nuki bridge just totally died, switched over to ESP32 emulation…
Same here, ever since I've upgraded to 2023.3. I think it might be related to a change done with Python, upgraded to 3.11, but urllib3 still refers to 3.10
Hi gshlomi, do you still have the problem?
No, my Nuki bridge just totally died, switched over to ESP32 emulation…
I'm not that expert. What's an ESP32 emulation and did you connect the Nuki lock to HA by it? Thank you.
Same here, ever since I've upgraded to 2023.3. I think it might be related to a change done with Python, upgraded to 3.11, but urllib3 still refers to 3.10
Hi gshlomi, do you still have the problem?
No, my Nuki bridge just totally died, switched over to ESP32 emulation…
I'm not that expert. What's an ESP32 emulation and did you connect the Nuki lock to HA by it? Thank you.
I had this communication error too and over the course of 5 mins I pressed the submit button every 20-30 seconds and then it connected one of the times
Just in case that helps anyone else
Logger: homeassistant.config_entries Source: helpers/network.py:206 First occurred: 1 aprile 2023, 21:19:56 (1 occurrences) Last logged: 1 aprile 2023, 21:19:56
Error setting up entry Nuki for nuki_ng 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 "/config/custom_components/nuki_ng/init.py", line 26, in async_setup_entry coordinator = NukiCoordinator(hass, entry, data) File "/config/custom_components/nuki_ng/nuki.py", line 345, in init url = config.get("hass_url", get_url(hass)) 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
gshlomi
diy you manage to use nuki_ng with technyon esp32 emulation?
Same here, ever since I've upgraded to 2023.3. I think it might be related to a change done with Python, upgraded to 3.11, but urllib3 still refers to 3.10
Hi gshlomi, do you still have the problem?
No, my Nuki bridge just totally died, switched over to ESP32 emulation…
I'm not that expert. What's an ESP32 emulation and did you connect the Nuki lock to HA by it? Thank you.
how do you use nuki_hub and retrieve bridge api token??
i had the similar issue, but when checking logs in HA error was 401 unauthorized. In my token I had ? as part of the token, when I changed token to only numbers and characters it started to work
I still have the same issue. Also I get 401 unauthorized error when trying to configure the integration. In my token there are only numbers and capital letters. Does anyone have further advises?
I guess the solution is quite simple:
After the bridge is restarted, you should try to configure the integration with your new token in Home Assistant.
Please give me a thumbs up, if the solution was helpful.
Hi there, same here (using RaspiNukiBridge as addon):
Log say:
Failed to get list of devices from bridge: HTTPConnectionPool(host='http', port=80): Max retries exceeded with url: //172.30.33.2:8080/info?token=e56f353daa61095e6fd1dacc4b0c8dcf48a5663b04f741f8880fcc05a472b729 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xde89e510>: Failed to establish a new connection: [Errno -5] Name has no usable address'))
But when I get into hassio's container and I curl the URL myself, it works.
Any ideas? When looking at the log above, it looks like the scheme is missing, although I provided it. I don't know if it's just for log formatting purposes or if the underlying python script actually removes the scheme, which would explain why it doesn't work...
I have the same problem as @bpolaszek. The only difference is that I'm using the regular bridge. Any ideas? :)
I guess the solution is quite simple:
- It might be that your mobile app and the bridge are still in maintenance mode and / or the (recently changed) API token is not finally stored on the bridge itself.
- Solution: Please leave the maintenance mode on your Nuki bridge. The app will tell you that the bridge will be restarted.
After the bridge is restarted, you should try to configure the integration with your new token in Home Assistant.
Please give me a thumbs up, if the solution was helpful.
This was the solution for me (using the regular bridge). Once the bridge is configured and you exit the maintenance mode, the bridge will reboot. Afterwards it connects as expected.
Hi,
I have a problem when trying to add Nuki Lock integration. I get this message:
The IP address of the bridge is correct and the bridge itself is fully functional. The Bridge API Token is also correct.
I'm running HA 2023.2.5 on Raspberry Pi 4
Here below the log. Thank you for help: