sia-server - IoT backend server

Age	Commit message (Collapse)	Author
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.
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.
14 days	Add hello world as main.go	xengineering
	This is just a minimal starting point for the repository.