sia-server - IoT backend server

Age	Commit message (Collapse)	Author
2 days	Switch ClientId to `siaserver`	xengineering
	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
2 days	Update payload for contact states	xengineering
	`true` and `false` are bad values to describe a contact state. `open` and `closed` make much more sense.
2 days	Publish state in retained mode	xengineering
	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.
2 days	Reduce polling period to 50 ms	xengineering
	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
2 days	Add cache implementation	xengineering
	This avoids frequent MQTT messages containing the same state.
2 days	Add continuous polling execution	xengineering
	This state polls the device states with 500 milliseconds period and publishes the state on every poll.
2 days	Refactor with Poll() function	xengineering
	This function allows to reduce the lines of code in main() further.
2 days	Refactor with Start() and Stop()	xengineering
	This reduces the lines of code of the main() function significantly and groups all start and stop actions.
2 days	Add logging for init and de-init steps	xengineering
	This helps to debug potential issues.
2 days	Run go fmt	xengineering

2 days	Refactor MQTT connect / disconnect	xengineering

2 days	Change topic structure	xengineering
	The new structure for the contact states is the following. <prefix>/contact/<id>/state The reasoning is: - `<prefix>` allows using multiple (Sia) services on the same broker - `contact` as device type indicates contact-specific semantics - `<id>` makes different contacts distinguishable - `state` is the actual payload
2 days	Change topic prefix to `sia`	xengineering
	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.
2 days	Refactor with OPENCCU constant	xengineering
	This unifies the HOST and PORT constants used so far and removes the need for a fmt.Sprintf() call.
2 days	Publish contact state with MQTT	xengineering
	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.
3 days	Add github.com/eclipse/paho.mqtt.golang	xengineering
	This dependency is required to use MQTT with Go.
12 days	Adopt homematic-go example	xengineering
	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.
12 days	Add homematic-go v0.1.0	xengineering
	This is the minimal viable product (MVP) of this library suitable to build the MVP of the sia-server.
12 days	Add Go module xengineering.eu/sia-server	xengineering
	This allows to add dependencies to this Go project.
2025-12-08	Add Meson build system	xengineering
	Meson as a general purpose build system is mightier than what the Go tool can provide. Furthermore it makes it possible to unify build, run and other workflows across projects with different languages.
2025-12-08	Add hello world as main.go	xengineering
	This is just a minimal starting point for the repository.
2025-12-08	Add AGPL as LICENSE.txt	xengineering