IoT

Domotiga on Raspberry Pi 2

I have been running Domotiga on the new Raspberry Pi 2 for a few weeks now after the initial months using the "old" Raspberry Pi. And I have to say the performance is very noticeable. I'm controlling Domotiga with the desktop client using VNC. I also control Domotiga with the web interface, but I find it faster to use VNC. Compared to the "old" Raspberry Pi, the response is almost instant, and the CPU usage is never over 25% compared to the the "old" one that used 100% every time Domotiga had work to do. That's the beauty of quad core CPU.

Lessons learned - First year

After a year I will say I have gained some experience in the field of DIY IoT and home automation. The first lesson is that it's not easy to plan what you want and actually go for it. Things and desires change on the way to the goal. I started with a Tellstick Duo, but I feel I outgrew it.

X10 PIR sensor for RFXCOM transceiver

After a lot of experimentation, research and prototyping, I finally have all the parts I need to finish my PIR sensors. I plan to have one in each room, well almost.

They will have two functions. Primarily they will be used to track us and switch lights and heating (Nexa remote switches) as appropriate when we are home. The switching will follow certain rules, like time of day, who is home, weekday, weekend etc. When no one is home, they will be part of the security system and notify us, using Pushbullet, if they sense movement while we are not home. Both functions will be controlled by DomotiGa running on a Raspberry Pi, using a RFXCOM rfxtrx433e USB transceiver.

Tellstick Duo out - RFXtrx433E in

Tellstick DuoAfter nearly a year running my home automation with Tellstick Duo I decided to upgrade to RFXCOM. I say upgrade because Tellstick has too few options apart from it's own simple interface where you can switch on/off and dim devices. I used Switch King and EventGhost (Windows), one of the few good programs that works with Tellstick. If you own a Tellstick and don't want to ditch it, I highly recommend the software mentioned.

From ThingSpeak to ThingTweet

I have been using ThingSpeak for a while now and I decided to create my own API for logging IoT readings. The main reason for this is that ThingSpeak require me to manually set it up for each thing I want to log. I think this is tiresome and not as easy as I want it to be. Also I need one api key for each of my connected things. Last, but not least, I don't know how long my data is my data. They may "pull the plug" at any time and have me pay for the service (something I can easily understand).

Subscribe to RSS - IoT