Home automation on BlocNotes

Fix Home-Assistant statistics and energy erroneous values

Tue, 30 Sep 2025 00:00:00 +0000

Introduction

I have been experimenting with solar panels, Home Assistant and my electricity meter lately. This French meter from the utility is called Linky. It provides a small power supply (130 mW) and a serial link hidden via amplitude modulation.
To avoid using batteries, I built a prototype that harvests this power, demodulates the serial link, and feeds the data into an nRF52 development kit. It works well enough that I never bothered turning this messy setup into a proper PCB.

However, every now and then—despite CRC checks—I get an erroneous reading that messes up the Home Assistant Energy panel. Here’s how to fix incorrect statistics in the Home Assistant database.

Preparation

Before editing the database, it is strongly recommended to stop Home Assistant to avoid concurrent access that could corrupt the database.

Connect to the system running Home Assistant
Install SQLite3 if needed. For example, on Debian-based systems: apt install sqlite3
Locate the home-assistant_v2.db database file in Home-Assistant data folder and create a backup

Open the database for editing

Open the database using SQLite and set a more readable output mode:

$ sqlite3 home-assistant_v2.db
# Then enter the commands
sqlite> .header on
sqlite> .mode column

Find the data id

Identify Home Assitant’s internal identifier, it is called metadata_id. Replace easf02 with Home-Assistant’s Entity ID you are looking for.
Using LIKE '%PARTIAL_ENTITY_STRING% allows for easier search by matching any string containing PARTIAL_ENTITY_STRING

sqlite> SELECT id, statistic_id FROM statistics_meta WHERE statistic_id LIKE '%easf01%';
id  statistic_id            
--  ------------------------
6   sensor.linky_easf01     
15  sensor.linky_easf01_cost

In this case id = 6 is the one we want to fix, and id = 15 is the associated cost.

Search for erroneous data

We let’s ask the database for any sudden jump in the data, e.g change greater than 10,000 Wh. Adjust metadata_id = 6 and the threshold (> 10000) as needed.

WITH ordered_stats AS (
  SELECT
    id,
    created_ts,
    sum,
    metadata_id,
    LAG(sum) OVER (PARTITION BY metadata_id ORDER BY created_ts) AS previous_sum,
    LAG(created_ts) OVER (PARTITION BY metadata_id ORDER BY created_ts) AS previous_created_ts
  FROM statistics
  WHERE metadata_id = 6
)
SELECT
  id,
  datetime(created_ts, 'unixepoch', 'localtime') as date,
  ABS(sum - previous_sum) AS difference
FROM ordered_stats
WHERE ABS(sum - previous_sum) > 10000 ORDER BY id DESC LIMIT 5;

In a nutshell, this query:

Selects statistics data for the entity and associates each value with the previous one.
Displays the five most recent entries where the difference between consecutive values exceeds the threshold.

Example result:

id      date                 difference
------  -------------------  ----------
229351  2025-08-18 14:00:10  20676793.0
38711   2025-01-28 12:00:10  20020401.0

Looks like we found the 20.6 MWh spike reported in the Energy panel :-)

Update the value

Since Home Assistant records cumulative sums, we need to subtract the erroneous difference from all entries starting from the anomaly. Use the following query:

UPDATE statistics SET sum = sum - 20676793.0 WHERE metadata_id = 6 and id >= 229351;

Replace 20676793.0 and 229351 with your actual values.

The statistics_short_term sum should also be adjusted by the same value:

UPDATE statistics_short_term SET sum = sum - 20676793.0 WHERE metadata_id = 6;

Once done, exit SQLite by pressing Ctrl + D. The database is now fixed, and the energy panel displays accurate values!

Fixed Home-Assistant energy panel

Automate shutters with an ESP and Home Assistant

Sun, 12 Jul 2020 18:50:41 +0000

I recently did a proof of concept on shutters automation by hacking the remote control: the idea is to wire the ESP in parallel with the remote control buttons.
My remotes are Bubendorff 41677 but it should work with a lot of other remote controls.

