sia-server/main.go, branch v0.2.0

Add version to start / stop log messages

2026-03-27T13:30:51Z

This makes it more transparent which version is executed.

Add Shelly / TP-Link device discovery

2026-03-26T20:34:16Z

This announces Shelly and TP-Link devices with an empty MQTT message. This makes it possible that a client can display the available devices.

Add TP-Link HS100 support

2026-03-26T16:46:54Z

Refactor and add routing concept

2026-03-25T20:09:11Z

This scales better when additional receiving routes will be added.

Add MQTT subscription for /cover//movement

2026-03-25T20:09:11Z

This let's the Sia server receive cover movement commands. For now they are simply logged.

Fix warning about OS signal listener

2026-03-23T15:55:47Z

An unbuffered channel triggers a warning here. This can easily be fixed by switching to a buffered channel with buffer length 1.

Do not print start banner on usage

2025-12-20T14:03:33Z

Before this commit the start banner `+++ Started Sia server +++` was printed before the usage instructions. The stop banner was not printed. The intended behaviour is to print none of them. This is not implemented.

Disable log timestamps

2025-12-20T13:30:37Z

The primary target environment is a systemd-based Linux system. There the logging system of the operating system will timestamp the log messages.

Implement passing user configuration

2025-12-20T13:20:42Z

This allows overwriting values of the default configuration with custom ones.

Use default config

2025-12-20T13:11:13Z

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 Homematic code

2025-12-20T12:47:56Z

Similar to a previous refactoring of the MQTT-related code this removes all Homematic logic to a dedicated file. The only connection to the outside is the `tx chan MQTTMessage` channel and the `HomematicRun()` function. This makes the code more modular.

Separate MQTT logic

2025-12-20T12:27:42Z

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.

Raise to QoS 1

2025-12-20T12:23:17Z

This ensures the state updates reach the broker. QoS 2 is not required since multiple reception of the same state will not make a difference.

Switch ClientId to `siaserver`

2025-12-20T12:18:55Z

The old version `sia-server` was problematic since the MQTT specification [1] ensures only this list of valid characters: 0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ For every other character the broker might support this or not. [1]: https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718031

Publish state in retained mode

2025-12-20T12:09:40Z

This ensures the MQTT broker caches the state when it is sent by Sia and sends it via MQTT to new MQTT clients. Thus no state polling is required by the MQTT client.

Reduce polling period to 50 ms

2025-12-20T12:05:09Z

The human reaction time is roughly 100 ms. The Nyquist-Shannon sampling theorem [1] is used for an approximation how often it is required to sample without humans noticing any delays. [1]: https://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampling_theorem

Add cache implementation

2025-12-20T12:00:52Z

This avoids frequent MQTT messages containing the same state.

Add continuous polling execution

2025-12-20T11:55:57Z

This state polls the device states with 500 milliseconds period and publishes the state on every poll.

Refactor with Poll() function

2025-12-20T11:51:01Z

This function allows to reduce the lines of code in main() further.

Refactor with Start() and Stop()

2025-12-20T11:46:28Z

This reduces the lines of code of the main() function significantly and groups all start and stop actions.

Add logging for init and de-init steps

2025-12-20T11:42:04Z

This helps to debug potential issues.

Run go fmt

2025-12-20T11:37:52Z

Refactor MQTT connect / disconnect

2025-12-20T11:33:00Z

Change topic structure

2025-12-20T11:27:47Z

The new structure for the contact states is the following. /contact//state The reasoning is: - `` allows using multiple (Sia) services on the same broker - `contact` as device type indicates contact-specific semantics - `` makes different contacts distinguishable - `state` is the actual payload

Change topic prefix to `sia`

2025-12-20T11:23:21Z

The old prefix `sia-server` was longer and not completely correct. The topics under this prefix never belong more to the server or the clients. Thus only `sia` seams to be a good solution.

Refactor with OPENCCU constant

2025-12-20T11:18:41Z

This unifies the HOST and PORT constants used so far and removes the need for a fmt.Sprintf() call.

Publish contact state with MQTT

2025-12-20T11:14:01Z

This demonstrates the ability to take information from the Homematic system to MQTT. It is a major proof of concept step towards a minimal viable product (MVP) Sia server.

Adopt homematic-go example

2025-12-10T20:14:38Z

This requests a list of devices from the Homematic central device and then queries the state of every `SHUTTER_CONTACT`. This is a good starting point for the server logic.

Add hello world as main.go

2025-12-08T20:08:46Z

This is just a minimal starting point for the repository.