Bridge API: Bell Ring of Nuki Opener

[ooooli]

Currently, the states are only reflecting the Lock functions.
e.g. ringing (state #224), recognized by the Opener is not announced.
"224": "Ringing",

{"id":"XXXXXXXXXXXX","smartlockId":XXXXXXXXXX,"deviceType":2,"name":"","action":224,"trigger":0,"state":0,"autoUnlock":false,"date":"2019-12-22T15:00:36.000Z","openerLog":{"activeCm":false,"activeRto":false,"source":0,"flagGeoFence":false,"flagForce":false,"flagDoorbellSuppression":false}}

[Zefau]

I will have a look at this shortly. Thanks for the report.

[Zefau]

What's your source regarding state #224 being Ringing? The ioBroker log? Is the log entry you have provided generated by the nuki-extended adapter?

According to the API documentation (both Bridge API and Web API), state 224 does actually not exist.

[Zefau]

Apparently, the state is delivered with the log entries from the Nuki Opener (according to the Web API documentation).

Though, if that state is not delivered by the Bridge API callback there is no possibility to announce this via the nuki-extended adapter.

I will open an issue at the Nuki developer forum and confirm.

[Zefau]

See https://developer.nuki.io/t/nuki-web-api-logs-delivers-state-224/4722

[Zefau]

@ooooli please sign up in the Nuki developer forum and vote for the related feature request, see https://developer.nuki.io/t/nuki-bridge-api-bell-ring-of-nuki-opener-as-trigger-for-callbacks/2557

The ringing event is not delivered by Nuki as of now and that feature request asks for its implementation.

[ooooli]

@ooooli please sign up in the Nuki developer forum and vote for the related feature request, see https://developer.nuki.io/t/nuki-bridge-api-bell-ring-of-nuki-opener-as-trigger-for-callbacks/2557

The ringing event is not delivered by Nuki as of now and that feature request asks for its implementation.

Done, thanks for following up

[nachtschatt3n]

do we have ideas without the API supporting it?

[Zefau]

How is that supposed to work? Any information is being retrieved from the Bridge or Web API.

[nachtschatt3n]

well right, my ideas so far :

• web scrape it from the nuki website (15-sec polling) (they should feel the pain)
• try to catch the request going to the nuki servers via proxy (let's hope they are not doing SSL pinning)
• catch the notification on the app (android is probably easier)
• an Arduino with a microphone listening for the doorbell ?! calling iobroker URLs ?!

[ooooli]

Nuki added a new state "ringactionState" into theit beta firmware:
https://developer.nuki.io/t/bridge-beta-fw-2-7-0-1-17-0/6792
If this is accessible via adapter, the issue may be solved. I have installed the beta on my Nuki Bridge and Opener and available for testing the functionality.

Edit: the state is available, after restarting the adapter and notifying the Doorbell correctly. So this issue can be closed, once the beta feature is public. The description in the adapter only needs to be adopted (from "(no description given)".

[Zefau]

My bridge is currently sent in for maintenance. Could you screenshot the states without description? I will add them then. Thanks

[Zefau]

@ooooli Do you own a lock as well and could verify, if the door sensor (see #71) is working correctly with the fw 1.6 / 1.7 as well?

[ooooli]

My bridge is currently sent in for maintenance. Could you screenshot the states without description? I will add them then. Thanks
Sure. The new states are created as following:

[ooooli]

@ooooli Do you own a lock as well and could verify, if the door sensor (see #71) is working correctly with the fw 1.6 / 1.7 as well?

Unfortunately, I don't have a lock. Only the bridge & Opener setup.

[Zefau]

@ooooli @nachtschatt3n with the latest adapter version 2.3.0 (from Github) the states state.ringState and state.ringStateUpdate should be available and reflect the bell ring. Could you please test and verify?

[nachtschatt3n]

@Zefau sure I can check it tomorrow but don't I need the beta firmware for this?

[ooooli]

@ooooli @nachtschatt3n with the latest adapter version 2.3.0 (from Github) the states state.ringState and state.ringStateUpdate should be available and reflect the bell ring. Could you please test and verify?

The states are now named correctly:

Cross fingers, that Nuki soon adds this to the standard firmware.

[Zefau]

@Zefau sure I can check it tomorrow but don't I need the beta firmware for this?

@nachtschatt3n You do. It's only possible with the beta firmware for now.