Wemos & the remote control

After poking with a multi-meter it appears that two test points are connected to the right signals:

TP103: Up
TP102: Down

The signal is active low: there is a pull-up resistor and it must be grounded to simulate the activation. A 680 Ohm resistor is used in series with each button of the remote to prevent current overshoot and maybe reduce power consumption, so I also used them:

Schematic

You might not see the resistors on the top picture as I only had SMD 0603 on hand; look carefully :)

On the first attempt, I used the great ESPHome project to simulate pressing the pushbuttons. I just created 3 virtual switches as a proof of concept but for correct integration, a cover component can be used.
I split the configuration into two files: one generic and the other only specifying the shutter name (room) and timings.

Per device file, called shutters-office.yaml in this example:

substitutions:
  # Used for HASS identifier
  name: office
  # Used for friendly name
  switch_name: "bureau"
  # Time from fully closed to fully opened
  full_time: "16s"
  # Time from fully closed to slightly opened
  partially_open_time: "5s"
  # Time for the "button pressed" event
  on_time: "150ms"

<<: !include shutters-common.yaml

Then the generic file called shutters-common.yaml:

esphome:
  name: shutters_${name}
  platform: ESP8266
  board: d1_mini

wifi:
  ssid: "MY SSID"
  password: "MY PASSWORD"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Shutter fallback hotspot"
    password: "12345678ABCDEF"

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

switch:
  # Define with GPIOs are used
  - platform: gpio
    id: up
    pin:
      number: 12
      inverted: yes
    restore_mode: ALWAYS_OFF
  - platform: gpio
    id: down
    pin:
      number: 14
      inverted: yes
    restore_mode: ALWAYS_OFF

  # Define template simulating the push on the button
  - platform: template
    name: Shutter ${switch_name} open
    turn_on_action:
      - switch.turn_on: up
      - delay: ${on_time}
      - switch.turn_off: up

  - platform: template
    name: Shutter ${switch_name} close
    turn_on_action:
      - switch.turn_on: down
      - delay: ${on_time}
      - switch.turn_off: down

  # Define template for slightly opening the shutter
  - platform: template
    name: Shutter ${switch_name} slightly open
    turn_on_action:
      - switch.turn_on: down
      - delay: ${on_time}
      - switch.turn_off: down
      - delay: ${full_time}
      - switch.turn_on: up
      - delay: ${on_time}
      - switch.turn_off: up
      - delay: ${partially_open_time}
      - switch.turn_on: up
      - delay: ${on_time}
      - switch.turn_off: up

As there is no feedback information on the shutter state the “slightly opened” state is achieved by fully closing the shutter then opening it for a small amount of time.
Once the ESP8266 or ESP32 is flashed the only thing remaining is to add it to Home-Assistant, thanks to Configuration => Integrations => Set up a new integration => Search for ESPHome => enter the ESP IP address. Et voilà, you are good to go and create powerful automations in Home-Assistant.

On the next version, I used a more clever strategy to command shutters from 0 to 100%, and a LoRaWAN board to allow battery-powered operation - to be published soon.

How to monitor pellet stove's tank

Tue, 26 Nov 2019 12:53:50 +0000

I have a great Rika pellet stove, but despite all the embedded electronics, it is unable to warn me just before the pellets tank is empty. As I already have my own low-power wireless devices and home automation tools, I just added a distance sensor and designed some enclosures.

Pellet stove

Sensor selection

IR sensor

Cheap usual Sharp sensor needs to be at least 10 cm away from the pellets. It is a no go for this use case as pellets are close to the lid when the tank is full

Ultrasonic sensors

As common as the Sharp IR sensor, the HC-SR04 was an option but I discarded it for two reasons:

Dust generated by pellets: sensor difficult to clean
Not working well with a power supply of 3.3 Vdc

STMicroelectronics time of flight sensor

So I went with ST VL53L0X: range adapted to my needs, low power, and it is easy to the clean sensor. Regarding dust, I used it for several months without having to clean it but summer was included, so let’s wait a full winter for feedback.

