8.4 KiB
| title | description | logo | ha_category | ha_release | ha_iot_class | |
|---|---|---|---|---|---|---|
| MQTT Binary Sensor | Instructions on how to integrate MQTT binary sensors within Home Assistant. | mqtt.png |
|
0.9 | Configurable |
The mqtt binary sensor platform uses an MQTT message payload to set the binary sensor to one of two states: on or off.
The binary sensor state will be updated only after a new message is published on state_topic matching payload_on or payload_off. If these messages are published with the retain flag set,
the binary sensor will receive an instant state update after subscription and Home Assistant will display the correct state on startup.
Otherwise, the initial state displayed in Home Assistant will be unknown.
Stateless devices such as buttons, remote controls etc are better represented by MQTT device triggers than by binary sensors.
Configuration
The mqtt binary sensor platform optionally supports an availability_topic to receive online and offline messages (birth and LWT messages) from the MQTT device. During normal operation, if the MQTT sensor device goes offline (i.e., publishes payload_not_available to availability_topic), Home Assistant will display the binary sensor as unavailable. If these messages are published with the retain flag set, the binary sensor will receive an instant update after subscription and Home Assistant will display the correct availability state of the binary sensor when Home Assistant starts up. If the retain flag is not set, Home Assistant will display the binary sensor as unavailable when Home Assistant starts up. If no availability_topic
is defined, Home Assistant will consider the MQTT device to be available.
To use an MQTT binary sensor in your installation,
add the following to your configuration.yaml file:
# Example configuration.yaml entry
binary_sensor:
- platform: mqtt
state_topic: "home-assistant/window/contact"
{% configuration %}
availability_topic:
description: "The MQTT topic subscribed to receive birth and LWT messages from the MQTT device. If availability_topic is not defined, the binary sensor availability state will always be available. If availability_topic is defined, the binary sensor availability state will be unavailable by default."
required: false
type: string
device:
description: "Information about the device this binary sensor is a part of to tie it into the device registry. Only works through MQTT discovery and when unique_id is set."
required: false
type: map
keys:
connections:
description: "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']."
required: false
type: [list, map]
identifiers:
description: A list of IDs that uniquely identify the device. For example a serial number.
required: false
type: [list, string]
manufacturer:
description: The manufacturer of the device.
required: false
type: string
model:
description: The model of the device.
required: false
type: string
name:
description: The name of the device.
required: false
type: string
sw_version:
description: The firmware version of the device.
required: false
type: string
device_class:
description: Sets the class of the device, changing the device state and icon that is displayed on the frontend.
required: false
type: string
expire_after:
description: "Defines the number of seconds after the value expires if it's not updated. After expiry, the value is cleared, and the availability is set to false"
required: false
type: integer
force_update:
description: Sends update events even if the value hasn't changed. Useful if you want to have meaningful value graphs in history.
required: false
type: boolean
default: false
json_attributes_template:
description: "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."
required: false
type: template
json_attributes_topic:
description: 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.
required: false
type: string
name:
description: The name of the binary sensor.
required: false
type: string
default: MQTT Binary Sensor
off_delay:
description: "For sensors that only sends On state updates, this variable sets a delay in seconds after which the sensor state will be updated back to Off."
required: false
type: integer
payload_available:
description: The payload that represents the online state.
required: false
type: string
default: online
payload_not_available:
description: The payload that represents the offline state.
required: false
type: string
default: offline
payload_off:
description: The payload that represents the off state.
required: false
type: string
default: "OFF"
payload_on:
description: The payload that represents the on state.
required: false
type: string
default: "ON"
qos:
description: The maximum QoS level to be used when receiving messages.
required: false
type: integer
default: 0
state_topic:
description: The MQTT topic subscribed to receive sensor values.
required: true
type: string
unique_id:
description: An ID that uniquely identifies this sensor. If two sensors have the same unique ID, Home Assistant will raise an exception.
required: false
type: string
value_template:
description: "Defines a template to extract a value from the payload. Available variables: entity_id. Remove this option when 'payload_on' and 'payload_off' are sufficient to match your payloads."
required: false
type: string
{% endconfiguration %}
Examples
In this section, you will find some real-life examples of how to use this sensor.
Full configuration
To test, you can use the command line tool mosquitto_pub shipped with mosquitto or the mosquitto-clients package to send MQTT messages.
To set the state of the binary sensor manually:
$ mosquitto_pub -h 127.0.0.1 -t home-assistant/window/contact -m "OFF"
The example below shows a full configuration for a binary sensor:
{% raw %}
# Example configuration.yaml entry
binary_sensor:
- platform: mqtt
name: "Window Contact Sensor"
state_topic: "home-assistant/window/contact"
payload_on: "ON"
payload_off: "OFF"
availability_topic: "home-assistant/window/availability"
payload_available: "online"
payload_not_available: "offline"
qos: 0
device_class: opening
value_template: '{{ value.x }}'
{% endraw %}
Toggle the binary sensor each time a message is received on state_topic
{% raw %}
# Example configuration.yaml entry
binary_sensor:
- platform: mqtt
state_topic: "lab_button/cmnd/POWER"
value_template: "{%if is_state(entity_id,\"on\")-%}OFF{%-else-%}ON{%-endif%}"
{% endraw %}
Get the state of a device with ESPEasy
Assuming that you have flashed your ESP8266 unit with ESPEasy. Under "Config" is a name ("Unit Name:") set for your device (here it's "bathroom"). A configuration for a "Controller" for MQTT with the protocol "OpenHAB MQTT" is present and the entries ("Controller Subscribe:" and "Controller Publish:") are adjusted to match your needs. In this example, the topics are prefixed with "home". Also, add a "Switch Input" in the "Devices" tap with the name "switch" and "button" as value.
As soon as the unit is online, you will get the state of the attached button.
home/bathroom/status Connected
...
home/bathroom/switch/button 1
The configuration will look like the example below:
# Example configuration.yaml entry
binary_sensor:
- platform: mqtt
name: Bathroom
state_topic: "home/bathroom/switch/button"
payload_on: "1"
payload_off: "0"