search

ebaauw / homebridge-nb

Homebridge plugin for Nuki Bridge
Apache License 2.0
51 stars 3 forks source link

Heartbeat, Drift, Port #88

Closed Peda-s closed 1 year ago

Peda-s commented 1 year ago

I've got problems with heartbeat and drift. there are two nukes registered to this bridge. Hb lost the bridge these days after timeout.

I tried to change the port to 8094. Nuki Bridge did it, but the plug-in is still on 8080 even after restart of hb.

any idea what to do?

[21/09/2022, 00:06:03] [Nuki] Nuki_Bridge_3509296F: warning: request 1: error: connect ECONNREFUSED 192.168.0.17:8080 [21/09/2022, 00:06:03] [Nuki] warning: heartbeat 2, drift 1900 [21/09/2022, 00:06:03] [Nuki] warning: heartbeat 3, drift 906 ... [21/09/2022, 00:21:11] [Nuki] warning: heartbeat 911, drift 1051 [21/09/2022, 00:21:41] [Nuki] warning: heartbeat 941, drift 1100 [21/09/2022, 00:22:11] [Nuki] warning: heartbeat 971, drift 1053 [21/09/2022, 00:22:41] [Nuki] warning: heartbeat 1001, drift 1059 [21/09/2022, 00:23:11] [Nuki] warning: heartbeat 1031, drift 997

ebaauw commented 1 year ago

Homebridge NB should handle a changed IP address or port of the Nuki bridge. Double-check with nb discover that the Nuki bridge has registered with the Nuki server under the new port. If not, try to power-cycle Nuki bridge.

The drift messages indicate that the heartbeat occurs a second late. Typically this means something is blocking NodeJS, e.g. by doing synchronous I/O. Are you running Homebridge NB in a child bridge or as only plugin? Maybe it’s caused by Homebridge NB having lost the connection to the Nuki bridge?

Peda-s commented 1 year ago

Another reboot of Nuki bridge changed the port. After setting Nuki as a child bridge everything seems to be ok. I will have a look what's happening after some days.

ebaauw commented 1 year ago

Weird. Mine has been running on 8080 since I got it.