sia-server/mqtt.go, branch v0.2.0IoT backend serverhttps://cgit.xengineering.eu/sia-server/atom?h=v0.2.02026-03-27T13:43:56ZAdd server version publishing2026-03-27T13:43:56Zxengineeringme@xengineering.eu2026-03-27T13:39:33Zurn:sha1:3158a0a132d6af4de78c9be90e45834350cfd414
This makes it possible that the client adapts it's behaviour easily to
the server version making support of breaking API changes during early
development and debugging easier.
Add `Retain` attribute to MQTTMessage2026-03-26T19:57:22Zxengineeringme@xengineering.eu2026-03-26T19:57:22Zurn:sha1:443ba52ab3f49a28e8874ebcb5476e36c3defb4c
This allows the sending part of the code to decide about the retain
flag. The MQTT go routine will set it accordingly.
Refactor and add routing concept2026-03-25T20:09:11Zxengineeringme@xengineering.eu2026-03-25T19:33:22Zurn:sha1:476db7047a9c650057c034c647ea66f3c38e8a53
This scales better when additional receiving routes will be added.
Add MQTT subscription for /cover/<id>/movement2026-03-25T20:09:11Zxengineeringme@xengineering.eu2026-03-23T19:53:40Zurn:sha1:1bd2833f81379f25b29ab5d929f14e51700fa471
This let's the Sia server receive cover movement commands. For now they
are simply logged.
Add MQTTMessage.String()2026-03-25T20:09:11Zxengineeringme@xengineering.eu2026-03-23T19:46:34Zurn:sha1:64f8cf0630ce51349b94aca2f91617d373ee800d
This simplifies debugging.
Use default config2025-12-20T13:11:13Zxengineeringme@xengineering.eu2025-12-20T13:11:13Zurn:sha1:224d52d1033d8ccce5087c9bee5a63457830a13a
The default config JSON is embedded as bytes into the executable.
Instead of constants the default values are now parsed from these
embedded bytes.
Implement <prefix>/server/health2025-12-20T12:57:21Zxengineeringme@xengineering.eu2025-12-20T12:57:21Zurn:sha1:c6249f96b09d9862f160c439ac8a97a92edb8228
This indicates if the Sia server is available and connected to the MQTT
broker.
Using the MQTT Will messages these will also be sent if the Sia server
unexpectedly crashes.
Using the retained flag it is ensured that freshly connected MQTT
clients will receive these messages even when they missed the initial
one from the Sia server.
Add MQTT keepalives2025-12-20T12:43:31Zxengineeringme@xengineering.eu2025-12-20T12:43:31Zurn:sha1:58d7c51baa053be8d6d4ec5f409fceef1c7c11b5
This issues ping request / response messages between the Sia server and
the MQTT broker making sure an interrupted connection is noticed.
Implement MQTT reconnects2025-12-20T12:38:14Zxengineeringme@xengineering.eu2025-12-20T12:38:14Zurn:sha1:bfd7b70c927d60242fb77b9b58a7c7aad73cf1bc
This is a central requirement to ensure a restart of the MQTT broker
does not harm the Sia server operation.
Log MQTT disconnect2025-12-20T12:32:55Zxengineeringme@xengineering.eu2025-12-20T12:32:55Zurn:sha1:12198f4d921eb6406d08a122e2e51971bf65e7fa
This makes connection loss visible during debugging.
Separate MQTT logic2025-12-20T12:27:42Zxengineeringme@xengineering.eu2025-12-20T12:27:42Zurn:sha1:96299467958aaffdbef5cb8ae780d3abeddfcaba
This reduces the coupling between the MQTT-related code and everything
else to a single `tx` channel of type `MQTTMessage`.
This improves the code quality significantly.