Currently lock template only supports locked/unlocked
please allow a third: open
This to support many European locks which operate with night lock, day lock and open.
Currently lock template only supports locked/unlocked
please allow a third: open
This to support many European locks which operate with night lock, day lock and open.
Wouldnât unlocked and open be the same thing?
If you mean the door is open then itâs not about the lock anymore?
No it will not.
Unlocked would mean the door is unlocked but closed
Open would mean it is unlocked and open
The lock
entity only refers to the lockâs state, not the door.
The lock can be locked or unlocked. However, I learned some while ago that certain European locks can have an âopenâ state where both their deadbolt and striker are retracted thereby allowing the door to be opened without having to turn the door handle. Is this the third state you want a lock
entity to have?
That is correct. Thank you for clarifying
My front door doesnât have an exterior handle. The only way to open it is with the lock in the âstriker retractâ position.
At this point nothing is holding back the door to swing open at the slightest gust of wind
Itâs interesting that the lock
integration has the following three services:
lock.lock
lock.unlock
lock.open
where lock.open
serves to unlatch the lock, yet it only reports two states:
locked
unlocked
It seems reasonable to have it report a third state (open
). You have my vote.
I think it would make sense as you describe it and actually my own lock would benefit from such state.
I started the architectural discussion to see if we can get it through.