Interesting :

Heterocera is an implementation of an associative memory system. It is inspired by the concept of a tuple space and by the work of David Gelernter (outlined in his book Mirror Worlds).

Heterocera is designed to enable easy communication in heterogeneous environments (e.g. Arduino applications and web applications). This is done by treating the memory space as a web server - where address locations are URLs. Heterocera will handle single values, rich JSON structures and files.

By reducing all interactions to HTTP GET and POST requests even simple platforms can record and retrieve data.

This is not meant to be a NoSQL system. It is designed to:

One more type of displays

I've tried to do some further analysis of the problems I have with the FHT80B wireless thermostats - and the interference from the Jeenodes in the house.

As I have mentioned before I store all read ins from all the house sensors in a memcached instance on one of the servers - and for the FTH80B's it looks like this (after I throttled the Jeenodes sending frequency)

It basically shows that the last time I heard from the FHT80's was 55 seconds ago for the conservatory thermostat, and 99 seconds from the living room one.

It is also clear from this that the actuator values are send frequently - the rest only less often.

I have a problem with the house monitoring system - it looks like I'm a victim of interference

If you look at the graphs for our FHT80B radio thermostats you will notice something missing :

There is not red line (temperature readings) for the top graph (Concervatory) at all - and only a short line for the second graph (living room).

A bit of experimentation shows me that this is due to the Jeenode transmissions that update the Jeenode displays! If I turn these off (or even lower the update frequency) then the temperature readings start appearing again.

The high level software in the house monitoring system works on a simple principle

(Click for a larger pic)

All the data collected from the various sensors is sent to a memcached instance running on one (or more) of the servers, and stored together with a timestamp.

A small library makes it easily accessible for all the other software in the system.

In a simple display it looks like this :