Home automation using Node.js, raspberry pi and tinkerforge | Hacker News Reader

Home automation using Node.js, raspberry pi and tinkerforge

blog.lastlog.de

78 pointsqknight22 comments

Nice writeup! Aand tinkerforge is pretty interesting, never heard of it. Wrote something for my own home that I use everyday. It mostly controls my IR/X10/XBMC/etc. but it has scheduling and a UI to build custom remotes. I host it on a tower connected to my tv and/or one of my raspi's and use arduino's to farm out the work. I have found that reliability is not too too hard to get down, but understanding state is where things get messy. Especially with IR beacuse it's one way. Contemplated a camera or stick on light sensors. Still haven't come up with a satisfactory idea. It was my first django app with jquery mobile on the frontend. I find that serving it up via a raspi is a bit heavy though. Maybe some simple profiling would fix. https://github.com/dandroid88/webmote

interesting. this one-way problem was the main reason not to use 433mhz controllers.

thanks for your posting.

Very interesting writeup, that's a cool project.

Now to make it still cooler and Jarvis-like, you can add voice commands with the Raspberry Pi. Somebody did it here [1] using the Wit Speech API [2]

[1] http://blog.fmpwizard.com/blog/go-cortex-using-wit-ai-using-...

[2] https://wit.ai/blog/2014/02/12/speech-api

thanks for your feedback! it is very cool stuff but i do not want to rely on external SaaS stuff.

anyway, it seems to be really cool - especially the part where the server replies with JSON ;-)

Using the super cheap 433mhz wirelessly switchable power plugs using the raspberry pi is also super low cost, it's just not secure against tampering. https://blog.codecentric.de/en/2013/03/home-automation-with-... has some details.

I have a good number of 433mhz switchable & dimmable outlets controlled by an Arduino with a 433mhz transmitter. It was a good weekend project that I am extending at the moment - including real world controls of my Sonos components (the Arduino talking to them via SOAP).

I've just ordered 10m of RGB LED strip, which is the next component I plan to control with an Arduino which will communicate with the first via an Ethernet shield and a protocol I am yet to devise!

Yes, all of this is fairly pointless but it's keeping my brain active whilst I recover from some fairly extensive surgery!

thanks for providing your link. very nice writeup but as i pointed out, 433mhz is not an option for me as i wanted to know if a set(..) really was working and 433mhz usually doesn't provide any return value.

seeing your post earlier would have saved me some effort getting into REST ;-)

I've been thinking of my own way to do something similar, but this setup seems (after reading the first part and looking over the rest) too easy to screw up and do something dangerous with a lot of electricity for me. Proceed with caution.

For a safer method of interfacing with AC voltage you can use something like the PowerSwitch Tail[1]. It is a little pricy (~$26 at Adafruit.com) and only works with one plug, but it means that you don't have to mess with AC voltage directly.

@cscru There is a 240V kit version of the PowerSwitch tail available.

[1] http://www.powerswitchtail.com

good point. but i do think that my setup works stable and safe for me.

however, i had added the disclaimer because others might be facing a different situation and therefore they are warned.

If you want to try out another technology, Erlang would be a pretty good fit for this.

I think better for him to use Node (or really, any language that will simply fall over in the case of failure), unless extremely familiar with a supervisor paradigm. Given the warnings he prefaces everything with, including not to toggle a relais(?) more than 10/min, it seems all too easy to accidentally have a supervisor strategy that in the face of failure could surpass that.

Well, he seems interested in trying different things, and Erlang is very well suited to something like what he's doing. He certainly needs to take adequate steps to ensure that things don't blow up, but long term, having something that's stable and doesn't fall over is going to be a more dependable solution.

"including not to toggle a relais(?) more than 10/min"

That's actually exactly what the latter two configuration parameters for OTP supervisors are for - to tell the supervisor how many failures in what unit of time it should consider "normal".

I know. Does -he- know, though? That was my point. Per the original comment, Erlang -would- be perfect for it. It would not, however, be perfect for someone who is not knowledgeable about OTP to use it as a learning project, because any oversight that leads to unexpected behaviors could burn his house down (or whatever toggling a relais too much does).

don't toggle too fast -> gen_server per relay -> sleep for 6 seconds in init().

i will consider erlang for the next project - you got interesting points.

Nice article. Never heard of tinkerforge before, interesting tech. And using Node.js for home automation is interesting. I wrote my home automation in C and use various Arduino's and I plan to add some Pi's.

I installed Loxone[1] when we built a house and can recommend it. Works right out of the box with web and mobile apps and has multiple APIs to hack with. Only (minor) downside is that you need a VirtualBox for the (otherwise good) configuration software if you're not on Windows.

[1] http://www.loxone.com/enus/

At $550 just for the controller, $109 for a light sensor and $160 for a temperature sensor, it seems quite pricy.

i guess my setup is about 200-300 euros summing all the single devices and casings together.

this does not include the days of assembling the hardware.

i've seen many such proprietary solutions and i dislike them all for various reasons. i've added a list in the motivation of my article.

why do these vendors not honor open source development?

Reply on news.ycombinator.com