As you might have noticed I am currently updating the household with some "smart devices". All of the old 433 MHz actuators have been replaced by WiFi actuators from Sonoff. At the moment I am controlling all the actuators via the web-interface of HomeAssistant. This is basically great, but I do not want to be a slave of my smartphone/tablet/PC. Especially not for such a simple task like turning lights on or off. When I browsed itead I found a "smart switch" - the Sonoff Touch. Seconds later it was on my list of ordered items.

If you have used Home Assistant it is very likely that you also glanced at the "History"-function of the GUI. I really like this view, because it shows you relevant data in a simple way and it is very easy to find basic connections between elements. So I would like to use this feature also in the future. So you might ask yourself "Where is the problem?". If we have a look at the documentation of Home Assistant you will notice that the default database is a sqlite3-database.

One of my biggest problems is that I am having so many different projects. So if I do not write down important steps I tend to forget them and I have to find the solution again from scratch. Because I am doing this now for the third time I am now writing it down.

Communicating with a huge number of clients requires a simple, fast and reliable solution. Message queues seem to solve this problem in a very efficient way. There is a reason why many people treat MQTT as the "language of the Internet-of-Things".

Due to the limited ressources of our IoT-devices we should try to optimize our code, in case we do not want to wait long time each time we access our nodes. In this post I will present you some simple tricks how you can make your device more reactive. The actions are listed from very quick steps to a bit more complex tasks. (May I am going to update this post after some time.)