I’m having a new lock, which I’d like to integrate with Home assistant over MQTT. In general that seems to work fine, connectivity is there, interaction is possible.
Only the unlocking of the door is not what we as a household are used to. The predecessor lock was directly integrated with HomeKit and when asking Siri to ‘open the door’ we would have it unlocked and unlatched in one go.
Now, the very same action when invoked only unlocks the door. It doesn’t open / unlatch, though. And, there doesn’t seem to be a way (in German) to trigger the unlatching by Voice over Siri or manually through Home.app. When using entities through HA UI it works though.
It seems to me that the MQTT integration doesn’t call the Unlock+unlatch but rather Unlock only.
Can anyone advise what we could do to bring back the expected Unlock+unlatch behaviour to HomeKit?
There’s a separate lock.open action which appears to have been added to mqtt locks a few years ago. However I’m not aware of any intrinsic tie between the two actions, so they might have to be called separately in HA.
If you have the control, then it should be possible to make it work as desired. For example, create a script that both unlocks and unlatches the door, then define a template lock which calls the script as its unlock action (it may even be possible to send both commands via a single mqtt message). The template lock could be exported to HomeKit instead of the “real” lock. If you always want the two actions to happen together, you can also define an automation to lock.open whenever it unlocks.
So, I created two scripts using either lock.open and lock.unlock. The behavior is such that the former unlocks and unlatches and the latter only unlocks, but leaves out the unlatching.
I will probably try the automation route to also unlatch once the unlock has been triggered (not sure how to detect that though). It deems easier to accomplish then setting up a complete template lock, with all other functionality available. Or am I mistaken on the efforts?