Error updating EmonSD / EmonCMS from 11.13.4 to current

Vster · 7 June 2026 23:30

I’m trying to update EmonSD version 11.13.4 (due to MQTT being too old mainly - my new HA build is whining v3.1 is too old!).

Running the web UI updater or the component updates gives a long list of log output that ends with

/opt/openenergymonitor/EmonScripts/update/update_component.sh: line 33: [: too many arguments

I can only see this error on GitHub, but with no resolution.

Has anyone had this before / have any ideas what to do?

awjlogan · 8 June 2026 19:26

Hi @Vster and @Robert.Wall - I think this might be an issue that has been surfaced by a newer version of PHP. Would you be able to change line 33 in ./update/update_component.sh to: if [ "$result" != "[]" ]; then and see if that fixes it? Also, to help, could you put the following line just before: printf 'result=<%s>\n' "$result" - that should print the value of result.

@TrystanLea - link to the issue.

Robert.Wall · 8 June 2026 20:42

My ‘latest’ is 11.13.0 - I can try the update if it will help? I’m still running on emonSD-10Nov22 SD image download, which has been updated in situ.

My PHP is Version 8.1.12 (Zend Version 4.1.12)

[If I do, I’ll take the SD card out and image it first.]

Vster · 8 June 2026 21:19

@awjlogan I’ve done the changes requested, just taking a backup after reading @Robert.Wall’s post. While looking at the new EmonSD images, I’ve noticed that the latest image does not support the RPi2 (which I’ve run for 15 years!), as 32bit seems to have been dropped? Will this cause an issue or any more/other issues?

Vster · 8 June 2026 22:45

OK, now I’m really confused. My EmonCMS dashboard is showing version 11.13.4 which appears to be the latest version. Released two weeks ago? The update failed, and I haven’t previously updated in well over a year. But looking at the images in the EmonSD downloads page, it looks like this install is the 21Jul21 version. The OS components aren’t up to date.

Running the patched version of update_component.sh doesn’t seem to do anything, it just show the old log file again. I added a row of asterisks to the end, and that’s what shows up, no corrected or printf result.

Looking at the Admin page I seem to be running PHP Version: 7.3.31-1~deb10u4 (Zend Version 3.3.31).

I think it may be time to buy a Pi3 and a new SD card, reinstall and migrate all the data?

TrystanLea · 9 June 2026 12:15

Hello @Vster

Yes you are now running the latest stable release of at least emoncms core. What happens if you now reboot and try running an Admin > Full update again?

Please copy full error details here if you see any more.

Vster · 9 June 2026 21:12

Shame the Pi2 didn’t get to three years of uptime!

Well, that was truly terrifying after that long without a reboot, but it restarted like a champ!

Log below -

LAST ENTRIES ON THE LOG FILE

Starting update via service-runner-update.sh (v3.0) >
Filesystem Size Used Avail Use% Mounted on
/dev/root 4.1G 2.6G 1.4G 65% /
devtmpfs 454M 0 454M 0% /dev
tmpfs 487M 0 487M 0% /dev/shm
tmpfs 487M 6.6M 480M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 487M 0 487M 0% /sys/fs/cgroup
tmpfs 1.0M 0 1.0M 0% /var/tmp
tmpfs 30M 0 30M 0% /tmp
tmpfs 1.0M 4.0K 1020K 1% /var/lib/php/sessions
/dev/mmcblk0p3 9.9G 5.7G 3.8G 61% /var/opt/emoncms
/dev/mmcblk0p1 253M 49M 204M 20% /boot
log2ram 50M 11M 40M 21% /var/log
tmpfs 98M 0 98M 0% /run/user/1000
- emonSD version: emonSD-21Jul21
- supported images: emonSD-10Mar26 emonSD-03Jul25 emonSD-01Feb24 emonSD-20Nov23 emonSD-10Nov22 emonSD-21Jul21 emonSD-08May21 emonSD-24Jul20 emonSD-02Oct19 emonSD-17Oct19
- emonSD base image check passed...continue update
git pull /opt/openenergymonitor/EmonScripts
master
* stable
On branch stable
Your branch is up to date with 'origin/stable'.

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)

modified: update/update_component.sh

no changes added to commit (use "git add" and/or "git commit -a")
Already up to date.
-------------------------------------------------------------
Main Update Script
-------------------------------------------------------------
Date: Tue 9 Jun 20:58:20 BST 2026
EUID: 1000
openenergymonitor_dir: /opt/openenergymonitor
type: all
serial_port: ttyAMA0
firmware: none
Hardware detected: rfm2pi
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 133 not upgraded.

I’m pretty sure the OS isn’t being updated as Buster is no longer supported.

It’s also complaining that update_component.sh has changed, which is had because of the patch above, but I’ve changed it back and it’s still complaining. Not sure what effect this would have or how to fix it?

Looking at the Components list version, I have -

Component name	    Version	
Emoncms Core        11.13.4
App                 3.1.5			
App                 3.1.5			
EmonHub Config      2.1.6			
Dashboard           2.4.3			
Device              2.3.6			
Graph               2.2.7			
Network Setup       1.0.5			
WiFi                2.1.1			
Backup              2.3.5			
DemandShaper        2.2.3			
Postprocess         2.4.9			
Sync                3.2.4			
Update              2.3.14			
EmonScripts         1.9.4			
RFM2Pi              1.4.3			
Avrdude-rpi         1.0.3			
Emonhub             2.7.16			
EmonPi              3.0.3

Are these fully up to date?