Nuki Bridge often returns 503 - not working correct

[Juergen (Jürgen Pansy)]

Usually a 503 error means that your integration is throwing to many requests at the bridge API, because the bridge can handle only one connection/request at a time:

Random "HTTP 503 Unavailable"

No, it’s not solved in a matter of hours because the bridge can handle only one connection at a time and if you don’t serialize at your end the API will always throw 503 errors (or timeouts if we restrict the HTTP server to just one HTTP connection). This is something that’s not going to go away, ever. If you can not properly serialize you’re better off using the Nuki Web API, where we do the serialization at our end.

Furthermore the bridge does not cache or retry requests. So if something is executed with 5 minutes delay, it must have been coming from your integration with a 5 minutes delay. You can use the /log command of the bridge API to debug such cases.