Create callback for door sensor status in Bridge API

Feature requests Done
1

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.

2 Likes
2

I see the bridge API has been updated today but unfortunely it only contains features for upcoming hardware. I would have liked to see support for current hardware as well like callbacks for the sensor status and the user or keypad code which opened the smartlock. Is there any timeline on these features?

2 Likes
3

I’d like to upvote this. It’s a shame that this is not already included in the Bridge API or in Callbacks. This is a key-feature to include the door into smarthome, and it has some interresting possibilities:

  1. trigger alarm if door is opened (including opening without unlocking the door!)
  2. warn if door stands open for longer time (i.e. if you forgot to close the door properly)
1 Like
4

Totally agree with @Andreas_Lackner :slight_smile:

1 Like
5

This is the feature request with the second most votes yet other stuff seems to get planned and there is not even a reaction from Nuki on this request. I’m aware of the “we don’t communicate timeline and roadmaps” policy but still.

What’s the point of having this voting system in place if you are not gonna act on this in some way.

6

As a quick update: Everything related to Bridge API improvements was delayed due to issues/rework of the bridge firmware. Currently it looks like we will soon have a state from which we are confident enough that we can work on new features and will for sure evaluate this one here too.

3 Likes
7

Sounds great. Maybe a christmas present :slight_smile:

8

Definitly not. :slight_smile:

9

We wait confidently.
Meanwhile I used the webapi to read the doorstate field. I’m sure the call worked fine in the beginning, now it always responds with a value of 2 while the app displays the open door or 3. I’m wrong about something or there’s a potential bug.
This is the call from linux shell

curl -X GET --header call ‘Accept: application / json’ --header ‘Authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx’ ‘https://api.nuki.io/smartlock’

and this a piece of json response

    "state": {
        "mode": 2,
        "state": 3,
        "trigger": 1,
        "lastAction": 3,
        "batteryCritical": false,
        "doorState": 2,
        "ringToOpenTimer": 0,
        "nightMode": false
    },

Thank

Riccardo

10

Are you sure the server is synched at that moment?

If you experience this again please check serverState and sync to recheck the values.

11

Hi Stephan,
after few sync, but not “immediately”, the value has become correct.

Thank for your fast reply.
Riccardo

12

Any news on this?

1 Like
13

Could you please add the doorsensor state to the bridge api?

1 Like
14

Any news on this? Would like to implement in my local Smart home? Should not be that difficult, in Web Api the door sensor is implemented.

3 Likes
15

This is an important missing function of the Bridge API. Please prioritize it.

16

I am very happy that we can finally announce Bridge Beta firmware versions with this requested feature:

Please test it out and give us your feedback!

9 Likes