Emoncms is an open-source web application for processing, logging and visualising energy, temperature and other environmental data and is part of the OpenEnergyMonitor project.
- PHP (tested with 8.1.12)
- MySQL or MariaDB (tested with 10.5.15)
- Apache (tested with 2.4.54)
- Redis* (tested with 6.0.16)
*Redis is recommended because it reduces the number of disk writes and therefore prolongs disk life (noticeably on SD cards e.g. Raspberry Pi). Some input-processors also require Redis and fail silently if Redis is not installed. Some environments such as shared hosting or as far as we have tried Windows servers don't support Redis hence why Emoncms has a fall back mode that allows core operation without Redis.
View the Emoncms documentation at: https://docs.openenergymonitor.org/emoncms
- Getting started emonPi/Base
- Getting started emoncms.org
- Emoncms Core Concepts
- Posting data
- MQTT
- View Graphs
- Dashboard Builder
- Application dashboards
- Octopus Agile app
- Calculating Daily kWh
- Calculating Averages
- Pulse counting
- Exporting CSV
- Histograms
- Post Process module
- DemandShaper module
- Import / Backup
- Update & Upgrade
- Remote Access
- Troubleshooting
Design
- Emoncms architecture
- Input processing implementation
- Developing a new Module
- Global variables in Emoncms
Emoncms timeseries database design (feed storage)
- Emoncms time series database development history
- Fixed interval time series
- Variable interval time series
- Improving write performance with buffering
Other
Emoncms Terminology
- Input: An incoming datasource. Each input has an associated "node" identifier and a "key" sub-identifier. Inputs are entry points, only the last value and time of the input is recorded. To record historic data a feed needs to be created from an input.
- Input: Node: A grouping identifier for an input or feed.
- Input: Key: A sub-identifier for items within each Node.
- Input process list (or input processing): A list of processes* performed sequentially on each input value as it is received on that input.
- Process: A function that can be attached to the process list of an input to change the value or to save the value to a feed*.
- Feed: A place where data is recorded, a time-series of datapoints. The standard time-series databases used by Emoncms are PHPFina and PHPTimeSeries and were written as part of the Emoncms project.
- For a description of what each input process does in Emoncms, see the helper note within the Emoncms input processing configuration interface.
Emoncms.org API Reference
Emoncms is designed and tested to run on either Ubuntu Linux (Local, Dedicated machine or VPS) or RaspberryPi OS. It should work on other Debian Linux systems though we dont test or provide documentation for installation on these.
We do not recommend and are unable to support installation on shared hosting or XAMPP servers, shared hosting in particular has no or limited capabilities for running some of the scripts used by emoncms. There is now a large choice of low cost miniature Linux VPS hosting solutions that provide a much better installation environment at similar cost.
Recommended:
An easy way to start with emoncms is to use the all-in-one docker container
A pipeline using github actions is producing builds with latest emoncms stable version for different architectures : amd64, arm64, arm/v7
These docker images, based on the alpine linux distribution, are designed for iot. Images are tagged using alpine and emoncms versions, for example alpine3.19_emoncms11.4.11.
The images have onboard :
- the mariadb and redis databases,
- the mosquitto mqtt broker,
- the main modules : graph, sync, backup, dashboard and app,
- the workers : emoncms_mqtt, service-runner and feedwriter.
You can easily :
- deactivate the low-write
- use an external broker.
To pull the latest image for testing :
sudo docker pull alexjunk/emoncms
More on https://emoncms-docker.github.io
not currently up to date
Multi-platform using Docker Container
Modules can be installed by downloading or git cloning into the emoncms/Modules folder. Be sure to check for database updates in Administration menu after installing new modules. The following core modules are included on the emonSD image:
-
Graph module - Advanced graphing module that integrates with the emoncms feed list, highly recommended; examples of use can be found in emoncms guide [1][2][3][4].
-
Device module - Automatically configure inputs and feeds using device templates.
-
Dashboards module - Required for creating, viewing and publishing dashboards.
-
App module - Application specific dashboards e.g. MyElectric, MySolar.
-
Config - In-browser emonhub.conf editor and emonhub.log log viewer. Use
git cloneto install. -
Wifi module - Wifi configuration interface designed for use on the emonPi
-
Raspberry Pi Backup / Restore module (emonPi / emonBase)
-
Usefulscripts: Not strictly a module, more a collection of useful scripts for use with emoncms.
-
DemandShaper module - Schedule smartplugs, EmonEVSE smart EV chargers, heatpumps to run at best time in terms of: carbon, cost, grid strain. Based on day ahead forecasts.
There are many other available modules such as the event module and openbem (open source building energy modelling module): check out the Emoncms repo list.
-
master - The latest and greatest developments. Potential bugs, use at your own risk! All pull-requests should be made to the master branch.
-
stable - emonPi/emonBase release branch, regularly merged from master. Slightly more tried and tested. See release change log.
- PHPFina data file viewer - Easily explore phpfina timeseries feed engine data files directly without a full Emoncms installation. Useful for checking backups and archived data.
- Cloud hosted platform - http://emoncms.org
- OpenEnergyMonitor Forums
- OpenEnergyMonitor Homepage
