From 8d9a6955f9f21d5503d591737ef737deaca4d367 Mon Sep 17 00:00:00 2001 From: Claude Bot Date: Wed, 28 Oct 2026 02:12:33 +0000 Subject: [PATCH] docs(mosquitto): point Shelly MQTT server note at shelly-manager root group settings shelly-manager's /api/v1/mqtt/push is being removed in favour of group settings (konairius/shelly-manager group-settings M3). Co-Authored-By: Claude Opus 5.5 --- .../apps/home-assistant/mosquitto-iot-service.yaml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/kubernetes/apps/home-assistant/mosquitto-iot-service.yaml b/kubernetes/apps/home-assistant/mosquitto-iot-service.yaml index 187cb4a4..59456d79 100644 --- a/kubernetes/apps/home-assistant/mosquitto-iot-service.yaml +++ b/kubernetes/apps/home-assistant/mosquitto-iot-service.yaml @@ -1,10 +1,11 @@ --- # Mosquitto broker LoadBalancer on the BGP-routed off-link pool. IoT # devices reach the broker via the UDM's BGP-learned routes — no -# on-link L2 announce on v30iot. Companion Shelly fleet is updated via -# shelly-manager's `/api/v1/mqtt/push` so each device's stored MQTT -# server resolves to `mqtt.renner.uno`, not a bare IP — that way future -# IP changes only need DNS updates, no reflash sweep. +# on-link L2 announce on v30iot. The Shelly fleet's MQTT server is set +# by shelly-manager's root group setting `mqtt.server` (Groups → All +# Shellies → settings) and reconciled to every device, so each device's +# stored MQTT server resolves to `mqtt.renner.uno`, not a bare IP — that +# way future IP changes only need DNS updates, no reflash sweep. apiVersion: v1 kind: Service metadata: -- 2.54.0