| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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
|
|
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.
|
|
This unifies the HOST and PORT constants used so far and removes the
need for a fmt.Sprintf() call.
|
|
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.
|
|
This dependency is required to use MQTT with Go.
|
|
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.
|
|
This is the minimal viable product (MVP) of this library suitable to
build the MVP of the sia-server.
|
|
This allows to add dependencies to this Go project.
|
|
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.
|
|
This is just a minimal starting point for the repository.
|
|
|
