| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
This allows the sending part of the code to decide about the retain
flag. The MQTT go routine will set it accordingly.
|
|
This scales better when additional receiving routes will be added.
|
|
This let's the Sia server receive cover movement commands. For now they
are simply logged.
|
|
This simplifies debugging.
|
|
The default config JSON is embedded as bytes into the executable.
Instead of constants the default values are now parsed from these
embedded bytes.
|
|
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.
|
|
This issues ping request / response messages between the Sia server and
the MQTT broker making sure an interrupted connection is noticed.
|
|
This is a central requirement to ensure a restart of the MQTT broker
does not harm the Sia server operation.
|
|
This makes connection loss visible during debugging.
|
|
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.
|
