"No Available Data" & "Real-time data is not visible"

Hello!

I’d like to ask why my RS has no available data on StationView, but it does on the ShakeNet app (1st photo). Also, I need access to the live data for an alarm system, but I can’t seem to access it through the ShakeNet app (2nd photo). Could you help me with this matter?

Thank you in advance for your response.

Here are the screenshots:



1 Like

Hello k8acirer,

Yes, I can see the same on my side, with data available on DataView, albeit delayed by some hours compared to real-time.

This is why you do not see anything on StationView or in the main Mobile App window, as those display the latest 10 minutes of activity.

Could I please ask you to download the logs from your Shake (instructions can be found here, if needed) and send them to me?

Thank you.

Hello again!

My apologies for not responding sooner. I encountered an issue with the configured IP address, but it is working now.

Regarding the log files, here they are:
RSH.R1B64.2025-03-28T04_08_45.logs.tar (3.3 MB)

1 Like

Hello k8acirer,

It’s no trouble at all. And thank you for the log files.

However, it seems that the zipped archive is corrupt, for some reason. Can you do the following procedure before downloading the new logs?

  • turn off your Shake
  • disconnect all cables from it
  • restart your router and wait for it to regain internet connection
  • now reconnect LAN and power cable to the Shake in this order
  • turn on the Shake again

Then, wait for about 6-12 hours and, when you can, download the new logs and send them to me.

Thank you!

Hello!

Thank you for the response! We have already followed your instructions. Here are the log files:
RSH.R1B64.2025-04-05T07_21_27.logs.tar (3.3 MB)

1 Like

Hello, and thank you for the logs!

They confirm what I was thinking, that is, that the Shake cannot reach any NTP time synchronization servers, and remains some hours behind real-time.

2025 094 06:08:14: NTP failed to start, continuing without it
Apr 04 06:10:35 raspberryshake systemd[1]: Failed to start Network Time Service.

To fix this:

  1. Make sure that port 123 is open in both UDP and TCP directions on your firewall. If this port is closed, the Shake will not be able to synchronize its time correctly.

  2. Try to execute the following commands one after the other after SSHing into the Shake (SSH instructions here):

sudo systemctl stop ntp
sudo systemctl restart ntpd
sudo systemctl start ntp
  1. If, instead, the port is already open and the above command sequence has not worked, then it may be necessary to manually specify NTP servers in the /etc/ntp.conf file, following the instructions on this manual page: NTP and GPS timing details.

Let me know how these checks go!

Hello!

I just want to say that we noticed that the error might be because of “failed to start configure bluetooth” (Please check the 1st photo). What should we do about this?

Then about IP addressing, it says ‘NONE’—is it really supposed to be like that? Should it really say ‘None’?" (2nd photo). Although, eth0 is okay.

That’s the update so far.

Thank you so much for your response, I will talk to my team with regards to your latest response about this matter.


1 Like

Hello!

Update: It’s all working out now. (Live data in shakenet & available data on station view) Thank you so much for your help. :smiling_face::heart:

2 Likes

Hello k8acirer,

The first thing I did this morning was to check if your station was trasmitting live data; very happy to see that everything is working as it should now!

It was my pleasure. And, if anything else comes up in the future, you know where to find us.

1 Like