MQTT Lock
The mqtt
lock platform lets you control your MQTT enabled locks.
Configuration
In an ideal scenario, the MQTT device will have a state_topic
to publish state changes. If these messages are published with a RETAIN
flag, the MQTT lock will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the lock will be false
/ unlocked.
When a state_topic
is not available, the lock will work in optimistic mode. In this mode, the lock will immediately change state after every command. Otherwise, the lock will wait for state confirmation from the device (message from state_topic
).
Optimistic mode can be forced, even if state topic is available. Try to enable it, if experiencing incorrect lock operation.
To enable MQTT locks in your installation, add the following to your configuration.yaml
file:
# Example configuration.yaml entry
lock:
- platform: mqtt
command_topic: "home/frontdoor/set"
Configuration Variables
- command_topic
(string)(Required)
The MQTT topic to publish commands to change the lock state.
- state_topic
(string)(Optional)
The MQTT topic subscribed to receive state updates.
- name
-
(string)(Optional)
The name of the lock.
Default value:
MQTT Lock
- payload_lock
-
(string)(Optional)
The payload that represents enabled/locked state.
Default value:
LOCK
- payload_unlock
-
(string)(Optional)
The payload that represents disabled/unlocked state.
Default value:
UNLOCK
- state_locked
-
(string)(Optional)
The value that represents the lock to be in locked state
Default value:
locked
- state_unlocked
-
(string)(Optional)
The value that represents the lock to be in unlocked state
Default value:
unlocked
- optimistic
-
(string)(Optional)
Flag that defines if lock works in optimistic mode.
Default value:
true
if nostate_topic
defined, elsefalse
. - qos
-
(integer)(Optional)
The maximum QoS level of the state topic.
Default value:
0
- retain
-
(boolean)(Optional)
If the published message should have the retain flag on or not.
Default value:
false
- value_template
(string)(Optional)
Defines a template to extract a value from the payload.
- availability_topic
(string)(Optional)
The MQTT topic subscribed to receive availability (online/offline) updates.
- payload_available
-
(string)(Optional)
The payload that represents the available state.
Default value:
online
- payload_not_available
-
(string)(Optional)
The payload that represents the unavailable state.
Default value:
offline
- json_attributes_topic
(string)(Optional)
The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Usage example can be found in MQTT sensor documentation.
- json_attributes_template
(template)(Optional)
Defines a template to extract the JSON dictionary from messages received on the
json_attributes_topic
. Usage example can be found in MQTT sensor documentation.- unique_id
(string)(Optional)
An ID that uniquely identifies this lock. If two locks have the same unique ID, Home Assistant will raise an exception.
- device
(map)(Optional)
Information about the device this lock is a part of to tie it into the device registry. Only works through MQTT discovery and when
unique_id
is set.- identifiers
(string | list)(Optional)
A list of IDs that uniquely identify the device. For example a serial number.
- connections
(list)(Optional)
A list of connections of the device to the outside world as a list of tuples
[connection_type, connection_identifier]
. For example the MAC address of a network interface:"connections": [["mac", "02:5b:26:a8:dc:12"]]
.- manufacturer
(string)(Optional)
The manufacturer of the device.
- model
(string)(Optional)
The model of the device.
- name
(string)(Optional)
The name of the device.
- sw_version
(string)(Optional)
The firmware version of the device.
Make sure that your topics match exactly. some-topic/
and some-topic
are different topics.
Examples
In this section you will find some real-life examples of how to use this lock.
Full configuration
The example below shows a full configuration for a MQTT lock.
# Example configuration.yaml entry
lock:
- platform: mqtt
name: Frontdoor
state_topic: "home-assistant/frontdoor/"
command_topic: "home-assistant/frontdoor/set"
payload_lock: "LOCK"
payload_unlock: "UNLOCK"
optimistic: false
qos: 1
retain: true
value_template: '{{ value.x }}'
Keep an eye on retaining messages to keep the state as you don’t want to unlock your door by accident when you restart something.
For a check you can use the command line tools mosquitto_pub
shipped with mosquitto
to send MQTT messages. This allows you to operate your lock manually:
$ mosquitto_pub -h 127.0.0.1 -t home-assistant/frontdoor/set -m "LOCK"