Good guess from @creak here. Looks like you got the new hardware-revision.
If you want to start using the HTTP-API asap please contact our support at firstname.lastname@example.org for a quick exchange of your device. Else you will have to wait for a FW-update .
okay - if the Nuki-Bridge ID ist the same as the Serial No. my starts with 15. So it seams, that I got a brand new hardware with only part of the software working correctly
For privacy and security reasons I don’t want to use any of those fency cloud services and I loved the idea having a bridge with local API that is usable inside a separated automation network under my control.
What’s the ETA of the new firmware? Or is the exchanged hardware also one with the new HW revison including the API or the older HW revision? Are there any information available about the diverences of the old and the new bridge HW?
That’s why we offer that solution. Unfortunatly the very high demand for our Bridge lead to that situation where we had to take the risk to ship this new revision with not yet ready HTTP API; and obviously even more people than we thought are using it!
Unfortunatly I also can’t give you an ETA yet. So if you want to be on the safe side we offer you an exchange to the previous hardware-revision. The difference is the chipset, which mainly means we use the same BT chip as in the SL v2, but features/functionality are the same in both versions.
If you want an exchange just contact our customer support at email@example.com for a quick replacement.
Thanks for the information about the the to bridge versions. So it seams, there are not that mutch differences between the both versions concerning functionality (except the running HTTP-API). If will contact you via e-mail for an exchange.
hello i have recently buy à doorlock v2 with bridge but the bridge api on my bridge return allways error 503 Unavailable but in my phone all are correct and on nuki web interface no problem all work. what wrong ?
Thanks for your feedback. Good to hear it is working now.
I also split out this part of the topic where it was a new hardware-revision bridge and not those irregular 503 errors the other users h. So users with the same issue should find the solution even quicker.