Hardware

I bought a cheap breakout board from eBay and plug the I2C lines into my NoteRF boards

Software

I just added the library from Pololu to my project then translated the data in Node-Red.

// VL53L0X
if ( sensorType == 7 ) {
    msg.topic = `data/sensor/noterf_distance_${sensorName}/state`;

	var distance = msg.payload.split( "|" )[2];
	distance_percent = 100 - distance/590*100;

	msg.payload = {
	    'rssi': rssi,
	    'battery': battery,
	};

	// Filter abnormal values
	if ( ( distance >= 0 ) && ( distance < 8000 ) ) {
	    msg.payload.distance = distance;
	    msg.payload.distance_percent = distance_percent;
	}
}

Home assistant

As for all other connected things in my house it reports to Home Assistant, which allows a nice interface, that I rarely use thanks to the automation: I am notified on my phone (through pushbullet) when tank level or device battery cross a threshold: the purpose of that device is achieved! Anyway, some fancy displays can be setup in a few seconds:

Tank status gauge - color changes according to the value

Tank status in millimeters - useless as percentage is more descriptive

Icons + values - I have view with it for all my devices

Device battery needs calibration :-)

Mechanics

I designed with OnShape two 3D printed boxes for the sensor and the electronics/battery, both are using magnets to stick in place The sensor is on the tank lid, while electronics and batteries are outside, hidden on the back of the stove.

Design files:

Time of flight sensor - Hot glued into 3D printed box

Enclosure for the electronics and the battery

NoteRF - Home automation

Sun, 28 Feb 2016 00:00:00 +0000

Here is the status of the project, right now it is not a real home automation as I only monitor things, but control will be added soon.

System architecture

All sensors emits to the gateway, which is just a sensor with the radio chip in reception mode. I use a Raspberry PI to collect and parse data from the gateway, then store it in the rPI and online. All data are displayed on Grafana for now and some are send to my phone by push messages.

NoteRF network architecture

Sensors PCB

I made custom PCB with ATmega328+HopeRF RFM69 radio transmitter, the Arduino bootloader is used in order to have easy access to thousands of libraries.

First batch had three minor errors which are hopefully corrected in the second batch. I should receive them soon, for reference there were:

ISP reset signal was on the wrong side of the DTR capacitor so a strap must be used when loading bootloader.
I forgot a capacitor in parallel of the tension divider to sense battery level, workaround is to stack it on the resistor. This capacitor is required because the divider has high resistor in order to decrease power consumption, so the capacitor helps to feed ATmega’s ADC capacitor
Some silkscreen text where on a layer not printed by the fab house.

Following batchs where corrected, see this page for schematics and layout.

NoteRF v0.1 sensors

Sensors

Currently I implemented those sensors:

Luminosity (Maxim MAX44009)
Temperature/Humidity (DHT11/DHT22 or HTU21D)
Pressure/Temperature (Bosh BMP180)
Temperature (Dallas DS18B20)
TIC: TéléInformation Client - French power meter’s output
Distance sensor (ST VL053L0) - Useful to monitor pellet’s stove tank
Soil moisture sensor
Currently testing the most essential : vibration sensor for mailbox !

Data parsing

I use Node-Red to receive serial data from the gateway on the rPi and parse it, check data integrity, gather data from web services (like air pollution), get the “end of print” data from my 3D printer… It is a great tool to quickly add new functionalities.

Node-RED

ioPush

I am currently writing ioPush, a logbook for error/warning/informations like Twitter but dedicated to the IoT (Internet of Things), with a phone application to receive push notifications. I was using Twitter but push notifications are not reliables and it does not fit my needs.

ioPush Android notification

Data storage

I use InfluxDB, a new noSQL database dedicated for time series data. Even if it still a bit buggy, it is now usable and the team reacts fast to issues. Data are stored in local on the rPi and send to a server on the internet in order to have a backup.

