Stuck on ver 0.20

[CrystalCave]

…So I have a Shake that is working fine but is stuck on ver 0.20. Before you ask, I don’t think it’s a firewall issue. Looking at the update log, I think the issue happened way back in 2022: I admit this shake has been reporting fine so I haven’t looked into the unit itself until today when I bought my second shake and saw the new UI.

Here is the latest check (scroll down for my 2022 update that I think started this issue)

2026 107 01:29:22: Checking for software updates…
2026 107 01:29:22: Updating rsh-SW-updater
2026 107 01:29:23: Shake-OS is up to date (ver 0.)
ls: cannot access ‘/opt/settings/sys/ver.*’: No such file or directory
2026 107 01:29:23: Updating Docker image registry.gitlab.com/rshake-public/rsh-fe-config:v19
2026 107 01:29:33: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-producer
2026 107 01:29:34: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-consumer
2026 107 01:29:35: Software updates complete.

*********** and here is 2022 when I think the issue started ************

2022 077 12:00:16: Checking for software updates…
2022 077 12:00:16: Updating repo rsh-SW-updater
From raspberryshake-SW-public / rsh-SW-updater · GitLab
80d3fde…54f79c3 master → origin/master
2022 077 12:00:18: Upgrading UPG to latest version
2022 077 12:00:18: Installing ver 0.20 of the R-Shake system…
grep: /opt/settings/config/config.json: No such file or directory
2022 077 12:00:22: Rebooting…

RSH.REA4F.2026-04-17T01_33_26.logs.tar (3.5 MB)

[Stormchaser]

Hello CrystalCave, and welcome back to the community!

Thank you very much for the detailed info you provided, alongside the log files.

You have a couple of options that should fix your updating issue:

1. If you’re comfortable operating on the command line, SSH into the Shake and execute the following commands by pressing enter after each one:

touch /opt/settings/sys/ver.20

and then

sudo reboot

After the Shake reboots, it should automatically detect the newly created version file, and then proceed with the update. However,

2. If that does not result in a successful upgrade to v0.21.2 (our latest), then you can either send the new log files and/or re-burn the Shake OS image from the public download website (you can find all you need here).

Let us know how these tests go!

[CrystalCave]

Thank you!! I accessed my Shake via SSH, followed your commands and it updated!

[Stormchaser]

Happy to have been of help!

Enjoy your (updated) Shake!