Emoncms v11.2.3 stable release

Emoncms
1

I’ve merged the emoncms master branch into stable alongside associated modules.

Emoncms Core v11.2.3
List of commits since last stable merge:
https://github.com/emoncms/emoncms/compare/11.0.9…11.2.3

  • Option to compress data sent using AES128CBC encryption option.
  • PHP 8.1 support, thanks to @thib66
  • Error checking on EmonLogger log file, thanks to @borpin
  • Support for public emoncms apps
  • Fix for an issue embedding dashboards
  • Option to return feed data without timestamps (useful for fixed interval data, reduces bandwidth use)
  • Improved user delete implementation
  • Documentation moved from learn

Emoncms App module v2.6.7
List of commits since last stable merge:
https://github.com/emoncms/app/compare/2.5.2…2.6.7

  • Fix west midland export id
  • My heat pump app internal temperature feed option
  • Support for sharing apps publicly
  • Only use apikey’s if specified
  • SolarPVbattery app option for DC side battery
  • New average daily profile app
  • Option to enter Octopus GO tariff details in Octopus Agile app
  • New solar pv and battery simulator app
  • My heat pump calculates COP without standby in detail section
  • Improve My heat pump app carnot COP calculation behaviour during defrosts
  • My Electric cost scaling fix

Emoncms Dashboard module v2.3.3
Commits since last stable merge:
https://github.com/emoncms/dashboard/compare/2.2.4…2.3.3

  • Fixed issue with kwhperiod when apikeys are used
  • Menu related fixes

Emoncms Graph module v2.2.3
Commits since last stable merge:
https://github.com/emoncms/graph/compare/2.1.6…2.2.3

  • Show graph menu if user has read level access
  • Improvements to public data view

Emoncms Sync module v2.1.4
Commits since last stable merge:
https://github.com/emoncms/sync/compare/2.1.1…2.1.4

  • Script for uploading feed data on a cron call

Emoncms Postprocess module v2.2.5

Commits since last stable merge:
https://github.com/emoncms/postprocess/compare/2.2.4…2.2.5

  • New carnot COP calculator, replicates functionality in the my heat pump app but allowing full calculation of all data.

EmonHub v2.4.1
See change log since last release: Comparing 2.3.4...2.4.1 · openenergymonitor/emonhub · GitHub

  • Support for gzip compression in EmonHubEmoncmsHTTPInterfacer thanks to @SeanDS
  • New interfacer to fetch from JLR API, thanks to @dconlon
  • Option to send input names in EmonHubEmoncmsHTTPInterfacer (automatically uses gzip compression)
  • Use a requests.Session to reuse HTTP connections, thanks to @bwduncan
  • Direct raspberrypi rfm69 spi interfacer
  • New option to read in data from a redis queue using redis interfacer
  • Documentation updates
2 Likes
2

You’ve been busy :laughing:

1 Like
3

Notable EmonHub changes:

Sending input names
It’s now possible to send input names using the EmonHubEmoncmsHTTPInterfacer! This allows for transferring input names to emoncms.org, making setup a lot easier. Here’s an example of a suitable emonhub.conf entry. Note sendnames = 1 this turns on this functionality.

    [[emoncmsorg]]
        Type = EmonHubEmoncmsHTTPInterfacer
        [[[init_settings]]]
        [[[runtimesettings]]]
            pubchannels = ToRFM12,
            subchannels = ToEmonCMS,
            url = https://emoncms.org
            apikey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
            senddata = 1
            sendnames = 1

Note: When sendnames is enabled the data is automatically compressed using gzip compression (thanks @SeanDS). This results in very little additional bandwidth use. Bandwidth is actually dwarfed by making the HTTPS connection - something I want to improve on.

OEM Interfacer
Although not a new feature in this release, it’s been quietly there in the background for a while. I wanted to recommend using this interfacer in place of the serialtx3e interfacer. The OEM interfacer is also designed to replace the EmonHubJeeInterfacer it supports 3 different data formats:

  • Decimal space seperate representation of RFM binary data e.g OK 5 0 0 0 0 (-0)
  • KEY:VALUE format e.g power1:100,power2:200
  • JSON format e.g {“power1”:100,“power2”:200}

Here’s an emonhub.conf example configuration:

    [[OEM]]
        Type = EmonHubOEMInterfacer
        [[[init_settings]]]
            com_port = /dev/ttyAMA0
            com_baud = 115200
        [[[runtimesettings]]]
            pubchannels = ToEmonCMS,

We will be updating the default emonhub.conf files included with emonSD to use this in the next emonSD release. Here’s the brief emonhub conf example page for this interfacer: emonhub/conf/interfacer_examples/OEM at master · openenergymonitor/emonhub · GitHub.

New interfacer for reading data directly from an RFM69cw module connected via SPI
We haven’t released hardware that can use this yet but it’s the direction we are heading in for reading data form RFM69cw modules rather than having another microcontroller as an intermediary. More to come on this soon.

1 Like
4

Thanks, hopefully the commit tags and git describe results are all lined up correctly now!

1 Like
5

Just to take care the new file doesn’t overwrite existing systems. :slight_smile:

6

Yes that’s what I was wondering about and is why I haven’t updated the example files yet until I have made sure we are safe.

7

If you add conf/emonhub.conf to the .gitignore then a pull will not overwrite the local version (and also ignores local changes so preventing emonhub from updating).

For standard systems you need a separate mechanism to make it the config to use.

Perhaps a selector from the emonhub page?

Another strategy would be to do a compare in the update script to see if the conf file has been modified, if not replace it with a copy of the new template. I have a feeling the install script copies the emonhub template file currently anyway.

Perhaps split this into a new thread?

1 Like
8

Thanks @borpin I will pick up the emonhub conf topic up again a bit later. Just wanted to get the stable release done for now. Will do some testing to work out what breaks.

1 Like