master:
devel:
- Introduction
- How to get the example working?
- Device configuration
- Event bus
- How to add control modules?
- How to add data processors?
- Communication protocols
- Copyright
HomeCtrl is an event based home or building automation system. The name is constructed from "home" and the label of the English keyboard control button "Ctrl".
You are currently looking at version 3 of the HomeCtrl software. This version is a Java application, that acts as a server. It is designed as a central control unit that can communicate with devices and user interfaces using different communication protocols with my COM library as a back-end. The current available protocols are HTTP for reading and writing and EnOcean for reading.
The HomeCtrl software consists of 6 projects:
- homectrl: the core application
- homectrl-com-if: all the stuff for interacting with the COM library the world beyond that
- sensors: software "sensors" for stuff, that is computed by the server
- dataprocessing: software modules for sensor data preprocessing
- controls: software modules for controlling devices
- server: the application project with all configurations
Version 3 of HomeCtrl is the first, where the server can actually control the devices. In versions 2 and earlier, devices where directly controlled by the user and the server was only creating the connection between user and devices. There is no user interface software yet, but that is planned (besides, a well configured system doesn't need user interaction ;)). The runtime structure and behavior of the application is defined in a device configuration file, which is written in JSON. It contains all devices, the processors and the controls with their individual settings.
- Compile the server project as runnable jar file (simply build the Gradle file in the main directory).
- Rename example-server.properties to server.properties.
- Change the data in server.properties to what you like (or go with the default).
- Rename example-configuration.json to configuration.json.
- Change the configuration in configuration.json to what your system looks like. This one might be a bit tricky. In case of doubt, check the chapter about device configuration.
- Start the application and lean back.
TODO
Light at the end of the tunnel ...
I know that this manual JSON writing is hideous. I'm planning on a visual tool to create and edit configuration files. It will mostly be colorful clicking and dragging and dropping. Even a simulation mode would be nice.
Unfortunately, it will probably take a while to get to this point.
TODO
TODO
TODO
TODO
TODO