From 126ef9c4aa0b59060759e31d2ec86f1d2904ae75 Mon Sep 17 00:00:00 2001
From: ESPHome Device Builder <device-builder@esphome.io>
Date: Sun, 26 Jul 2026 19:35:07 +1200
Subject: [PATCH] Edit esp-downstloungeentry.yaml

---
 esphome/esp-downstloungeentry.yaml | 14 ++++----------
 1 file changed, 4 insertions(+), 10 deletions(-)

diff --git a/esphome/esp-downstloungeentry.yaml b/esphome/esp-downstloungeentry.yaml
index 18d412e..2101c72 100644
--- a/esphome/esp-downstloungeentry.yaml
+++ b/esphome/esp-downstloungeentry.yaml
@@ -6,6 +6,7 @@
 # https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-downstloungeentry.yaml
 #:########################################################################################:#
 # VERSIONS:
+# v3.10 2026-07-26 Made the physical main switch the sole retained status publisher
 # v3.9 2026-07-25 Added on_connect republish and state guards for reliable two-way sync
 # v3.8 2026-07-20 Updated remote MQTT topics for the flattened downstairs lounge main lights topic
 # v3.7 2026-02-25 Updated yaml to zorruno layout V1.1
@@ -60,7 +61,7 @@ substitutions:
 
   # Project Naming
   project_name: "Zemismart Technologies.KS-811 Single"
-  project_version: "v3.9"
+  project_version: "v3.10"
 
   # Passwords & Secrets
   api_key: !secret esp-api_key # unfortunately you can't use substitutions inside secrets names
@@ -163,15 +164,8 @@ logger:
 # This adds device-specific MQTT command triggers to the common MQTT configuration.
 #:########################################################################################:#
 mqtt:
-  # Republish current mirror state whenever MQTT reconnects so the remote device
-  # knows our view of the state.
-  on_connect:
-    - mqtt.publish:
-        topic: "${mqtt_remote_status_topic}"
-        payload: !lambda |-
-          return id(Relay_1).state ? "${mqtt_remote_device_command_on}" : "${mqtt_remote_device_command_off}";
-        retain: true
-
+  # The physical main switch is the sole retained status publisher. This remote
+  # mirror only consumes that authoritative state and publishes commands.
   on_message:
     # Mirror remote state onto Relay_1 (only toggle if a change is needed)
     - topic: "${mqtt_remote_status_topic}"