iNELS InfluxDB

This project handles the saving of home automation events from the proprietary iNELS home automation suite. It parses events then saves them to an InfluxDB database which then can be displayed using data monitoring tools such as Grafana.

How to run

Docker and Docker Compose should be installed on the machine before proceeding.

Steps to start the inels-influxdb container:

• Clone this repository to the system
  • git clone https://github.com/domenix/inels-influxdb.git
• Change into the directory that was downloaded
  • cd inels-influxdb
• Rename example.env file to .env
  • mv example.env
• Edit the properties inside .env according to your preference, keep in mind that DB_TOKEN should be something secure
• Change into data
  • cd data
• Either rename export_example.imm to export.imm or export the configuration from the iNELS software and place it in this directory
• Start the container
  • docker-compose up -d

Steps to start InfluxDB and Grafana:

• Change into the monitoring directory
  • cd monitoring
• Rename example.env file to .env
  • mv example.env
• Edit the properties inside .env according to your preference, DOCKER_INFLUXDB_INIT_ADMIN_TOKEN should match DB_TOKEN that was set previously
• Start the containers
  • docker-compose up -d

If done correctly, InfluxDB should be accessible on the machine on port 8086 and the defined bucket should have some data already in it. Access Grafana on port 3000 and makes some cool looking dashboards for your home automation system. Enjoy!

Troubleshooting

You can see the logs of the container by using docker-compose logs --follow. It will watch the logs of all services defined in the docker-compose.yml file present in the current directory. Use docker-compose logs --follow inels-influxdb in order to follow one specific service or execute docker logs inels-influxdb in any directory of your system.

If you want to see inside of the containers, you can jump into them by executing docker exec -it <container_name> sh.

Building the image

TODO

Todo

• Queue up events in the database thread if the db server becomes unavailable.
• Database error handling should be better compartmentalized (right now errors are just printed out from the influxdb-client library) and connection loss during saving should be handled as well similarly to the connection thread.