Emoncms stable release v11.7.4

Emoncms
1

While there have been fairly regular stable branch updates to emoncms core and associated modules over recent months, it has been a while since we created a set of releases with release notes. The following amends that.

If you have updated emoncms recently it’s very likely that you will have many of these updates already as the emoncms update process will pull in interim release tags as well.

If you haven’t updated for a while, some highlights in the last year include:

The latest releases are now:

Emoncms Core: Release 11.7.4 · emoncms/emoncms · GitHub

Modules:

Emoncms component versions snapshot:

image
image974×1695 198 KB

4 Likes
2

Did you mean this: 3.4.1 ? Methinks not.

2 Likes
3

containerized version also updated

docker hub

2 Likes
4

Thanks for all of your help @alexandrecuer

1 Like
5

Fixed thanks @Robert.Wall

1 Like
6

4 posts were split to a new topic: Problems upgrading to 11.7.3

8

Does anyone have any experience with auto generating github release notes? E.g every time a new git tag is generated, perhaps a release with a list of the commits could be generated? Cherry on the cake would be an AI analysis of both the commit descriptions and the file changes to provide an even more comprehensive change log summary!

Copilot suggested modifying the script I currently use for this like so, but are there any other better approaches: EmonScripts/other/stable_release.sh at master · openenergymonitor/EmonScripts · GitHub

# Get commit messages since last tag, excluding "update version"
last_tag=$(git -C $M describe --tags --abbrev=0 HEAD^ 2>/dev/null)
if [ -z "$last_tag" ]; then
    commit_range=""
else
    commit_range="$last_tag..HEAD"
fi

release_notes=$(git -C $M log $commit_range --pretty=format:"* %s" | grep -vi "update version")

# Create GitHub release with notes
gh release create "$version" --title "$version" --notes "$release_notes" --target stable
1 Like
9

This actually worked a treat!

See new EmonScripts release, automatically generated

and with commit diff:

1 Like
10

I’ve made the switch to the use of the rpi-lgpio library, preparing for the new emonSD image build.

Running update on existing systems will now install this library and associated modification to boot/config.txt SPI chip select. This requires a REBOOT for the RFM69 radio to continue working and so I’ve added a message that now appears at the end of the update process when this or other similar actions where reboots are required occur:

image
image1170×316 23.2 KB

1 Like
11

Further changes to the emonHub install script. It now only installs rpi-lgpio if rpi-lgpio is actually available. I had an older system error out on that and then fail as it had also removed the original rpi-gpio. It will now only install lgpio if it’s available in the package list for that distribution.

2 Likes
12

Thanks. Have just upgraded.

I need to remind myself how to configure an export from Home Assistant for the new dhwT and dhwTargetT inputs/feeds. Although, as we have a myenergi eddi (solar diverter) is that going to potentially confuse the My Heatpump app, where it sees the DHW temp rising while the dhw boolean is false?