For a number of years now I have been working with John Cantor on monitoring heat pumps. John is one of the UK's foremost experts on heat pumps having worked in the field since the early 1980's, he has written a book on heat pumps and is an advisor and consultant on the technology.
Earlier this year we worked on reading heat metering data from a Kamstrup heat meter in order to obtain accurate heat output measurement in addition to system flow temperatures and electrical power input. After spending quite a bit of time adapting existing emontx hardware and often emontx v2 hardware to integrate the additional circuitry required we decided it might be better to try and design a dedicated heat pump monitoring board that would have all the functionality we needed on a single board.
This board is currently going through initial testing. Read on →
Using the emonPi in it's current default configuration works great to post data to Emoncms for logging and visualisation. However there may be times when you want some more flexibility and or ability to interface with other hardware or services
In my last few blog posts I have been taking a look at making the emonPi the heart of a smart energy optimised home and how live energy monitoring data from the emonPi can easily be used to inform other services:
Yesterday evening Trystan and I attend a local meetup in Bangor, North Wales hosted by NorthWalesTech It was a good event with some interesting talks. Here are the slides from the 5min lightning talks we gave:
My slides give a brief overview of the OpenEnergyMontor project before diving in to MQTT and node-RED with a live demo controlling LightWave RF plugs switching Christmas lights over the web using MQTT and nodeRED:
Trystan's lightning talk was focused on a heatpump which he has recently installed with John Cantor to heat his home. Trystan gave an overview of heatpump technology, his monitoring setup and the preliminary performance results:
Using a Raspberry Pi as an emonPi / emonBase web-connected base station for energy monitoring has many advantages (maintainability, remote access, debugging, updated etc.) but it does seem rather wasteful to have a 900Mhz 1GB RAM machine being used to post a couple of integers to a web-server! The always-on nature of a web-connected base station and plenty of spare processing power makes it ideal to use the emonPi for more than just energy monitoring; home automation and heating control optimisation are obvious candidates.
Hardware Many home automation products such as RF plugs, relays and heating remotes use a simple OOK (On-Off-Keying) wireless protocol. UK company LightWaveRF produce a variety of RF plugs and relays which can be controlled via OOK RF. The protocol is also compatible with some cheaper OOK learning receiver relays. While maybe not strictly open-source the protocol and been reverse engineered allowing plugs to be easily controlled from Arduino / Raspberry Pi. There is an active LightWaveRF online community. Using off-the shelf hardware like this is a 'safe' way to control lights, heaters and appliances around a home without getting our hands dirty dealing with with high voltages. These plugs and relays can be used to control anything from lights to immersion heaters, most LightWaveRF plugs/relays will switch up to 13A / 3kW.
Note: OOK protocol by it's simplistic nature is not particularly secure, I would not recommend controlling anything you don't mind getting accidently switched.
Existing LightWaveRF remotes can be emulated allowing plugs to be controlled from either emonPi MQTT or via the remote.
Now our plugs can be controlled via MQTT there are a many of options open as to how to control either via interface openHAB (blog post coming soon..), nodeRED, android Tasker etc.
I have been using nodeRED with input from android OwnTracks running on my phone to detect when I'm home and turn on a couple of lights:
Using NodeRED and OwnTracks to turn on LightWave RF sockets when I arrive home:
Using android Tasker with AutoVoice and MQTT plugins to control LightWaveRF sockets:
Now we can control appliances remotely via MQTT the next logical step is to add a mobile user interface. In my next blog post I plan to explore setting up openHab to control appliances. Here's a early preview:
We plan to include out-of-the-box support for OOK LightWave RF, nodeRED and openHab pre-configured on our next emonPi pre-built SD card. Due for release in December 2015.
I have recently been experimented using Node-RED for a number of tasks. Thanks to the work of others a Node-RED flow node already existed for Emoncms making it very easy to post data to Emoncms. For my Ambient Wind Energy Indicator I had the need to extract real-time feed data from Emoncms feeds using the Emoncms API. I have now contributed this functionality to the official Node-RED Emoncms node. Using the updated Emoncms node it's now super easy to post data to extract latest real-time feed values from any Emoncms server including Emoncms.org.
The emonPi / emonTx standard install is designed to monitor whole house power consumption. An excellent learning exercise that we recommend everyone undertake soon after installing a whole house energy monitor is to turn off every appliance in the house then slowly turn on each appliance keeping a close eye on the real-time Emoncms dashboard. Walking around the house using a handheld mobile device to display the Emoncms dashboard works great for this. For fastest response we recommend connecting to the local Emoncms running locally on the emonBase / emonPi which will update ever 5s (emonPi default) or 10s (emonTx default).
After this exercise you should have a good idea what the trace signature of each of your appliances looks like on the graph. The easiest to identify are the large power consumers e.g kettle 3kW spike and shower 8kW spike. However with a bit of observation it's possible to identify subtler power signatures. Here's an excellent example by posted by @Zapaman showing a Solar PV dashboard annotated to identify his fridge / freezer and central heating pump running over night. It's great to see the solar PV kick in providing more then the demand when the sun hits the panels in the morning :-)
As we move to a low carbon electric grid with large amount of input from renewable sources we will need to match our consumption of energy to generation. The wind will not always blow and the sun doesn't always shine. Grid energy storage will play a role, however the closer we can match our consumption of energy to generation the less storage will be required. In the future we can expect dynamic pricing to act as as an incentive for shifting consumption patterns.
As an experiment I have been playing around with creating a real-time ambient indicator of UK wind energy generation. Since wind energy is the greatest input of renewable energy into the UK grid we can assume that when wind generation output is high this is the best time for us to use power e.g. run the washing machine, dish washer etc..
First let's install the software to control the Blink(1) USB on the emonPi / RaspberryPi:
$ git clone https://github.com/todbot/blink1 $ sudo cp ~/blink1/linux/51-blink1.rules /etc/udev/rules.d/ $ sudo udevadm control --reload-rules un-plug then re-plug device $ cd blink1/commandline $ make
Note: if Node HID fails to compile you may need to install gcc-4.8. I did not experience this problem using Raspbian Wheezy: https://github.com/node-hid/node-hid/issues/115 Test it's operation by turning on a white LED with $ ~/blink1/commandline./blink1-tools --on To make the Blink(1) USB work with Node-RED we need to install the Blink(1) node-RED flow and libusb driver. If you haven't already got it installed this example also requires the emoncms noe-RED flow to pull data from emoncms.org
Node-RED makes it super easy to link the required software components together, with pre built nodes available for emoncms and Blink USB it's just a case of linking the nodes together and adding some logic. Here is now node-RED flow, see node-RED export at bottom of this post:
We have a script running on emoncms.org to pull in real-time UK wind energy generation. We have been logging this data for almost a year now. Checkout the dashboard here: http://emoncms.org/mywindpower/ukwind.
The read API key for this account is 8f5c2d146c0c338845d2201b8fe1b0e1 and the feed ID is 67088. To pull the real time data into node red just plug in the api key and feed ID into the node-RED emoncms in node. Node-RED will then execute the following GET request: