lock.open does not open if lock is locked

[riesi77]

The problem

This is a bug entry resulting from a question under https://community.home-assistant.io/t/custom-component-tedee-doorlock/242743/164?u=riesi

If I call lock.open, my lock opens as expected if the lock is unlocked. However, if the lock is locked, it does only unlock and I need to call it a second time:

Steps to reproduce:

1. Lock the lock
2. Call lock.open with the lock as entity_id
   Current behaviour: lock just unlocks
   Expected behaviour: lock unlocks and opens

Workaround is to call, depending on the state, unlock first and then open, but this takes several seconds and confuses users because of the long waiting time.

What version of Home Assistant Core has the issue?

Core-2024.12

What was the last working version of Home Assistant Core?

never

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Tedee

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

as a workaround, but basically it should be possible to only call lock.open
 actions:
   - choose:
       - conditions:
           - condition: state
             entity_id: lock.tedeelock
             state: locked
         sequence:
           - action: lock.unlock
             metadata: {}
             data: {}
             target:
               entity_id: lock.tedeelock
   - action: lock.open
     metadata: {}
     data: {}
     target:
       entity_id: lock.tedeelock
 mode: single

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @patrickhilker, @zweckj, mind taking a look at this issue as it has been labeled with an integration (tedee) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tedee 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 tedee Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[zweckj]

What lock do you have? Does this work as expected in the Tedee App?

[riesi77]

I have a Tedee Pro connected via bridge.
The app provides an "open" (DE öffnen) when the door is locked:

And "pull" (DE ziehen) when the door is unlocked:

But it does not offer unlock (they call it "open") PLUS open (they call it "pull") as one action.

[riesi77]

The German wording in the app is a bit strange. But it's more transparent in the integration itself on the lock entity:
If the lock is locked, you can either unlock it, or "open door" (even if it looks disabled, you can click on it):

If you press "open door" when the lock is locked,, you get a confirmation "really open?"

And if you confirm, it just unlocks, but does not open

[zweckj]

In the lock settings (tedee app) what are your settings for:

• "Türfalle einziehen"
• "Auto-Unlock" -> Abschnitt "Andere" -> Türfalle
• "Auto-Unlock" -> Abschnitt "Andere" -> "Erweitert"

Might be that one of those is affecting the behavior of your lock

[riesi77]

Türfalle einziehen: on
Auto-Unlock: Off, so all the options below do not apply.

but maybe interesting as well:
"Türfalle einziehen" --> Türfalle automatisch einziehen is "off". If I put that on, the open changes into "open and pull":

With that setting on, I can achieve my desired behavior in the automation (fast unlock and pull), but I loose the ability that pressing the physical button on the door just unlocks and does not pull the spring (for this, I have the handle). This is why I turned it off.

[riesi77]

Conclusion:

If "Automatic pull spring" is on, then the hardware button can not just unlock, but it always pulls. This is unwanted because I have the door handle on the inner side for that. And there is a risk as well: If I unlock by buttonpress on the inner side and then leave and close the door from outside. The spring may still pulled and the door doesn't close.
If "Automatic pull spring" is off, the lock.open command does not unlock + open at once. You have to call it twice with a significant delay.

I don't think anymore this is a bug in the integration, but more an inconsistency in the tedee functionality.