From b84f596358f684d918d35c98f0b6d6f6871ff6dd Mon Sep 17 00:00:00 2001 From: Ryan Warner Date: Sun, 12 Apr 2020 05:18:25 -0400 Subject: [PATCH] Update lock.mqtt example with state_locked and state_unlocked (#12533) * Update lock.mqtt for reflect breaking change Had an issue with my HASS not working with locks. Turns out the docs didn't reflect the new "state_lock" and "state_unlock" payload breaking change mentioned here: https://www.home-assistant.io/blog/2020/01/15/release-104/#breaking-changes Is it worth getting rid of the old payload_lock payload_unlocked states and changing them in the example? * Forgot "ed" in the example * Put payload_lock/unlock back in Let's have both the payload_lock/unlock back in the example along with state_locked/unlocked. --- source/_integrations/lock.mqtt.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/lock.mqtt.markdown b/source/_integrations/lock.mqtt.markdown index 5a9baf5a6cc..312714b401d 100644 --- a/source/_integrations/lock.mqtt.markdown +++ b/source/_integrations/lock.mqtt.markdown @@ -165,6 +165,8 @@ lock: command_topic: "home-assistant/frontdoor/set" payload_lock: "LOCK" payload_unlock: "UNLOCK" + state_locked: "LOCK" + state_unlocked: "UNLOCK" optimistic: false qos: 1 retain: true