sia-server/meson.build, branch v0.2.0IoT backend serverhttps://cgit.xengineering.eu/sia-server/atom?h=v0.2.02026-03-27T13:30:51ZAdd version to start / stop log messages2026-03-27T13:30:51Zxengineeringme@xengineering.eu2026-03-27T13:30:51Zurn:sha1:5b64946098839d3df679bdc7ef1c4cc4e692323a
This makes it more transparent which version is executed.
Move version string to VERSION.txt2026-03-27T13:28:51Zxengineeringme@xengineering.eu2026-03-27T13:28:51Zurn:sha1:6c920f59a20849deb882f60a3eab42b069914a7e
This new files can easily be included into Meson and Go. Passing it from
Meson to Go or vice versa is not that easy.
Thus the version string is now maintained in a dedicated file.
Add TP-Link HS100 support2026-03-26T16:46:54Zxengineeringme@xengineering.eu2026-03-26T16:46:54Zurn:sha1:5c7284640a6f0ddc0aa80178d5a3b91a5123b6c8Add 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.
tools: websocket: Add dummy and build integration2026-03-23T15:55:47Zxengineeringme@xengineering.eu2026-03-21T15:06:11Zurn:sha1:1a953af65ca5b3a83e7a50407a0c480ab22cc924
Adding support for Shelly devices requires usage of the Websocket API.
To make development easier a debug tool is created.
Since it is not relevant for users it is not an artefact included into
the deploy file archive. This also avoids later removing it which is by
definition of the public API (see README.md) a breaking change.
Add `-dev` version suffix2026-03-23T15:54:18Zxengineeringme@xengineering.eu2026-03-23T15:54:18Zurn:sha1:6b101a7fe8f2c9e4d608f68de773c423bf83a89b
This makes clear that the current version is not a clean release.
Release version 0.1.02025-12-20T14:38:31Zxengineeringme@xengineering.eu2025-12-20T14:38:31Zurn:sha1:b3092e759896ec038e6b42ee2310036fedcde41f
This is the first release of the Sia server. It is the Minimal Viable
Product (MVP).
Add CHANGELOG.md2025-12-20T14:23:33Zxengineeringme@xengineering.eu2025-12-20T14:23:33Zurn:sha1:134991968b8661aef17468aa3358af29a21b9f32Deploy README.md2025-12-20T14:13:17Zxengineeringme@xengineering.eu2025-12-20T14:13:17Zurn:sha1:f2e6dee6000258c95b5e0e52a9e17fafc35f6a5b
This information is useful in the deploy tar archive. Thus it is copied
there.
systemd: Add service and sysusers configuration files2025-12-20T13:59:15Zxengineeringme@xengineering.eu2025-12-20T13:59:15Zurn:sha1:b1bd87926098e03ffd983666d0746055122854fd
This makes it possible to run the Sia server executable on systemd-based
Linux distributions with systemd making system administration easier.
Maintaining these files in the source instead of packaging repository
was decided since systemd is the dominant init system across Linux
distributions and thus not every distribution-specific packaging repo
needs to re-invent the wheel.
Deploy default configuration2025-12-20T13:54:42Zxengineeringme@xengineering.eu2025-12-20T13:54:42Zurn:sha1:5f3cd750b2867854a1e05f66312062426024f676
The default configuration from the source tree is embedded into the
executable with Go's embed package to assume the correct defaults.
Furthermore it is now also part of the artifact tar archive to give
users an idea how a configuration file should look like.
Add Meson-tracked project version2025-12-20T13:50:28Zxengineeringme@xengineering.eu2025-12-20T13:50:28Zurn:sha1:b9ae3f51309ff0b38e7291239a0334e8df76b9d1
This allows to use the version of the project in the build system
independent from the version control system. Thus a source tar archive
can be built the same and also changing the version control system does
not change anything regarding the build process.
Add tar archive generation for deployment2025-12-20T13:40:31Zxengineeringme@xengineering.eu2025-12-20T13:40:31Zurn:sha1:e66f5b43a41283ddf4c4dae10e3b32e1fa0be077
Bundling all build artifacts into one tar archive is good practise to
make deployment easier and underline which files in the build directory
are important.
zstd was picked for compression because of the very good compression
ratio.
Make GOOS and GOARCH part of executable name2025-12-20T13:35:45Zxengineeringme@xengineering.eu2025-12-20T13:35:45Zurn:sha1:e4eeebd12a41b65da02087d93e19ee719723fd8b
This renames `sia-server` to `sia-server-linux-amd64`. This makes clear
for which target environment the executable is built and allows to later
place additional executables for other environments too without name
collisions.
Implement passing user configuration2025-12-20T13:20:42Zxengineeringme@xengineering.eu2025-12-20T13:20:42Zurn:sha1:167772b87698cce479090dbe5bd3d1cc7c1bc808
This allows overwriting values of the default configuration with custom
ones.
Add default config parsing2025-12-20T13:06:34Zxengineeringme@xengineering.eu2025-12-20T13:06:34Zurn:sha1:d6fa255b1df26a12329a614601a027e074aabeb2
This is a first step towards configurability.
Add Meson target `test` for unit testing2025-12-20T13:01:51Zxengineeringme@xengineering.eu2025-12-20T13:01:51Zurn:sha1:ba367f41077be88338db981c88802d7292ac7013Separate Homematic code2025-12-20T12:47:56Zxengineeringme@xengineering.eu2025-12-20T12:47:56Zurn:sha1:6978bf0635372b0330629469fb86ddb640cdd863
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 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.
Add cache implementation2025-12-20T12:00:52Zxengineeringme@xengineering.eu2025-12-20T12:00:52Zurn:sha1:853e3fd5f2b4e622d4e35c0e3c2fad6c358cb8ae
This avoids frequent MQTT messages containing the same state.
Add Meson build system2025-12-08T20:14:18Zxengineeringme@xengineering.eu2025-12-08T20:14:18Zurn:sha1:1324f1efdbc9b34a6821be26a45c152d8afea614
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.