Bridge discovery & HTTP-API activation

[dumdiedum (Magdalena Lorentz)]

Hi there!

When I’m trying to list all smart locks, I get an ‘HTTP 503 Unavailable’ response, although I already activated the API in the app bridge management (while using the api key for the http request, of course).

A restart of bridge doesn’t work either. I also tried Holgers approach, but I wasn’t lucky.

In the app the smart locks have a green connection to the bridge and I’m able to performe lock/unlock etc.

Do you have an idea how to fix this?

Edit: Just found this new thread from today:

Nuki Bridge hardware revision

Update: The new Bridge Firmware is now public and there should be no need any more to join Beta just to get access to it. Note that the update runs automatically, but can take up to 25 hours. Starting next week, Nuki Bridges delivered to customers will be in a new hardware revision whose firmware does not yet contain the complete HTTP API. Why? We changed the chipset to match that in the Smart Lock in an - other than that - unchanged Nuki Bridge. So the Bridge will work in the same way as usu…

On the back of my bridge there is a Nuki-ID starting with the number 15. Is this the mentioned serial id of the new hardware revision? I’m a bit confused, because you mentioned shipping next week, but I got my bridge today. Did I got an early bird?