Where jcw’s Housemon is moving

jcw (father of the Jeenodes) is still working on his home monitoring/home automation system – and he is moving it in a interesting direction, partially along the same lines as I have been (slowly) moving my own monitoring system.

He’s now moved a significant portion on by using Go – something I have not looked at yet.

Here’s where I’m headed with all this:

Flow is the foundation for it all: dataflow programming is – p e r f e c t – for real-time apps such as HouseMon and Tosqa. The fact that it’s called 0.1 just reflects my inexperience with it all. But there’s no way back. There are lots of “worker” components in the 0.1 release already. They don’t really belong there, but it was easy to develop them that way. These will be moved to JeeBus soon – due to the registry, this won’t affect the program code (just a few “import” lines).
JeeBus will collect all the functionality which is generally useful for HouseMon and Tosqa: a HTTP web server, MQTT messaging (client and server), websockets, the LevelDB database, a JavaScript engine for implementing logic not built into the core, and AngularJS with CoffeeScript on the browser side. I’ve been repeating this for some time now, and it won’t change. Lua is out (but it could easily be tied in as external MQTT client, same for any other language). With Flow now in the picture, JeeBus will also include lots of fairly general “workers”, tying into the serial port, websockets, MQTT, etc.
HouseMon is simply a small “main” application built on top of the JeeBus package. It needs less than a dozen lines of code to make a usable application. In addition, HouseMon is where additional home-monitoring and -automation specific stuff can be implemented: in Go, as dataflow Workers and Groups, as JavaScript / CoffeeScript definitions, and as external processes: shell, Lua, Python, Ruby, Java, you name it. I see HouseMon as the proving ground for everything else, with the option to migrate whatever makes sense to JeeBus or Flow.
The other thing which hasn’t changed is “developer mode”. This is a setup now in JeeBus, which adds node.js and “gin” to the mix, to support live reload while making changes. I’ve briefly stepped away from it while hacking on Flow, but will definitely bring it back to the foreground once HM/JB and client-side development enter the picture again.

[From HouseMon + JeeBus + Flow – JeeLabs Café – JeeLabs . net]

Updated FHEM for our heating control

We are running a multitude of home automation systems – but the one that communicates with all the heating is still FHEM, one of the few that can actually communicate with our FHT80b thermostats.

Here is tonights picture of our houses heating :


The green line show how open each actuator (aka valves on our radiators) are in each of the 3 heating zones in the house.

The red line is the actual temperature in the zone.

There’s another part to it as well, controlled by a set of bespoke routines for turning on and off the main valves for the hot water and the heating water circulation as well. Included in this is software for turning on and off the circulation pumps.

Our new smokealarm

Who should have thought that a smoke alarm could create so much hilarity

The new Nest


speaks to you in a almost perfect female voice saying things like :

“There is a lot of smoke in the kitchen, the alarm may sound, it’s very loud”

whereupon you can see whoever is in the kitchen when this happen leaping around waving their arms to turn the alarm off….

Domoticz and the Home easy HE305 switch

In the continuing discovery of the Domoticz software I bought a couple of Home Easy HE305 magnetic door switches


To try to get them working I first of all had to switch on the Home Easy EU in the Rfxcom control panel like this


and the use the “Learn” button on the switches tab. This recognised the switch as long as I was very close to the Rftrx transceiver.

But – it does not work reliably. It updates the log for every time I remove the magnet and again when the magnet is close enough, but it only sporadically updates the panels.


So I may have to raise a bug…


UPDATE : Found the problem – edit the switch to se the correct type like this :


This changes the display to :


Home Automation – I gave in a bought one of these

So in the end I bought one of these transceivers


It can communicate with a very long list of 433 Mhz devices – the full list is here .

And I plugged it into my Raspberry Pi running Domoticz


I can see my weather station sensors – so now I may get around the problem where my receiver (inside) stopped working when the temperature in the room goes below 15 degrees Celsius (!)

Air Quality Egg – Dust sensor

The Dust sensor arrived tonight for the Air Quality egg arrived today – and has now been installed, and the feed is working.


(Click for larger image)

The measurements seem a bit wrong though – possibly the Dust_r0 of -1 is somewhat wrong.

Btw. I followed the instructions here for the physical installation. I will post pictures later.

heimcontrol.js – Home automation in Node.js with Raspberry PI and Arduino

This may be of interest due to the combination of technologies and the fact that it is open source…

Awesome home automation with Raspberry PI and Arduino using Node.js, MongoDB, HTML5 and Websockets

[From heimcontrol.js – Home automation in Node.js with Raspberry PI and Arduino]