Skip to main content

DIY home automation v2

Previously I set up a simple home automation system for controlling outlets at home. So far I've used the system for controlling various lights at our home. I've been satisfied with oulet controlling via browser but I wanted something more.

Objective


I had a idea of temperature and humidity monitoring via Raspberry Pi. I was already browsing for electronics components needed for building a system with sensors but buying single components seemed a bit expensive and I would also have to actually connect all the components to RPi and write the code to read the sensor data.

Mainly because of the price the components I started looking for a pre-built system with the preferred sensors. Almost immediately I came across Proove's sensor that has indoor and outdoor temperature sensors and a indoor humidity sensor. Best part of the pre-built system is that it's already compatible with TellStick system that I used for controlling outlets.

I decided to buy the pre-built sensor system. I just needed to figure out how to read the sensor values and display them on the same UI that I built for controlling outlets.

Sensor data


The sensor system is nice in the way that it automatically sends it's sensor data in some sort of broadcast and the TellStick Duo automatically receives all the data. Something's also flaky with the sensor system because it sends sensor data from a bunch of sensors. Most of the sensor data is just invalid data and it's up to the user to determine which sensors are sending valid data.

tdtool --list-sensors

Reading and decyphering sensor data


Decyphering which sensors were sending valid data was a manual process of viewing the sensor data and comparing that to the values displayed on the sensor system's lcd screen. I managed to figure out that my system sends outdoor temperature with sensor id 135 and indoor temperature and humidity with sensor id 136.

Reading sensor data via python


The telldus-core library that's used to control the outlets also provides functionality to read sensor data. It was just a matter of figuring out how to read the data and I found a good example from github.

Result


As previously the REST API is written with Python and it uses the C-library to communicate with TellStick Duo and the UI functionality is written with JavaScript. Reading the sensor data and viewing it in the UI is implemented in the same code base as the outlet controller.

I just added a new endpoint /sensors that returns sensor data for the two sensors and added some UI functionality to read and view the data.

Sensor data above outlet control


Few things to know about the code

 

Because the sensor system sends invalid data with bogus id's I extracted the sensors id's to their own module sensorconf.py that defines the id's for indoor and outdoor sensors 

The UI has names for the different sensor values but I didn't separate them from the logic but instead hard coded them.

Comments

  1. Hello Jori,

    Nice blog! I am editor at System Code Geeks (www.systemcodegeeks.com). We have the SCG program (see www.systemcodegeeks.com/join-us/scg/), that I think you’d be perfect for.

    If you’re interested, send me an email to

    Eleftheria.drosopoulou@gmail.com and we can discuss further.

    Best regards,
    Eleftheria Drosopoulou

    ReplyDelete

Post a Comment

Popular posts from this blog

Simple code: Immutability

Immutability is a special thing that in my mind deserves a short explanation and praise. If you're familiar with functional programming you surely recognice the concept of immutability because it's a key ingredient of the paradigm. In the world of object oriented programming it's not as used and as easy to use approach but there are ways to incorporate immutability to parts of the code and I strongly suggest you to do so. Quick intro to immutablity The basic idea of immutability is unchangeable data.  Lets take a example. We have a need to modify a object's property but because the object is immutable we can't just change value but instead we make a copy of the object and while making the copy we provide the new value for the copy. In code it looks something like this. val pencil = Product(name = "Pencil", category = "Office supply") val blackMarker = pencil.copy(name = "Black marker") The same idea can be applied in functions and metho

Simple code: Contracts

Code works around contracts and contracts should be carefully thought and crafted. What are contracts A High abstraction level of contracts for code are API's. They define a interface that is basically a contract that the producer and consumer of the API agree to use to communicate with each other. Two common forms of API's are libraries that are used in code and external API's  that are used via HTTP, RPC etc. When thinking in a bit deeper contracts consist firstly of functions, methods or external endpoints and secondly of data, more precisely on data models and data types within the models.   Defining contracts Contracts should always be defined with careful thought. I've come accross few times to someone saying that "this is for intenal use only so it doesn't need to defined and/or documented as thoughtfully as a public API would be" but I disagree with that. The same care should be be given to internal and external contracts because the contracts are

Simple code: Unit tests

Unit tests are the developers number one safety net. Let that sink in. This is the number one reason for writing unit tests. Unit tests are written by developers for developers to ensure that the code works as expected and handles happy and sad paths correctly. With enough unit test coverage the tests enable a safe environment for refactoring and rewriting code. Unit test scope Unit test should test a single thing, a method or function call and it should test only one use case within. In other words a unit test should test a function with a single input. This is a important guideline to understand. When a unit test tests a function with single input it makes the test isolated, repeatable and predictable. Example of good tests: @Test fun findsAddress() {   val address = findAddress("Stevens street 35", "Southport", "Australia")   assertThat(address).isNotNull() } @Test fun doesNotFindAddress() {   val address = findAddress("Stevens street 697", &q