-
Notifications
You must be signed in to change notification settings - Fork 83
Description
Analysis
I mean, it used to work (though I'm not entirely sure), but right now it's not working the way it should. I live in Germany and have a lock with a latch.
The "unlock" command triggers the unlocking mechanism and also pulls the latch. As a result, the door is left open unintentionally. In this case, the desired behavior would be for the door to be unlocked, but for me to still have to turn the handle to open it.
On the other hand, I interpret the "deadbolt" command as meaning that the latch should be engaged. In reality, however, nothing happens—except that I always have to recalibrate after issuing this command, as the system seems to get out of alignment. When I press "deadbolt," the lock might turn about 1 mm, but it would need to turn much further (~5–7 mm?) to actually engage the latch.
It works as intended in the Switchbot app on my Android phone. There, you can also choose between "Unlock Door" (the lock opens and the latch is released → the door opens) and "Unlock Door Lock" (the lock opens but the latch is NOT released → the door is no longer locked, but it does not open).
SwitchBot-Mqtt 1.0.59, Webhook via Ngrok
Installation method Home Assistant OS
Core 2026.3.1
Supervisor 2026.03.0
Operating System 17.1
Frontend 20260304.0
Expected Behavior
as written above
Steps To Reproduce
as written above
Logs
no logs
Configuration
as written above
Environment
- OS:
- Software:
- Node:
- npm:
Additional Context
No response