Hello,
since having updated HA-core to 2025.1.1/2025.1.2 the previous well-running tedee-integration doesn’t work any more and the lock is not available any more.
My lock is connected via bridge and integrated by access-token in the configuration file.
If I turn back to 2025.12.5 by backup, it works great again.
Has anyone out there the same issue or a solution?
My guess is you are still using the custom integration (can be recognized by the red box on the integration page, attached Nordpool as an example) - which has been deprecated a while ago. Remove the integration, uninstall tedee from HACS and then add it again from the core integrations.
Hi Josef, having done to your advice, it’s working fine, now again!
Thanks a lot!
I have a question regarding best practice / duration of unlock/open. I have an automation that, after being triggered, unlocks the lock if it’s locked and then opens the lock. Unfortunately, there is a long delay of several seconds between unlocking and opening. Is there a way to improve that?
This is the relevant part of my automation:
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
why not always call open directly?
If I call open when the lock is locked, it just unlocks and does not open.
that’s weird it should absolutely also open
Thanks. I created lock.open does not open if lock is locked · Issue #137425 · home-assistant/core · GitHub for that.