IHM

I did not find the ideal tool yet and do to want to write it for now, so I am using Grafana to display and graph data. I might move to something else later if I find, OpenHAB 2.0 is a good candidate but nothing is defined.

Grafana

Enclosure

I quickly designed a 3D printed box but I am not happy with it because it is way too big, so I might try another design. Algouth I might change the batteries because 18650 elements are free, but big.

NoteRF 3D printed enclosure

Power consumption

I power several sensors on upcycled 18650 batteries from old laptops since one year. So I optimised power consumption in design and code, but never measured it because sensors consumed only few percentage of the 2 400 mAh batteries.

Sources

Sensor and gateway code
PCB design files
Software
Installation notes (A friend of mine is currently writing an Ansible script to ease the process)
ioPush

All blog posts associated to NoteRF

ioPush-App

Wed, 27 Jan 2016 00:00:00 +0000

This web service is an IoT logbook and Android push notification server, it can be considered like Twitter but for the Internet of Things. It is a part of my home automation system: I previously used Twitter as a logbook of warning/errors but it lacks some functionalities, and for few months notifications did not work well on my phone.

Website screenshot

ioPush messages

Android notification

ioPush Android notification

So it should be able to

Keep record of events - Done
Send event to push message if asked - Done
Manage users - Done
Send push notifications to Android, maybe other OS - Done, Android app to be published
Android application -> receive notifications - Tested in the 1st version
Android application -> display user’s events

What can be logged?

Sensors out of battery warning
Pollution data over a threshold
Your 3D printer has finished its job
Server down
Motion sensor triggered
A new mail is inside your mailbox
Hoarfrost alert
Whatever you want to be written :)

Useful links

Dashing - Job to get data from InfluxDB v0.8 database

Tue, 14 Apr 2015 09:29:00 +0000

To use my dashboard, I wrote some Dashing jobs to be able to query some values from my InfluxDB database.

There are thre versions:

In Ruby
In node.js (javascript) after my switch to Dashing-js
A way to update a ‘list’ widget

The third code also changes the background color of a list widget, to set it regarding data values. I will share the widget’s code soon, I just need some time to clean a bit the code

1. Ruby code

# Insert required components
require 'json'
require 'net/http'

# Parameter
serverAddr = 'http://localhost:8086'

# :first_in sets how long it takes before the job is first run. In this case, it is run immediately
SCHEDULER.every '1m', :first_in => 0 do |job|

  # Url to get data
  url = URI( "#{serverAddr}/db/db_name/series?u=xxxx&p=xxxx&q=SELECT%20*%20FROM%20%22/data/Conservatory/Humidity%22%20LIMIT%201" )
  # Query server
  res = Net::HTTP.get( url )
  # Transforms JSON in object
  j = JSON.parse(res)
  send_event('welcome', { text: j[0]['points'][0][2] })
  send_event('synergy', { value: j[0]['points'][0][2] })

end

2. In node.js, easier to modify

// Includes
var request = require( 'request' )

// Configuration
var dbAddress = 'localhost'
var dbPort = '8086'
var dbName = 'XXXX'
var dbUser = 'XXXX'
var dbPwd = 'XXXX'
var refreshTime = 60*1000    // in ms

function getData( parameterToRefresh, widgetId, unit ) {
  // URL creation
  var urlToGet = 'http://'+dbAddress+':'+dbPort+'/db/'+dbName+'/series?u=' + dbUser+'&p='+dbPwd+'&q=SELECT%20*%20FROM%20%22/data/'+parameterToRefresh+'%22%20LIMIT%201'
  // Request
  request( urlToGet, function (error, response, body) {
    if (!error && response.statusCode == 200) {
      // No error, send the value to the dashboard
   	  send_event( widgetId, { value: Math.round(JSON.parse(body)[0]['points'][0][2]*100)/100 })
    }
  })
}

setInterval( function() { getData( 'Outside/Pressure', 'outsideText', ' mbara' ) }, refreshTime )

