Bridge API: Door sensor?

[membersound]

Any updates on this? I mean, why should this fundamental door state not exist in a local network? It is crucial for smarthome automations to request the doorsensor state eg once 1 minute for detecting if door has eg been left open.

[christianTF (Christian Fenzl)]

I’m very sad too.
Nuki 2.0 is available since Nov. 2018, with the door sensor as new feature.
Now we have May 2020. The bridge costs about 100 Euros, and there is a new bit (Open/Closed) to implement.

I’m also surprised about your new business model to pay yearly to open a door (Nuki Box). Very disillusioning that you sell hardware with subscriptions. Most of cloud based things like that finally close and the hardware is worthless.

[Juergen (Jürgen Pansy)]

@christianTF

and there is a new bit (Open/Closed) to implement.

Unfortunately it’s much more than that.

@christianTF

I’m also surprised about your new business model to pay yearly to open a door (Nuki Box). Very disillusioning that you sell hardware with subscriptions. Most of cloud based things like that finally close and the hardware is worthless.

The business model for Nuki Box is quite different than for the Smart Lock: It’s bought by property managers, mounted by electricians and used by several different parties, inc. the people living in the building. All have their own service level requirements and all want a system that works for many years.
There are at least as many “not cloud based” (or better “one off payment”) things that are mounted and unusable because nobody does service them anymore (which is especially true if you rely on Smartphone Apps, which usually stop working after a few years without updates). But i agree with you, nobody likes to pay regular fees

[ben1 (Benjamin Bräuer)]

@Juergen

Unfortunately it’s much more than that.

But in the Web API the status is implemented. All bits and triggers are there. And just need to be implementet into the bridge api. The Bridge itself should already have this information, otherwise it could not give the information from lock -> bridge -> server.

[Juergen (Jürgen Pansy)]

@ben1

The Bridge itself should already have this information, otherwise it could not give the information from lock -> bridge -> server.

This is not how the Nuki system works. Because of the end to end encryption the bridge can not read what Apps or Nuki Web are communicating with the lock (https://nuki.io/en/blog/stay-secure/focused-on-security-nukis-encryption-concept-explained-simply/). Furthermore events created by Nuki Web are based on the log & state, while bridge API events are based only on state changes (because the bridge does not have access to the log).

[Stephan (Stephan Lendl)]

New Bridge Beta firmware versions with this requested feature are now available:

Bridge Beta FW 2.6.0 / 1.16.0 with door sensor state

With the latest Beta firmware version 2.6.0 and 1.16.0 you can now: get the door state in /info and /lockState commands get callbacks for door state changes Examples: /lockState { “mode”: 2, “state”: 1, “stateName”: “locked”, “batteryCritical”: false, “doorsensorState”: 2, “doorsensorStateName”: “door closed”, “success”: true } /list [{ "nukiId": 1, "deviceType": 0, "name": "Home", "lastKnownState": { "mode": 2, "state": 1, "stateName": "locked", "batter…

Please test it out and give us your feedback!

[Lorenzo_Castricini]

This feature isn’t available for Android Bridge App, is it correct?
Are you planning to upgrade the bridge app in the future?

[Stephan (Stephan Lendl)]

@Lorenzo_Castricini

This feature isn’t available for Android Bridge App, is it correct?

Correct.

@Lorenzo_Castricini

Are you planning to upgrade the bridge app in the future?

Unfortunately there are no updates planned for the Bridge App.