homebridge-nb
homebridge-nb copied to clipboard
ebaauw
Bridge not reachable. How long button push
I followed instructions. And got to the "push bridge button" . Fo how long? is it the long 10 second and flash light push or a simple push.
"and press the button on the Nuki bridge. The bridge should be discovered automatically. Pressing the button allows Homebridge NB to obtain a token (API key)." how long should I press button.
API is up and running in NUKI
But even after that I get this both from auto discovery and Aldo after using using terminal and pushing the button shortly **** homebridge log****
20/07/2022, 11:17:11] [Nuki] warning: 192.168.1.28: request 1: GET /info [20/07/2022, 11:17:11] [Nuki] warning: 192.168.1.28: request 1: error: timeout after 15 seconds [20/07/2022, 11:24:47] [Homebridge UI] Starting terminal session [20/07/2022, 11:26:54] [Nuki] warning: 0.0.0.0: request 1: GET /info [20/07/2022, 11:26:54] [Nuki] warning: 0.0.0.0: request 1: error: connect ECONNREFUSED 0.0.0.0:8080 [20/07/2022, 11:34:02] [Homebridge UI] Terminal session ended.
Homebridge Terminal
Node.js Version: v16.16.0 Node.js Path: /opt/homebridge/bin/node Plugin Path: /var/lib/homebridge/node_modules
Update Node.js: hb-service update-node
Install Plugin: hb-service add homebridge-plugin-name Remove Plugin: hb-service remove homebridge-plugin-name
pi@homebridge:/var/lib/homebridge $ nb discover nb discover: 0.0.0.0: request 1: GET /info nb discover: warning: 0.0.0.0: request 1: error: connect ECONNREFUSED 0.0.0.0:8080 [] pi@homebridge:/var/lib/homebridge $ nb discover nb discover: 0.0.0.0: request 1: GET /info nb discover: warning: 0.0.0.0: request 1: error: connect ECONNREFUSED 0.0.0.0:8080 [] pi@homebridge:/var/lib/homebridge $ nb discover nb discover: 0.0.0.0: request 1: GET /info nb discover: warning: 0.0.0.0: request 1: error: connect ECONNREFUSED 0.0.0.0:8080 [] pi@homebridge:/var/lib/homebridge $
Now I get this. my range is 192.168.1.x
pi@homebridge:/var/lib/homebridge $ nb discover nb discover: 10.247.1.153: request 1: GET /info nb discover: warning: 10.247.1.153: request 1: error: timeout after 5 seconds [] pi@homebridge:/var/lib/homebridge $
It’s just a short press. Doing a long, 10s, press enables BLE on the bridge, so it can be configured from the Nuki app. I’m not sure, but I wouldn’t be surprised if that suspends the HTTP server and screws up the registration with the Nuki server.
Could you please run nb -DD discover? Normally nb discover checks that it can reach each of the Nuki bridges returned by the Nuki server. I think the Nuki server has registrations from some of your Internet neighbours that share or previously used your public IP address. Please check if the response from the Nuki server includes the bridgeId for your Nuki bridge. If not, power cycle your bridge to refresh the registration with the Nuki server.
did por cycle and then
pi@homebridge:/var/lib/homebridge $ nb -DD discover nb discover: nuki server: request 1: GET /bridges nb discover: nuki server: request 1: GET https://api.nuki.io/discover/bridges nb discover: nuki server: request 1: response: {"bridges":[{"bridgeId":1862020107,"ip":"192.168.1.28","port":8080,"dateUpdated":"2022-07-20T10:43:01Z"}],"errorCode":0} nb discover: nuki server: request 1: 200 OK nb discover: 192.168.1.28: request 1: GET /info nb discover: 192.168.1.28: request 1: GET http://192.168.1.28:8080/info nb discover: 192.168.1.28: request 1: GET /info nb discover: warning: 192.168.1.28: request 1: error: timeout after 5 seconds [] pi@homebridge:/var/lib/homebridge $
The good news: the bridge seems to have registered correctly and the Nuki server returns its info.
The bad news: there's no response when nb tries to connect to your bridge. You could try nb -DD discover -t 30 to use a longer timeout. If that doesn't help, there's probably a firewall on your server or in between your server and the Nuki bridge blocking the traffic.