@anon97065019, @Steffen
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
Copy
{
“mode”: 2,
“state”: 1,
“stateName”: “locked”,
“batteryCritical”: false,
“doorsensorState”: 2,
“doorsensorStateName”: “door closed”,
“success”: true
}
/list
Copy
[{
"nukiId": 1,
"deviceType": 0,
"name": "Home",
"lastKnownState": {
"mode": 2,
"state": 1,
"stateName": "locked",
"batteryCritical": false,
“doorsensorState”: 2,
“doorsensorStateName”: “door closed”,
"timestamp": "2018-10-03T06:49:00+00:00" }
}]
Callback:
Copy
{“nukiId”: 11, “deviceType”: 0, “mode”: 2, “state”: 1, “stateName”: “locked”, “batteryCritical”: false, “doorsensorState”: 2, “doorsensorStateName”: “Door Closed”
}
doorsensorState:
| ID | Name |
|---|---|
| 0 | unavailable |
| 1 | deactivated |
| 2 | door closed |
| 3 | door opened |
| 4 | door state unknown |
| 5 | calibrating |
Note: Very fast sequences of door state changes may not trigger an individual callback each, so you can not build a complete door state history witht this feature.
The update will be done autonatically if your Bridge is part of the Beta program.
