mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-05-03 17:48:59 +00:00
a964ae5ac8
* Add sensor example
* Small changes
* Add ESPEasy example
* Add ESPEasy example
* Fixes
* ✏️ Minor improvements
150 lines
4.9 KiB
Markdown
150 lines
4.9 KiB
Markdown
---
|
|
layout: page
|
|
title: "MQTT Switch"
|
|
description: "Instructions how to integrate MQTT switches into Home Assistant."
|
|
date: 2015-08-30 23:38
|
|
sidebar: true
|
|
comments: false
|
|
sharing: true
|
|
footer: true
|
|
logo: mqtt.png
|
|
ha_category: Switch
|
|
ha_release: 0.7
|
|
ha_iot_class: depends
|
|
---
|
|
|
|
The `mqtt` switch platform lets you control your MQTT enabled switches.
|
|
|
|
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 switch will receive an instant state update after subscription, and will start with the correct state. Otherwise, the initial state of the switch will be `false` / `off`.
|
|
|
|
When a `state_topic` is not available, the switch will work in optimistic mode. In this mode, the switch will immediately change state after every command. Otherwise, the switch will wait for state confirmation from the device (message from `state_topic`).
|
|
|
|
Optimistic mode can be forced, even if the `state_topic` is available. Try to enable it, if experiencing incorrect switch operation.
|
|
|
|
To enable this switch in your installation, add the following to your `configuration.yaml` file:
|
|
|
|
```yaml
|
|
# Example configuration.yml entry
|
|
switch:
|
|
- platform: mqtt
|
|
command_topic: "home/bedroom/switch1/set"
|
|
```
|
|
|
|
{% configuration %}
|
|
name:
|
|
description: The name to use when displaying this switch.
|
|
required: false
|
|
type: string
|
|
default: MQTT Switch
|
|
state_topic:
|
|
description: The MQTT topic subscribed to receive state updates.
|
|
required: false
|
|
type: string
|
|
command_topic:
|
|
description: The MQTT topic to publish commands to change the switch state.
|
|
required: false
|
|
type: string
|
|
availability_topic:
|
|
description: The MQTT topic subscribed to receive availability (online/offline) updates.
|
|
required: false
|
|
type: string
|
|
payload_on:
|
|
description: The payload that represents enabled state.
|
|
required: false
|
|
type: string
|
|
default: ON
|
|
payload_off:
|
|
description: The payload that represents disabled state.
|
|
required: false
|
|
type: string
|
|
default: OFF
|
|
payload_available:
|
|
description: The payload that represents the available state.
|
|
required: false
|
|
type: string
|
|
default: online
|
|
payload_not_available:
|
|
description: The payload that represents the unavailable state.
|
|
required: false
|
|
type: string
|
|
default: offline
|
|
optimistic:
|
|
description: Flag that defines if switch works in optimistic mode.
|
|
required: false
|
|
type: boolean
|
|
default: "`true` if no `state_topic` defined, else `false`."
|
|
qos:
|
|
description: The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
|
|
required: false
|
|
type: integer
|
|
default: 0
|
|
retain:
|
|
description: If the published message should have the retain flag on or not.
|
|
required: false
|
|
type: boolean
|
|
default: false
|
|
value_template:
|
|
description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload."
|
|
required: false
|
|
type: string
|
|
{% endconfiguration %}
|
|
|
|
<p class='note warning'>
|
|
Make sure that your topic matches exactly. `some-topic/` and `some-topic` are different topics.
|
|
</p>
|
|
|
|
## {% linkable_title Examples %}
|
|
|
|
In this section you will find some real life examples of how to use this sensor.
|
|
|
|
### {% linkable_title Full configuration %}
|
|
|
|
The example below shows a full configuration for a switch.
|
|
|
|
```yaml
|
|
# Example configuration.yml entry
|
|
switch:
|
|
- platform: mqtt
|
|
name: "Bedroom Switch"
|
|
state_topic: "home/bedroom/switch1"
|
|
command_topic: "home/bedroom/switch1/set"
|
|
availability_topic: "home/bedroom/switch1/available"
|
|
payload_on: "ON"
|
|
payload_off: "OFF"
|
|
optimistic: false
|
|
qos: 0
|
|
retain: true
|
|
```
|
|
|
|
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 switch manually:
|
|
|
|
```bash
|
|
$ mosquitto_pub -h 127.0.0.1 -t home/bedroom/switch1 -m "ON"
|
|
```
|
|
|
|
### {% linkable_title Set the state of a device with ESPEasy %}
|
|
|
|
Assuming that you have flashed your ESP8266 unit with [ESPEasy](https://github.com/letscontrolit/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". There is no further configuration needed as the [GPIOs](https://www.letscontrolit.com/wiki/index.php/GPIO) can be controlled with MQTT directly.
|
|
|
|
Manually you can set pin 13 to high with `mosquitto_pub` or another MQTT tool:
|
|
|
|
```bash
|
|
$ mosquitto_pub -h 127.0.0.1 -t home/bathroom/gpio/13 -m "1"
|
|
```
|
|
|
|
The configuration will look like the example below:
|
|
|
|
{% raw %}
|
|
```yaml
|
|
# Example configuration.yml entry
|
|
switch:
|
|
- platform: mqtt
|
|
name: bathroom
|
|
state_topic: "home/bathroom/gpio/13"
|
|
command_topic: "home/bathroom/gpio/13"
|
|
payload_on: "1"
|
|
payload_off: "0"
|
|
```
|
|
{% endraw %}
|
|
|