Keypad via Bridge HTTP-Api

[Stephan (Stephan Lendl)]

The HTTP API is currently in revision, but I’m sorry I can’t give you an exact feature scope or date yet.

To your points:

@Manuel_Mager

Will the Bridge HTTP-API callback indicate the Lock was controlled via keypad

The Bridge can’t show users of last actions atm due to it not having Admin rights.
This means this would need a complete rebuild of the logic. - We already had a similar request which ended in this feature request:

Add user to bridge HTTP API notifications

Product name Nuki bridge Summary I’d like to see an addition in the bridge http api callback. It would be great if the user who initiated the change in lockstate would be mentioned in the posted JSON as well. This would allow for further integration with other home automation devices. Features add user that changed the lockstate to JSON callback of Bridge HTTP API Reason being able to do other home automation stuff based on who opened or locked the door Examples people that use a home aut…

@Manuel_Mager

Are invalid code attempts reported?

Invalid code attempts are listed in the activity log - to which the bridge has no access for the same reasons as stated above.

@Manuel_Mager

Will the keypad be accessible via Bridge HTTP-API?

The Bridge does not directly communicate with the Keypad, so all admin action has do be done via the Smart Lock - and I think you already know the restrictions for that.

To sum it up: All admin actions can only be done via Web API (which can be granted those rights) atm.
The main reason for that being that the HTTP API was planned for easy local communication with smart home control centers or similar; with the minimal access rights needed for that task.