HTTP responses not extensive enough

When I send a HTTP request to open or close a Nuki lock I always get a 204 HTTP code, even if the lock has encountered a motor block. Would it be possible to return a HTTP response code dedicated to lock errors, e.g.: motor block.

Even a general code for any lock error is better than the 204 code, as it is now impossible for me to log errors with Nuki locks in our system.

API commands are asynchronous. What you’d need in the http response is a transaction ID and - once the command has been executed - receive a callback with the transaction ID and a success or error code.

If this is something you’re interested in you should file a feature request and start collecting votes for it.

Thanks for the information. I have created a feature request right here:

1 Like