Lock Manager API - Version 01.10.02
- (new) Added usage history page
- (enhancement) Check for invalid DTH
- (fix) Check if the door selection was accidentally left out for notifications and relocks
- (enhancement) Support for new platform garage door capabilities
- (fix) Various minor fixes, enhancements and UI improvements
- (new) “lock status” adds
connection
member to the response JSON which reports the lock connectivity state
The connectivity status for each lock can contain the following values:
online
- The platform is able to communicate with the lockoffline
- The hub cannot communicate with the lock (mesh problems, lock batteries etc)hub disconnected
- The platform cannot communicate with the hub (power failure, internet connectivity etc)
Please ensure that your lock is within 20ft of a buffering/beaming repeaterfor the best experience (the buffering device should be between the hub and the lock for maximum effectiveness).
Recommended you can use the Enhanced Universal Z-Wave Lock or the Universal ZigBee Lock device handler for a more robust lock experience.
The programmed state for each user in every lock is shown in
lockProgrammedState
which can contain the following values:
Pending program
- Awaiting code programming confirmation from lockPending deletion
- Awaiting code deletion confirmation from lockActive
- Code programming is confirmed by lockInactive
- Code deletion is confirmed by lockFailed
- Lock failed to respond even after configured number of retries