Document private MQTT topics and the 1.1 upgrade
This commit is contained in:
1 parent
593f86e6dd
commit
6ba2656c9d
3 files changed
+316
-1
No files matched your search
@@ -0,0 +1,21 @@
|
||||
# Changelog
|
||||
|
||||
## 1.1 — 2026-10-03
|
||||
|
||||
- Full command, state and availability topics are required in the private INI.
|
||||
- Subscription, state publication, availability and Last Will use those settings.
|
||||
- Generic shared topic examples; no installation-specific topic prefixes in the current source.
|
||||
- MQTT client ID can also be configured in the INI.
|
||||
- Missing, blank, duplicate, wildcard and oversized topics are rejected at startup.
|
||||
- Upgrade instructions preserve existing topics and the existing Home Assistant entity.
|
||||
- 24 behaviour/configuration tests with mocked MQTT and Docker.
|
||||
|
||||
## 1.0 — 2026-10-03
|
||||
|
||||
- MQTT-controlled handover between MeshCore WebUI and a native phone app.
|
||||
- Independent systemd controller; stops/starts only `meshcore-webui`.
|
||||
- Confirmed Docker state, retained JSON and MQTT availability/Last Will.
|
||||
- Automatic MQTT reconnect without changing container state.
|
||||
- Non-retained ON/OFF commands and idempotent container operations.
|
||||
- Home Assistant package, Debian installer and example credentials config.
|
||||
- 16 behaviour tests; initial installation and switching confirmed working.
|
||||
Reference in new issue
Block a user