Rasberry pi random disconnect and not reconnecting

FlightAware ADS-B Flight Tracking
1

Having issues with my Raspberry Pi disconnecting and not always reconnecting.
Issues I have noted over the past 2 months:

  1. Skyaware stopped working on Chrome but at the same time was working when I pulled up my site using a different browser. The Chrome browser would show 2-3 planes then drop off to 0 while at the same time I could 20-30 planes on the alternate browser.
  2. Raspberry Pi would disconnect - needed to restart to have it reconnect
  3. Raspberry Pi would disconnect but would reconnect on its own many hours later (Has reconnected on its own when I am at work)
  4. Skyaware shows the weather radar while at the same time it says I am not connected.
    On Skyaware 6.1

The issue really has come to fruition the past two week with long outages (6-8 hours).
I am not very tech savvy and I get lost in the technical language when reading the answers in the forum. I am more of plug and play so I would be grateful if any of the answers/suggestions explained things for a true novice.

2

Which type of network connection do you have? LAN or WiFi?
While the site is not loading. are you trying to ping the raspberry as well?

If this is also not working, you might have networking issues.
To avoid longer outages, i would suggest a ping script which reboots the device if a specific address is not pingable from your raspberry.

Pingfail

However this fixes the symptom, but not the root cause where you need to take a closer look

3

Common causes of such disconnects of pi are often 1) wi-fi issues (as aluded to by other reply) or 2) power supply or power quality issues.

4

Thank you for the advice. I have done the following:

  1. Was able to get 7.1 up and running. (it showed that my clock was off by 53 hours). But that message went away soon after the reboot using 7.1) Any idea how I can check the clock to see if it is currently correct?
  2. Had my service provider reboot everything. I also did the same prior but they suggested the same thing.
  3. Changed power supply. (new power strip)

Has been up and running for the past 24 hours with no interruptions.

5

for the clock check issue the following command from the SSH CLI screen:
timedatectl

This will show you something like this

pi@orangepitom15:~$ timedatectl
Local time: Mon 2022-03-14 19:39:29 CET
Universal time: Mon 2022-03-14 18:39:29 UTC
RTC time: Mon 2022-03-14 18:39:24
Time zone: Europe/Amsterdam (CET, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

6

Wow, that’s also a quick and handy way to find the current UTC time. Thanks!

1 Like
7

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.