Station AM.R41DF.00.EHZ is not online

I am installing a new unit and have data forwarding on and it shows connected. I cannot see it on station view or the ShakeNet app

Hello Russell,

Could you please post the logs from your Shake, so I can try to get more insight on what’s happening?

In case you don’t know or don’t remember how to do it, they are downloadable from the Raspberry Shake’s web configuration page, accessible entering the rs.local address in your browser, then by clicking on the “Download Logs” button.

One other thing I was going to mention was that the time did not seem correct. However it now looks ok I don’t know if I mis-read it yesterday or it has updated.
time on shake = 15:43
local time (US eastern standard) = 10:43

RSH.R41DF.2020-12-05T15_40_35.logs.tar (371.5 KB)

Thank you for the logs Russell.

From them, everything looks fine, except that time synchronization issue that solved itself. That was likely the case of your station not appearing on the StationView map, since if the time is not correctly set by the NTP servers (which is done by the Shake automatically) then the data will not appear online.

Now you can see your station at this address:

Enjoy Shaking!

I saw that it was online. Once it is setup, I will mail it to Vermont for installation so I made a few changes to prepare it for the new location.
I set the final location and attempted to set a static IP address for the network it will be connected to.
The unit now shows "Server Connection: not connected "
On the Networks page set static IP is currently unchecked, the static IP field is blank and the DNS server is (560.5 KB)

A question, just to be clear. Does the network that this unit will be connected to have the same specifications than the one that you are using right now?

From the postboot.log file this appears:

2020 341 18:58:27: Network detection failed, unable to curl or ping common sites
2020 341 18:58:27: No internet connection found
2020 341 18:58:27: Network detection failed, unable to curl or ping common sites

and it shows that the DNS server you input was

If the Static IP configuration from the rs.local page does not work, then I would suggest using the procedure described in the second section of this page:

However, it may be more convenient (if obviously the logistics are not a problem with you) testing the Shake in the new location before doing these changes, to see if the unit will adapt to the new network by itself.

The network it is currently on is not the same. I have shipped it and will have them install it in the new location to see what happens.

I would like to confirm the expected behavior when it is plugged in on the new network. The static address we want to use is At present the Use static IP box is not checked, the static IP field is blank and the DNS is Do we just plug it in or do we need to check the static IP box and enter

For the initial setup, it took almost 24h for it to show on the network. While it is currently off-line, it does show the location on the network map. When we plug it in in the new location, should we expect to see it sooner?


Hello Russell,

Thank you for explaining the situation. On the speed of data appearing on our servers, it will depend from the DNS propagation, which is out of our control. Usually, it is inside the 24/48h time window.

When the Shake arrives at the new location, and you will install it this is the procedure that you will have to follow:

There are two possible ways - setting a manual IP and DNS in the http://rs.local web config, or adding a line to /etc/dhcpcd.conf in the Shake filesystem.

  1. The first doesn’t require logging into the Shake. Navigate to rs.local, make note of the Shake’s IP address, then click on the Settings gear icon (high on the left) to access the configuration menu.

    Click on NETWORK, then under ETHERNET SETTINGS, click on “Enable static IP”.

    Fill out the Static IP field with the address you copied from the front page.

    Fill out the DNS server field with the server of your choice or a generic but reliable DNS service. OpenDNS, which is, is a good choice. You can also use Cloudflare DNS service by entering or Google by entering

The second way, a bit more complex, in which you can keep your Shake on a dynamic IP (assigned by your modem/router):

  1. SSH into the Shake (guide here:

    Once you’re in, copy and paste these commands (this example is for Cloudflare DNS):

    sudo echo 'static domain_name_servers=' >> /etc/dhcpcd.conf
    sudo service dhcpcd restart

    Now make sure those changes took hold:

    nano /etc/resolv.conf

    The file should look like the following:

    # Generated by resolvconf

You should not need to restart, these changes will take effect immediately, but if you want, you can still do it.