From 10902559cf0a09879da103c19bf35722cae64db0 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 21 Oct 2015 19:42:55 +0200 Subject: [PATCH] Update --- source/components/switch.mqtt.markdown | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/source/components/switch.mqtt.markdown b/source/components/switch.mqtt.markdown index ac0ff005e97..4800d5ffaf9 100644 --- a/source/components/switch.mqtt.markdown +++ b/source/components/switch.mqtt.markdown @@ -10,19 +10,13 @@ footer: true --- -In an ideal scenario, the MQTT device will have a state topic to publish -state changes. If these messages are published with RETAIN flag, the MQTT -switch will receive an instant state update after subscription and will -start with correct state. Otherwise, the initial state of the switch will -be false/off. +In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with RETAIN flag, the MQTT switch will receive an instant state update after subscription and will +start with 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 device -(message from state_topic). +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 device +(message from `state_topic`). -Optimistic mode can be forced, even if state topic is available. -Try to enable it, if experiencing incorrect switch operation. +Optimistic mode can be forced, even if state topic is available. Try to enable it, if experiencing incorrect switch operation. ```yaml # Example configuration.yml entry