service "lock.open" not available anymore

[dareios1995]

The problem

normally I can control my Danalock Smartlock via the three services lock.open, lock.lock and lock.unlock.
Since an update, I can now only control the lock via lock.unlock and lock.lock. The lock.open service does not let me select my lock (see photos).

I assume that since the change to the new lockslider as lovelace-card which knows only close and unlock, but not the function "open" which is mandatory for German doors, for example.
Another side effect is that Siri locks or unlocks but does not open the door when you say "Siri, open my door".

The behavior in the UI is similar to this case:
#98296

What version of Home Assistant Core has the issue?

core-2023.8.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

https://www.home-assistant.io/integrations/lock/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (lock) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of lock can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign lock Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

lock documentation
lock source
_{^{(message by IssueLinks)}}

[MartinHjelmare]

With which integration are you using the Danalock?

[dareios1995]

i am using zigbee2mqtt. Version 1.32.2 with a Conbee2

[MartinHjelmare]

I think what has changed is that we now filter entities in the service call selector depending on what features the entity supports. In the lock case, a lock entity that doesn't support the lock.open service won't be selectable in the lock.open service selector.

For a lock in the MQTT integration to set the supported feature for the lock.open service, the payload_open config needs to be set. I suspect this is what's missing in your case in zigbee2mqtt.

https://www.home-assistant.io/integrations/lock.mqtt/#configuration

[dareios1995]

First of all, thank you very much for your help. Through further research I was able to find out that my lock probably only knows the payload LOCK or UNLOCK, but not the payload OPEN (see here https://www.zigbee2mqtt.io/devices/V3-BTZB_V3-BTZBE.html#lock).
So I guess I can say that it is not a bug in homeassistant. I apologize for that.

My last question would be now actually only whether one can include the circumstance of a German/European door with the lovelave-card. Previously, there were the two buttons open and close. With the button open I could also obtain the pulling of the door latch. Today, when I press the lock slider to pull the door latch (and the door is already unlocked), the door only locks because it only knows the status lock or unlock. So I have to make an intermediate step to finally open the door. I first have to lock the door again to finally unlock it again and then open it.

Is there a way to change the lock button slider to trigger an UNLOCK even if the door is already unlocked?

I think this possibility would make some users very happy :D

Thanks a lot and best regards
Darius

[MartinHjelmare]

You may be able to customize the entity to use assumed state.

For further questions, please use our help channels.

https://www.home-assistant.io/help/#communication-channels

Closing here now as there's no bug in Home Assistant regarding lock.open availability.