OpenEnergyMonitor Community

emonSD-24Jul20 release

I use Balena Etcher now, works a treat! Maybe it would be better to point to the OEM image page which recommends Etcher rather than the raspberrypi documentation there come to think of it


@TrystanLea, it looks like you unpinned this. Did you mean to?

It is good to keep it pinned so easily found. The alternatives is an ‘Announcement’ Category into which you post announcements (funnily enough) but lock the posts so questions get added to new threads. If possible link to the menu at the top (other than in categories) so easily found (when responding to a question answered by the announcement).

Thanks @TrystanLea - I am flashing via Etcher now. Another quick question - why is the image so large? It is 15.5GB, and even a fairly loaded version of Raspbian is notably smaller than that? How much space is left for user data? (I’m using a 16GB card).

Compressing an image file is a little tricky and not something we do at the moment. If anyone wants to offer of course :slight_smile:


I wasn’t complaining - just wondered how it allowed space for user data on a 16GB card - but perhaps 500MB is enough anyway.


No that is a whole card and includes all the partitions, but the partitions are empty not full.


df -h

4 posts were split to a new topic: Duplicate Inputs with new Image

2 posts were split to a new topic: Problems with restore from USB

@TrystanLea please note emonscripts documentation has not been updated

Thanks @borpin now updated:

1 Like

I have been keeping mine up to date, at least I thought.

I guess upgrading does not upgrade everything?

It says I still have Release emonSD-26Oct17?

Can I get an answer on this? I guess the upgrading does not upgrade the SD card fully?

As it says in the main post…

Okay, so I can get that, and I do, but what confuses me:

The update scripts do not ever update the OS at all? How do you guys deal with that? You are developing software that works on X amount of releases of SD cards at this point?

I always thought that it would apt-update/upgrade also…so why would I not have the latest version of python?

I guess I was just trying to understand the update functionality of the software that you wrote. It never updates the OS? Does this mean that no vulnerabilities ever get patched? Thanks for the replies!

Yes they do update the OS - that isn’t the issue.

Because if it wasn’t installed at first it would not get installed. Python3 is completely different to Python and is not part of the OS.

Emoncms has grown over the years and one of the issues recently has been the move from Python to Python3. Some of the things done previously have tripped us up when trying to move so the decision was made to EOL previous versions and require a full update. Bit like moving from Windows XP to Windows 7 - complete reinstall. In fact, moving from Python to Python3 in itself cannot be automatic - scripts need to be rewritten to work and there are a number of incompatibilities.

So, while not ideal, it is a fact of life that sometimes you need to start from scratch albeit with existing data.

I noticed the latest image auto-updates. Was this just my imagination??

You could be right: I have 3 copies running at the moment, testing the continuous monitoring emonPi and the changes needed to accommodate it. I noticed a few days ago that one Feeds page had the title in the browser tab as “Feed view” and two as “feed list”, then it became 2 : 1 the other way round, now all 3 are “Emoncms - feed list”.

If they are auto-updating without asking permission first, that’s extremely naughty - almost as bad as the behaviour that earned platformio the categorisation of malware - because I have a “metered” Internet connection during the daytime and I don’t want one, let alone three of them, doing a 1.5 GB download between 8 am and midnight (local time). 4.5 GB accounts for nearly half my monthly allowance.

Do you mean OS updates or emoncms updates. The former possibly (might be enabled in the Raspberry OS image by default now); emoncms I don’t think so. @TrystanLea.

I simply reboot the pi and this is what I’m getting. Seems like it’s updating the update script and running ‘apt update’.

Starting update via (v3.0) >
- emonSD version: emonSD-24Jul20
- supported images: emonSD-24Jul20 emonSD-02Oct19 emonSD-17Oct19
- emonSD base image check passed...continue update
git pull /opt/openenergymonitor/EmonScripts
* stable
On branch stable
Your branch is up to date with 'origin/stable'.

nothing to commit, working tree clean
Already up to date.
Main Update Script
Date: Sun 8 Nov 21:55:19 GMT 2020
EUID: 1000
openenergymonitor_dir: /opt/openenergymonitor
type: all
firmware: emonpi
Reading package lists...
Building dependency tree...
Reading state information...
python3-pip is already the newest version (18.1-5+rpt1).
0 upgraded, 0 newly installed, 0 to remove and 46 not upgraded.
Looking in indexes:,
Requirement already satisfied: redis in /home/pi/.local/lib/python3.7/site-packages (3.5.3)
Hardware detected: rfm2pi
Running apt-get update
Get:1 buster InRelease [15.0 kB]
Get:2 buster InRelease [32.6 kB]
Get:3 buster/main armhf Packages [13.0 MB]
Get:4 buster/main armhf Packages [331 kB]
Fetched 13.4 MB in 13s (1,059 kB/s)
Reading package lists...
git pull /opt/openenergymonitor/emonpi
* master
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
Fetching origin
   c84d6ba..f915a88  master     -> origin/master
Updating c84d6ba..f915a88
Fast-forward          | 4 ++--
 firmware/ | 2 --
 2 files changed, 2 insertions(+), 4 deletions(-)
git pull /opt/openenergymonitor/RFM2Pi
* master
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
Fetching origin