-
-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: The unlatch action should be available also when the lock is locked #876
Comments
Ok, now I understood the logic: when the door is locked, you only see the unlock button, not the unlatch one. When it's closed and unlocked, you see both action buttons. I think this logic is not the best, because unlatch actually implies unlock, so you should be able to unlatch also when the door is locked. That's how it works at the API level with Nuki locks for example: you can unlatch in both unlocked/locked states, unlatch basically means do an extra half-turn of the knob after the unlock, to physically open the door. So I don't know if this was intentional or not (if it is, this is not a bug), but I would ask if this kind of behavior could be configured via an option of the Lock Card. I also saw in another issue that someone would like the unlatch button to be optionally off. Thanks. |
Oh you can open when it's locked ? You don't have to unlock before open? What integration do you use ? |
There are two possible actions: unlock and open (unlatch) Basically the difference between unlock and open actions is that the latter does a half turn more to open the door. :)
I use a Nuki lock. UPDATE: I updated the title and the description of the issue. |
When using e.g the Nuki Opener with the nukihub integration, the lock entity uses the lock/unlock mechanism to configure ring to open. The lock.open service can always be used to really open the door, so its quite unhandy that the open action is hidden. |
That is also true for HA default behaviour when exposing the lock entity in lovelace, the lock.open service is not exposed in the UI, only Problem is that many think that if the lock is locked, the only possible action is I hope at least with mushroom this can be corrected. |
I also think there should be an option for the unlatch button to not show up when the door is unlocked, or at least a way to get a confirmation message. This is my card code:
|
@piitaya Paul, will this be corrected? |
Any upgrade on this matter?
I pretty sure we have to options:
I really like the suggestion from @thor9898 to ask for a confirmation before open it, it avoids the mistake to wide open it when im not at home |
Probably a bit too simple (no config entry and no confirmation before opening) but here is a one-line change to always show "open" even when locked (for the ones who can't wait for a proper change): |
Did you submit a PR? :) |
Requirements
Current Behavior
The Lock Card should show the Open button (
unlatch
action) based on thesupported_features
attribute of the lock, but since I migrated to Mushroom, I don't always see the second button on the card, it appears only when the lock is unlocked.I'll show 2 screenshots where you can see the card with only 1 button and with the 2nd (I updated the template in one of them but the Lock Card is the same), the lock device is the same (Nuki). You can also see the attribute of the lock:
supported_features: 1
.Expected Behavior
No response
Steps To Reproduce
No response
Context
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: