sia-server/cache.go, branch v0.2.0IoT backend serverhttps://cgit.xengineering.eu/sia-server/atom?h=v0.2.02026-03-26T19:57:22ZAdd `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.
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.
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.
Update payload for contact states2025-12-20T12:14:09Zxengineeringme@xengineering.eu2025-12-20T12:14:09Zurn:sha1:b58d415169180e58c0661a09c97d311e2eb0c96a
`true` and `false` are bad values to describe a contact state. `open`
and `closed` make much more sense.
Add cache implementation2025-12-20T12:00:52Zxengineeringme@xengineering.eu2025-12-20T12:00:52Zurn:sha1:853e3fd5f2b4e622d4e35c0e3c2fad6c358cb8ae
This avoids frequent MQTT messages containing the same state.