<pre>// Includes
var http = require( 'http' )
var async = require( 'async' )
var request = require( 'request' )

// Configuration
var dbAddress = 'localhost'
var dbPort = '8086'
var dbName = 'XXXX'
var dbUser = 'XXXX'
var dbPwd = 'XXXX'
// itemsToQuery [ dataNameInInflux, NameToDisplayInWidget ]
var itemsToQuery = [ [ 'Conservatory',  'PLA' ],
                     [ 'SensorTest_1',  'Citrus' ],
                     [ 'LivingRoom',    'Salon' ],
                     [ 'Office',        'Bureau' ]
                    ]
var refreshTime = 60*1000    // in ms

// Function to fetch data
function getDataList(url, callback) {
  var data = ""

  var req = http.request(url, function(res) {
    res.on('data', function(chunk) {
        data += chunk
    })
    res.on('end', function(e) {
        callback(e, data)
    })
  }).end()
}

function refreshDataList( parameterToRefresh, widgetId, unit ) {
  // Variables declaration
  var urls = []
  var itemarray = []
  var average = 0

  // Set url regarding unit
  switch( unit ) {
    case ' %': urlPrefix = 'data/'; urlSuffix = '/'+parameterToRefresh; break
    case '°C': urlPrefix = 'data/'; urlSuffix = '/'+parameterToRefresh; break
    default:   urlPrefix = parameterToRefresh+'/'; urlSuffix = ''; break
  }
  // Table construction regarding the items ot query
  for( var i = 0; i < itemsToQuery.length-1; i++ ) {
    urls.push( 'http://'+dbAddress+':'+dbPort+'/db/'+dbName+'/series?u='+dbUser+'&p='+dbPwd+'&q=SELECT%20*%20FROM%20%22/'+urlPrefix+ encodeURIComponent(itemsToQuery[i][0])+urlSuffix+'%22%20LIMIT%201')
  }

  // Asynchronous call to get the data
  async.map( urls, getDataList, function( err, result ) {
    // Parse results
    for( var i = 0; i < result.length; i++ ) {
      itemarray[i] = {label: itemsToQuery[i][1], value: (JSON.parse(result[i])[0]['points'][0][2] + unit)}
      average = average + JSON.parse(result[i])[0]['points'][0][2]
    }
    average = Math.round( average/result.length*100 )/100

    // Select color and 'moreinfo' message regarding data type and average value
    switch( unit ) {
      case ' %':
        backGroundColor = humidityColor( average )
        moreinfo = 'Moyenne : ' + average + unit; break
      case '°C':
        backGroundColor = insideTemperatureColor( average );
        moreinfo = 'Moyenne : ' + average + unit; break
      case ' V':
        mini = Math.min.apply(Math, result.map(function(table) { return JSON.parse(table)[0]['points'][0][2] }))
        backGroundColor = batteryLevelColor( mini )
        moreinfo = 'Minimum : ' + mini + unit; break
      case ' dB':
        mini = Math.min.apply(Math, result.map(function(table) { return JSON.parse(table)[0]['points'][0][2] }))
        backGroundColor = rssiColor( mini )
        moreinfo = 'Minimum : ' + mini + unit; break
      default:
        backGroundColor = '55555'
    }

    // Prepare structure to send
    var datastruct = {
      items: itemarray,
      backGroundColor: backGroundColor,
      moreinfo:  moreinfo
    }
    send_event( widgetId, datastruct )
  })
}

// Set job call every refreshTime
setInterval( function() { refreshDataList( 'Humidity', 'humidityList', ' %' ) }, refreshTime )

From Dashing.io to Dashing-js

Fri, 10 Apr 2015 09:15:00 +0000

I recently discovered Dashing.io, which is an easy to use dashboard, which seems to fit my needs :

Easy to install
Useful widgets available, easy to add new ones
Generation of templates for dashboards, jobs, widgets
Great design (subjective), some friends find it too close to Windows 8, but I don’t use it, so…
New data can be pushed via internal jobs or external API, by calling an URL
Tile based interface with drag&drop re-arranging (based on Gridster)
Auto-adaptation to smartphone/tablets (Responsive)

