Bridge API: Door sensor?

[jensih (Jens I.)]

Hi,

thanks for confirming but would be also interesting to have some ETA.
I have already plenty of ideas I can do with this little but so important information.
Lovely Product Managers, can you just bump it up on the backlog?

Thanks!

[Stephan (Stephan Lendl)]

Lovely Product Managers

I fear this won’t help.

I’m sorry, but I still can’t give an ETA. But i’m looking forward to your ideas what to build with it.

[jensih (Jens I.)]

First of all I would go ahead and create an Push Message alert if the Door is open too long. Meaning someone left it open withour knowing / intending to do so.

Additionally a camera could be activ activated based on this information, to verify what is going on.

Technically you could also do something where the lock reports locked, but the door reports open state. This means something went wrong on locking it and / or possible intruder. Maybe only the lock felt down on the floor, but this would be good to know as well.

Basically I believe every function or status/sensor should be readable/exposed by the APIs. For example a state change from locked to unlock causes some ligths to be turned on during special daytimes. This being a good automation without needing to use geo information.

[Torsten85 (Torsten Blindert)]

Any update on this? I’m also looking forward for this update

[kgrill (ING. KARL GRILL)]

There’s a new API documentation V1.8 dated 20190306 but i still miss the door sensor state? When will this state be available?

[Stephan (Stephan Lendl)]

There’s a new API documentation V1.8 dated 20190306 but i still miss the door sensor state?

The changelog for v 1.8 can be found here:

New Bridge API documentation v. 1.8

The Nuki Bridge API documentation has been updated to reflect the newly implemented hashed token alternative. See also: Changelog v 1.8 Introducing the hashed token as a more secure alternative to sending the plain token Minor text and formatting fixes

Door sensor will hopefully be part of the next big update, but I can’t promise an ETA yet.

[kgrill (ING. KARL GRILL)]

This sounds terrible. You announced Smartlock 2.0 mid of october last year with the door sensor feature (i know, it’s still Beta). If you want to integrate nuki in a smart home you either need the door sensor state or you’ve to add some other magnetic contact to check the correct door state. Double Cost!

[Stephan (Stephan Lendl)]

The door sensor is available in the Web API (I know this won’t help you if you want a local/offline solution, but for some it can be a transitional solution). We have to set priorities in firmware development and unfortunatly not every feature request can be handled as fast as we would like to.

[jensih (Jens I.)]

Any updates on getting the door sensor into the Bridge / Local API? Thx

[Stephan (Stephan Lendl)]

Sorry, I can still give not date on that. Existing issues have still to be handled before locking at new bridge features.

[jespertheend (Jesper van den Ende)]

I’d love to see this as well. Looking forward to any updates when they happen

[jespertheend (Jesper van den Ende)]

Is there any documentation of the door state in the Web API? I noticed the doorState value is 2 when the door is closed and 3 when the door is open, but I was wondering if this is documented anywhere.

[Stephan (Stephan Lendl)]

Is there any documentation of the door state in the Web API

You can find this at the model of https://api.nuki.io/#!/Smartlock/get

Smartlock.State {

...
doorState (integer): 

The door state: 0 .. unavailable, 1 .. deactivated, 2 .. door closed, 3 .. door opened, 4 .. door state unknown, 5 .. calibating,
...

}

[jespertheend (Jesper van den Ende)]

Ah I see, I wasn’t aware of the model button. That should be useful. I suppose the web API doesn’t have some sort of web hook functionality like the local http rest api?

[nicohirsch]

Still nothing? I get a callback when the door is opened/closed, but no state.
This thread is now nearly a year old, with no updates…

[Stephan (Stephan Lendl)]

We are aware of this request, but we do not communicate our timelines, priorities and roadmaps in the public, so there have been no updates.

[iMarkus (Markus)]

I am also a little bit wondering why this is not available offline as it is implemented in Web API and we are not talking about reinvent the wheel

Feature request for voting:

Create callback for door sensor status in Bridge API

Product name Bridge API Summary Notify 3rd party devices of changes in the door sensor status through the Bridge API. Features new callback option which is triggered when door sensor changes Reason Better integration with home domotica system and also use the door sensor for home automation. Examples Perform some sort of action when the door sensor detects a change and notifies other home automation systems of these changes.

[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.