I recently upgrade from the Nuki Lock v1.0 to v2.0 and it’s been great so far. The door sensor works really great, although I miss the bridge as the HTTP API doesn’t work on the new bridges. The door sensor isn’t available anyway, even on the old bridges.
I am currently developing a Node.JS library for Nuki and have already implemented the basic protocol. However the Bluetooth specification is missing some important information.
- How does Nuki signal a state change to the authorised apps? The bridge can call a web hook but how is the state change indicated via the bluetooth protocol? What I have seen so far on GitHub is, that one user inferred the state change by looking at a specific bit in the manufacturer data that Nuki advertises via Bluetooth. Is there any specification on that?