From my point of view, the major drawback is that it uses Ruby language. I have nothing about it, I just did not want to add another ‘technology’ to this project, which uses already lots of things. So I tried it, and then discovered Dashing-js: a Node.js port.

Dashing dashboard

The port is not as well documented as the Ruby version, so I will share my experience:

Run on a sub-directory (helpful for reverse proxy)

The easiest way to add it on /dashing is:

In file node_modules/dashing-js/lib/dashing.js
Add app.use('/dashing', app.router); (L75) inside app.configure(function() { } block
In file assets/javascripts/application.coffee
Add Batman.config.viewPrefix = 'dashing/views' after #= require_tree ../../widgets,

Stop a dashboard launch as daemon

If you start your dashboard in background with dashing-js start, dashing-js stop will not work, you must use kill PID command. I hope to have some time to explore the code and correct the bug/implement it soon.

Set default dashboard

Edit the file server.js, then line dashing.default_dashboard = 'subPathIfNeeded/sample';.

Save the current tile layout

Drag the tiles
Click on the ‘Save this layout’ button
Copy the code
Paste it in dashboard/yourDashboard.jade respecting the following example indentation, and the . (dot) after script(type="text/javascript"). Done !

extends layout

block title
  | Dashboard's title

block content
  div.gridster
    ul
      li(data-row='1', data-col='1', data-sizex='4', data-sizey='2')
        div(data-id='welcome', data-view='Text', data-title='Hello', data-text='This is your shiny new dashboard.', data-moreinfo='Protip: You can drag the widgets around!')
    center
      div(style='font-size: 12px') Try this: curl -d '{ "auth_token": "YOUR_AUTH_TOKEN", "text": "Hey, Look what I can do!" }' -H "Content-Type: application/json" http://#{request.header('host')}/widgets/we$


  script(type="text/javascript").
    $(function() { Dashing.gridsterLayout('[{"col":1,"row":1,"size_x":4,"size_y":2} [...] }]') })

Node-RED - Grab pollution data from local services

Thu, 29 Jan 2015 14:13:00 +0000

I am currently evaluating some solutions to build my home automation system. As a part of this system I want to monitor air quality, but, I do not have any sensor yet, so I use a public service and parse its data with Node-RED.

I built the following flow which gets the data from Air Rhone-Alpes, a local service. After grabbing the web page, it extracts the pollution level, parses it, publishes it to my MQTT broker. I added a filter to avoid any update if there is no change in the pollution level value. Another flow subscribed to the MQTT topic and send ioPush-App notifications depending on the pollution level.

Node-RED screenshot

The flow may be useful to somebody else to understand how to parse an HTML page, but mainly people from the Rhône-Alpes area, France will use it :)

So copy the following flow, and insert it in your Node-RED page (Import->Clipboard->Paste). It can be tested by clicking on the Start flow button.

