Setting up ruoter

I have plugged in the RS to the home router.
I cannot see it from rs.local.
I have forwarded ports from WAN to LAN Raspberry Shake local IP

123 UDP
55555 TCP
55556 TCP
22 TCP
443 TCP

Do I have to enable DMZ?

Yet on rs.local i get this info (showing the wrong date)

Shake Model : RS3D
Raspberry Pi Model : Unknown Model
System Status : RUNNING
System Version : 0.20
Ethernet Local IPv4 : 192.168.1.130
Ethernet MAC : e4:5f:01:d2:71:f8
Data Producer : ON
Data Consumer : ON
Off-line Mode : OFF
Data Forwarding : ON
Server Connection : Not Connected
Latitude : 35.8699
Longitude : 14.5244
Elevation : 1 m
System Time : 2025-12-13 21:03:04 UTC
Disk Usage : 52% Used – 3.6 Gb Available
CPU Temp : 62 C / 144 F
Uptime : 1 Days 10 Hours 22 Minutes

Hello matthewagius, and welcome to our community!

Could I ask you to scroll down on the page you copied the info from, click the orange “Download Logs” button, and then send me the resulting zipped file?

This will help us understand why the Shake is not connecting to time servers and our data one.

Thank you.

RSH.R71F8.2025-12-14T08_37_08.logs.tar (3.4 MB)

Thank you for the logs.

The first thing I’m seeing is that, apparently, both Ethernet and WiFi connections are active. Could you, just for the moment, check if the WiFi is indeed turned on, and deactivate it?

For the sake of this test, and to collect more information, could I then ask you to:

  1. Shut down the Shake
  2. Remove all the forwarding that you have done in the router and restart it
  3. Turn on the Shake again, wait for about 1 hour, then download and send the new logs

This will give me a second set with a “clean” router, to see if there are any differences in what the logs show.

Thank you again for your collaboration.

Hi, thanks for your help.
Sorry for the delay. By mistake, I replied via email instead of here.

Wifi was already off on the GUI

I followed your steps.

Attached is the log
RSH.R71F8.2025-12-15T06_29_06.logs.tar (3.2 MB)

It’s no trouble at all, and thank you for sending the new log files.

From them, it seems we have a series of issues we need to work through. In order:

The gibberish below, paired with buffer overflows, is usually a symptom of insufficient power supply, where the Shake cannot get enough power to either start or work properly.

2025 282 09:43:54>>	No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data.  This is a fatal condition and should be investigated if this condition persists!
2025 282 09:43:54>>	Data has been successfully received, fatal condition resolved.
2025 282 09:43:54>>	internal error: buffer overflow!  cannot process read data...
2025 282 09:43:54>>	buf: …æFj*D²$²@$.Dd.DFdrvAD²tv`¢LFd²kB
2025 282 09:43:54>>		16065	435

It is recommended that you check whether the current power supply continues to deliver a stable voltage between 5.0 and 5.2V and a current of at least 2.5A at all times (3.0A if the Raspberry Pi board being used is an RPi4), as a decrease in power could lead to data service interruption. If you have another Pi power supply that you know is in working condition, please try exchanging the current one with that and see if the Shake now appears more stable. If you have an official Raspberry Pi power supply to try, all the better.

As the WiFi was already off on the GUI (thank you for confirming this), but it still appears “ON” in the log files

Network Info
--------------------

  Stand-Alone Mode : OFF
       Ethernet UP : YES
           WiFi UP : YES

this may indicate that the software on the microSD card has been corrupted. I would then advise to re-burn a completely new microSD after formatting and erasing all its data/partitions (you can use DISKPART for this, as it is very efficient), and then see how the Shake behaves with the newly installed system together with the new power supply, possibly resolving the issues we are seeing. I will leave the link to the burning instructions here for your convenience: microSD card topics.

If the Shake still doesn’t connect after these two operations, please download the new logs and send them to me so I can check how the situation is progressing.

Thank you for your collaboration.