Please see OpenEnergyMonitor Development Plan Outline for the latest development plan (November 2018).
Posted February 2018:
Its been a while since we published a list of our development goals and an overview of what we are working on. I’m aware its a question that a number of people have asked and so we wanted to give a bit more transparency. We have already discussed the following with forum moderators and a number of other core contributors and have made a number of amendments, thankyou to all who have given input so far.
If you would like to give feedback on the following feel free to reply below or send us a PM.
OpenEnergyMonitor goals 2018/2019
OpenEVSE integration: Growing out of our interest in electric vehicles we have developed an integration of the OpenEVSE open-source electric vehicle charging station with our solar pv monitoring system (working with Chris Howell lead developer of the OpenEvse project and Jeremy Poulter), making it possible to divert excess solar to charge an electric vehicle. We are working on a 7kW/22kW single/3-phase compatible type-2 (non-tethered) charger suitable for home & public charging stations with full certification. We have also become an OpenEVSE distributor for UK/EU. It is our intention to improve the emoncms support for the OpenEVSE including a apps module app that records energy use per charge, rather than kwh/d.
IotaWatt: Continue to work with Bob Lemaire to support IotaWatt as part of the OpenEnergyMonitor system: providing WiFi Connected 14 Channel Electricity Monitoring. Add IotaWatt to guide:system overview, update product pages on the shop to reflect CT operating range findings. Ensure historic upload of data to emoncms.org works ok.
EnergyLocal: Develop further ESP8266 based SonOff S20 smartplug and WIFI relay control: for use in demand side response whether solar diversion, time of use tariffs or renewable energy availability on the grid, this is a development that is coming out of our collaboration with EnergyLocal. The project so far has resulted in significant improvements to our ESP8266 firmware called EmonESP, the emoncms device module device-integration developments, wifi access point setup of the emonpi/emonbase, a new emoncms module called demandshaper which can be used to schedule appliances based on a day ahead power availability forecast and a focus on emonbase/emonpi bug testing especially for the phpmqtt_input process. The next steps include completing the release of the EmonESP software development, documenting how to use it, merging the device-integration work in the device module and documenting the use of the device module in conjunction with these control devices and the demandshaper for scheduling. We will be advertising soon for a development position to help us with this project, if your interested please get in touch.
- Github: CydYnni developments
- Github: EmonESP control node
- Forum post: device-integration
- Github: demandshaper
- Forum post: CydYnni, EnergyLocal Community hydro smart grid
Integrate heatpump monitor into the EmonTx V3: with a separate MBUS reader board and further work on the ESP8266 option for the EmonTx. Allowing lower cost installation where an emonbase or emonpi is not needed. Consider as part of any EmonTx v3 changes that may result from this wider suggestions from the community.
Emoncms billing and scale: emoncms.org has grown significantly over the past few years. Significant investment in server storage, processing and development time will be required in the coming years to continue scaling to meet demand. In the last 12 months the number of active users has grown from 2,400 to 3,500 and the number of active feeds from 28,000 to 38,000. We would like to add further storage servers, optimise the front end and input processing load to enable further scaling. We project emoncms.org costs to rise to £6k for servers and ~£32k for development and administration this year (including the addition of one dedicated full time emoncms.org developer). Our present proposal is to implement a pay-per-feed model with costs in the region of £1-2 per feed per year. For customers of OpenEnergyMonitor hardware, emoncms.org accounts will be automatically credited with credit based on a percentage of total order spend, e.g a full EmonPi costing £153 may result in £31 (20%) of emoncms.org credit providing 3-5 years of free use for 6 feeds. Exact feed cost have not yet been finalised, these figures above are likely to change over the coming months as we assess the impact of different costs. We realise that this is a significant change and that some expectation of service is assumed when buying a hardware product, we are also glad that for those where a payment model will not work, emoncms is open source software that can be self hosted, which is also something we encourage. All emonPi’s will continue to be shipped with Emoncms pre-installed of course, enabling easy local logging if required. Emoncms credit will be applied retrospectively for past OpenEnergyMonitor shop order spend.
emonHub: Work with Paul Burnell to bring emonhub development efforts together. Fix a number of issues in the emonpi variant in particular the emoncms interfacer buffering. Extend the documentation to give example use cases for all the different interfacers e.g recent socket interfacer discussion. Implement option to pass MQTT data from ESP devices through EmonHub and then on to a local emoncms installation so that emonhub can relay the data simultaneously to a remote server such as emoncms.org.
EmonLibCM: Work with Robert Wall to bring continuous monitoring support to the EmonTx, currently in testing.
Groups: Work with Carlos Alonso Gabizón of CarbonCoop on the integration of his groups module developments on to emoncms.org enabling multi-user administration, notifications and alarms.
LoRAWAN: Develop LoRaWAN RF support for our hardware units to enable easy wide area deployment using open The Things Network.
Thankyou for reading, we wish everyone well for the year ahead!
Trystan & Glyn