Hi People,
I’m still on 2.3.0 for the last few days and my lock refuses to upgrade (even after calling /fwupdate a few times). I also removed and inserted the bridge again.
Do I still need to become a beta tester? If not, should I do a factory reset or something to make it jump from an old version to 2.4.x immediately?
I’m also using my own made software which is calling /info and /list occasionally (30s). Could this be in the way?
Greetings from the Netherlands,
Gijs
2.3.0 is an intermediate version which then updates firmware to 2.4.x and also the Wifi firmware.
If it could update to this version it should also get to 2.4.x
Please try to deactivate your call and restart the bridge. It should try again itself after some time or you can call /fwupdate again and should see the bridge start blinking while downloading the updates.
Note that the process can take 15+ minutes and should not be interrupted or it will start again.
I have Software 1.13.1
How can I update?
FW version 2.x is for the second hardware revision of the bridge (Nuki Bridge hardware revision)
With the latest release it has again identical features to FW version 1.13.1
I have Nuki2.0 and Bridge V1. I have delays up to 40 sec until the bridge reports the state. Could this be the reason?
This should not take 40 sec with this combination. If possible please send a log directly from the bridge (see https://developer.nuki.io/page/nuki-bridge-http-api-190/4/#heading--log) to our support team at contact@nuki.io, so they can check the details of what happend.
It worked when I did the following:
Thanks for the support!
Gijs
New in forum and Nuki smart lock and bridge. Both new versions but bridge stuck in 2.2.13 and wifi 2.0.
Any help to force update?
Tryed:
None of this works. Thanks in advance
Can you send me the ID of your bridge via PM?
“versions”: {
“firmwareVersion”: “2.4.8”,
“wifiFirmwareVersion”: “2.1.4”
}
it’s seems bidge updated overnight. Thanks for the support @Stephan
I have switched to 2.4.21 and now my bridge will not connect to my router, error message is Bluetooth error.
Did it just stop working or did you try to reconfigure something (as the update to 2.4.21 normally happens automatically)?
In any case best directly contact our support via https://nuki.io/en/support-request/ or contact@nuki.io for direct help as this is already a public firmware version.
Hi, I did this and the response was not helpful. Please see below. they basically directed me to update the firmware (already was updated) and to connect to WLAN (THIS IS THE ACTUAL PROBLEM). The bridge stopped connecting to the WLAN and now, when I try reconnecting it to the WLAN it shows the message in the image.
Thx!
"Thank you for contacting us.
The Bridge 2.0 firmware 2.4.21 was publicly released this week.
Please leave the Bridge plugged in and connected to the WLAN.
Then go to “Manage Bridge” in your Nuki App and choose “Firmware update”. Then follow the instructions in the Nuki app to update the firmware of your Bridge.
O.k., seems there has to be a missunderstanding. Please activate debug mode for your App, retry the bridge management till you get the error again and then send a log-file to the support as a reply to their note.
This should help them investigate your issue.
Please also include when/how you noticed that it “stopped connecting to the WLAN”.
Meanwhile you could also try to restart your smartphone or try with another device to rule out an bluetooth issue there.
My bridge also upgraded to 2.4.21 and also has no connection to the WLAN anymore (can’t ping it). Will also investigate the logs to see what is going on. 2.4.8 was working perfectly from my home-grown home automation system.
Somehow my access point system time (a TP-Link EAP330) got to a date in 2014. I configured an NTP server and synchronized the time, rebooted the access point and the nuki connected again. Don’t really know if this was the problem. But maybe it helps others 
Hi, I have just installed a NUKI kit, including a Bridge, but this last is continuously being disconnected from my wifi (despite a good signal, other smart devices connected to it are working properly). NUKI bridge connects and disconnects alone with no action on my side. My app version is 2.5.3 (1372). Thanks for your support ¡
@pedro Please contact our support via https://nuki.io/en/support-request/ or contact@nuki.io with your Bridge ID for direct help on your issue.
Same problem here. Nuki bridge connecting, disconnecting etc. How can I downgrade to 2.4.8?
Patrick
Hello, my bridge is still on 2.3.0 and will not update to newer version.
I tried several times to restart the bridge und forced fwupdate via HTTP API with token_id.
http://10.4.70.100:8080/fwupdate?token=xxxxxx
But the bridge is only flashing the light for just 1 sec than stops blinking and will not updating.
The PING interrupts every vew minutes for a while. The device is not stable.
Antwort von 10.4.70.100: Bytes=32 Zeit=20ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=6ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=8ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=7ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=5ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=7ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=6ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=5ms TTL=255
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.103: Zielhost nicht erreichbar.
Antwort von 10.4.70.100: Bytes=32 Zeit=1756ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=6ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=5ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=6ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=4ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=8ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=106ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=5ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=7ms TTL=255
Antwort von 10.4.70.100: Bytes=32 Zeit=5ms TTL=255
How can I fix this issue? Thank you in advance.
Regards
Thomas
---------- edit -----------------
Ok, I fixed this issue by doing a factory-reset. After this, the bridge has updated to 2.4.26
