fix: require configured mqtt iata before broker connect

release-notes.yml

@@ -344,3 +344,24 @@ releases:
         area: web-panel
         text: "Updated the repeater web panel and custom CLI docs to reflect full web CLI access and the new HTTP-to-HTTPS behavior."
     breaking_changes: []
+
+  - track: repeater-mqtt
+    version: "1.3.7"
+    tag: "repeater-mqtt-eastmesh-v1.3.7"
+    date: "2026-04-20"
+    previous_version: "1.3.6"
+    summary: "Made MQTT IATA explicit on fresh repeater installs, blocked broker connects until it is configured, and surfaced the missing-IATA state in the web panel and CLI status."
+    changes:
+      - type: changed
+        area: mqtt
+        text: "Changed fresh repeater_mqtt defaults to use `mqtt.iata=UNSET` instead of pre-filling Melbourne."
+      - type: fixed
+        area: mqtt
+        text: "Blocked EastMesh and LetsMesh broker connection attempts while `mqtt.iata` is unset, and reported `invalid iata` in `get mqtt.status` for enabled brokers until a real code is saved."
+      - type: changed
+        area: web-panel
+        text: "Added a top-of-page warning banner and inline MQTT Settings warning when the repeater still needs its MQTT IATA configured."
+      - type: docs
+        area: mqtt
+        text: "Updated the custom CLI and web panel docs to describe the unset-first MQTT IATA flow and the resulting broker behaviour."
+    breaking_changes: []