Version 21 Update Released!

Big news for the Raspberry Shake community!

The RS Local Control Center has been fully redesigned and is now rolling out to all devices. Enjoy a cleaner, faster dashboard with real-time previews, smarter controls, and an intuitive user experience. :fire:

This update will roll out progressively across all the units in the network over the course of the next six days. if your unit is still on V20, do not worry, V21 is in the mail!

Read more here => Introducing the New Raspberry Shake Control Center

Special note: Raspberry Shake updates are automatic updates and do not require you to do anything. Within a week’s time from the release date (November 21st, 2025), your Raspberry Shake will automatically update. So, if you do not see the new rs.local/ interface yet, you will within a week’s time.

1 Like

I’m running into a few problems with this new release:

My RS3D is only recording one channel now: EHZ. The other two channels were working until last night.
My RS3D has also stopped sending data. It says “Server Connection: Inactive”, but Data Sharing is enabled and had been sending data in fine until last night.
My RS4D and Raspberry Boom appear to have changed their names from “raspberryshake” and “raspberryboom” to “rs.local”, so I don’t know how to access my 4D anymore, because rs.local only takes me to the Boom.
The link to the local helicorder is gone, so it’s harder to get to the history. All I can see locally now is the last 10 seconds (which doesn’t look like it can be expanded).

How quickly will we see the update? Mine is still on the old version.

Rolls out over 7 days. So up to 7 days.

1 Like

hello Redbeard,

please open a separate post here as technical support, and when doing so, also include the log files, you can download these from the dashboard’s home page.

thanks in advance,
richard

My RS3Ds were installed outside in some remote mountainous areas. I logged into their local control center today and found the new version pages. Very fantastic but they can’t work properly. The offline message jump out few seconds later, and I cant’ do anything but refresh it, repeatedly. I have no idea what’s going on. The old version work very well in my daily check before update. Please give me some instruction to deal with it.

hello raychu,

can you please forward the log files? either try to download them from the dashboard, (on the right side of the main page), or follow the instructions in this post:

thanks in advance,
richard

Hi ivor,
Thanks for your quick reply. I attach the log files of my one device. Please have a look and give me some suggestion. I checked local.rs of devices but they all have the same problem.

RSH.R21D0.2025-11-25T05_43_36.logs.tar (2.8 MB)

Hi,

I am having a hard time adding an additional UDP stream in datacast, There is no save button.

hello waw0102,

thank you for your report. sorry about that, you are right, something’s not working correctly here.

expected functionality:

  1. only the Add button is needed to create a new entry in the underlying UDP configuration file. that is, there is no Save button on purpose

recognized bug:

  1. the last destination created does not end up being defined in the configuration file

temporary workaround

  1. simply create a second destination definition that is fake. in this case, the first one you defined will now be saved to the configuration file and should produce the expected results.

permanent solution

  1. a patch to V21 will be issued in the near future addressing this bug

apologies for the inconvenience.

cheers,
richard

hi raychu,

thanks for the log files. we are looking into this issue and will get back to you once we have a better understanding of what’s going on here.

one thing you can try is to restart the FE config app:

  1. log in to the shake via ssh
  2. run the following command:
    > sudo systemctl restart rsh-fe-config

and then let me know if there is any change in behavior in the FE app. and if you could send the log files back again, i would be very appreciative.

thanks in advance,
richard

hi richard,

Thanks for your help first.
I followed your suggestion and tried the command of > sudo systemctl restart rsh-fe-config, but the thing went in the same way.
I refreshed page several times, tried Chrome and Edge, and got the same results.

Ray

image.png

Hi Ivor,

I can confirm that our 8 stations have the same behavior than raychu.
And restart the service didn’t succeed resolve this bug.
Possibly, in a local network, if I still on the web page then restart the shake, the interface could stay functional.
I can wait to use it, cause it seem a great improvement of the interface :).

Bye

1 Like

Same here. All 11 devices in our school network experience the same issue.

1 Like

hello Seizmolog,

if possible, can you send me the log files from one of the units having this issue?

thanks in advance,
richard

Hi folks. Apparently coincident with your pushing out the ‘great’ new RS control center, your wiz-bang s/w has utterly hosed our ability to access our device, node 71B here in Colombia.

Wrecked us completely.

For years now we’ve accessed it’s simple interface – until this s/w push you made on ur own – by accessing the LAN IP address, which, as the RS.local/ for whatever reason never resolved to our device in or LAN, we’d nailed the address to it’s MAC, and it simply always worked.

Now, we hang in space. Dead in the water.

Attempts to view data on Stationnet give obnoxious cloud flare screens like:

Simple (read EASY) suggestions to return our RS to a state that we can actually view/inspect data again
?

Thanks.

  • h

hi yeatesh,

no, your system’s not hosed, sorry your impression is otherwise. that URL you are requesting is not alive, and hasn’t been for many years. rather, if you want to be seeing your data, you should use use this address:
Station View: Raspberry Shake Network & EQ Activity Map

and, you can also see on this page that, after this update, 2740 shakes continue to stream their data just fine; this is, in fact, an all-time high!

as for the missing front-end display, there is a known issue involving a race condition with DNS services that will be addressed in a patch release to be issued within a week’s time; this is the likely source of your problem, also likely fixable with a simple command you can run on the Shake itself, if you’re so inclined:

  1. log in to the shake using ssh
  2. once logged in, issue the following command:
    > sudo systemctl restart rsh-fe-config
  3. the method you previously used to access the front-end, specifying the LAN IP, continues to work fine, nothing there was changed

warm regards,
richard

Thanks, Richard. Seems the new interface has just now made its debut appearance here
 Looks shiny and clever.

Just one Q; there 's a screaming pop-up window urging my to update my “SSH password”. I don’t recall ever setting one, but trying to provide a new one just now using the default ‘shakeme’ as old pass brought no joy. How to update/reset it? Thanks.

Can we get a link/button back on the main page to the helicorder graphics? It seems like it was removed in the “new” look.
I found it by adding /heli to the URL of my local Shake, but when I went to my Shake and saw thew new look I wasn’t too happy until I was able to search around and find the direct link in the manual.

At least the URL of the images wasn’t altered (I FTP the latest up to my website).

1 Like