Product name
Nuki Bridge API
Summary
The callback URIs should be called when the bell rings (detected by Nuki Opener).
Features
- If a Nuki Opener registers that the bell rings, the registered callback URIs should be called by the Nuki Bridge.
- The JSON body of the callback should contain a value indicating that the bell rang.
Reason
This feature is part of the unique selling point of Nuki compared to Nello: events (like bell ring) can be handled on the local network rather than having to communicate with a server in the Cloud.
I’ve already implemented the homebridge plugin for Nello. Like the Nuki Web API, the Nello (Web) API supports web hooks. However, if your homebridge instance (local network) should receive notifications, you have to implement some sort of relay server (in this case web hook to web socket) that redirects the callback requests to your homebridge instance in our local network.
Now, I’m going to implement the homebridge plugin for the Nuki Opener and don’t want to rely on the relay server part anymore, especially as the Nuki Bridge already handles the events of the Nuki Opener (different from Nello, where the device itself is connected to the WiFi).
Examples
- Homebridge plugin for the Nuki Opener
- Any kind of server/service in the local network that communicates with the Nuki Bridge API