[
  {
    "id": "b82a5ab2.47d5a8",
    "type": "mqtt-broker",
    "broker": "localhost",
    "port": "1883",
    "clientid": "Node-RED"
  },
  {
    "id": "9f2c1b12.60d3e8",
    "type": "inject",
    "z": "d99ce1.ff26632",
    "name": "Start flow",
    "topic": "",
    "payload": "",
    "payloadType": "date",
    "repeat": "3600",
    "crontab": "",
    "once": true,
    "x": 138.99993896484375,
    "y": 102.55555311838782,
    "wires": [["e9f3befe.160c4"]]
  },
  {
    "id": "e9f3befe.160c4",
    "type": "http request",
    "z": "d99ce1.ff26632",
    "name": "",
    "method": "GET",
    "ret": "txt",
    "url": "http://www.air-rhonealpes.fr/indice/atmo",
    "x": 218.99993896484375,
    "y": 159.55555311838782,
    "wires": [["30106e06.cfef92"]]
  },
  {
    "id": "30106e06.cfef92",
    "type": "switch",
    "z": "d99ce1.ff26632",
    "name": "Check HTTP status",
    "property": "statusCode",
    "rules": [
      { "t": "eq", "v": 200, "v2": 0 },
      { "t": "neq", "v": 200, "v2": 0 }
    ],
    "checkall": "true",
    "outputs": 2,
    "x": 319.49993896484375,
    "y": 208.8888966242472,
    "wires": [["473dec33.b8c214"], ["4c47b272.b3b84c"]]
  },
  {
    "id": "473dec33.b8c214",
    "type": "function",
    "z": "d99ce1.ff26632",
    "name": "Extract data",
    "func": "var msg = { payload:msg.payload.split(\"<tr class=\\\"odd\\\">\")[3].split(\"span\")[3].substr(24, 1) };\n\nreturn msg;",
    "outputs": "1",
    "noerr": 0,
    "x": 526.4999771118164,
    "y": 176.66666507720947,
    "wires": [["4dfde937.b20218"]]
  },
  {
    "id": "576fcefb.a8903",
    "type": "mqtt out",
    "z": "d99ce1.ff26632",
    "name": "",
    "topic": "/raw/Outside/AirQuality",
    "qos": "0",
    "retain": "false",
    "broker": "b82a5ab2.47d5a8",
    "x": 975.4999771118164,
    "y": 176.66666507720947,
    "wires": []
  },
  {
    "id": "4c47b272.b3b84c",
    "type": "function",
    "z": "d99ce1.ff26632",
    "name": "Add error message",
    "func": "msg.payload = \"Erreur - Impossible de récupérer la polution de Grenoble @\" + msg.url\nreturn msg;",
    "outputs": 1,
    "noerr": 0,
    "x": 549.4999771118164,
    "y": 236.66666507720947,
    "wires": [["76bea7bc.894158"]]
  },
  {
    "id": "1319a2fc.ece65d",
    "type": "comment",
    "z": "d99ce1.ff26632",
    "name": "Get the data from http://www.air-rhonealpes.fr",
    "info": "1. Every hour, get the RSS feed from \"Air rhone alpes\"\n2. Parse it to find last report URL\n3. Get the report and extract the data",
    "x": 190.5,
    "y": 40,
    "wires": []
  },
  {
    "id": "4dfde937.b20218",
    "type": "rbe",
    "z": "d99ce1.ff26632",
    "name": "Block unless value change",
    "func": "rbe",
    "gap": "",
    "x": 731.5,
    "y": 180,
    "wires": [["576fcefb.a8903"]]
  }
]

Install eMonCMS on OVH shared hosting

Fri, 16 Jan 2015 12:48:00 +0000

First, post :)

I am currently testing Emoncms as a part of my home automation system, it is a tool to store house’s data and which should allow us to analyze it from an “energetically point of view”. It is a part of the OpenEnergyMonitor project.

Emoncms’s servers seem to be quite overloaded so I decided to host it myself. It should have been easy as good documentation is provided, but, it was not!

First, follow the instructions on the website. Then change the root’s “.htaccess” file to add the following lines

# Set PHP version, otherwise OVH use version 4.3
SetEnv PHP_VER 5_4
# Disable magic quotes
SetEnv MAGIC_QUOTES 0

Then try to create an account. If it does not work, but you have just a red box displayed, it could be good to have a look at your MySQL database: on my installation, the script did not create the tables. So I commented the if condition in the file index.php:

(L57 and L59 in the current version)
// if (!db_check($mysqli,$database)) {
db_schema_setup($mysqli,load_db_schema(),true);
// }

Finally reload the page, check if the tables are created and uncomment.

Now, it should work! If you are wondering what address you must use for the data folder, it is “/home/yourID/yourEmoncmsData” if you put the data folder at the same level as “www” to hide it from the internet. No need to change permissions.

Thanks to Olivier for the ‘magic quotes tip’.

I used Emoncms V8.4.0