On a Pi4 alt-tab should bring the terminal to the front. On a Pi3, you would need to use VNC or SSH to connect to the Pi. This will show you the Terminal. Does that help? Is it still “frozen”?
I have a Pi 3B+. Using SSH I can login but just get that terminal window. Using port 22 to connect. It’s not frozen now, I rebooted the Pi to get it going again. I can check for errors when it freezes again if I can figure out how to view the terminal.
Oops - my mistake, SSH isn’t going to work. The best option would be VNC. With a VNC connection you’ll see the Pi desktop and you can open a terminal from which you can start the console with wfpiconsole start. Any errors will then be printed to that terminal. If you have the console set to auto-run, you can stop it first with wfpiconsole stop.
OK, I was able to VNC in and stopped / restarted wfpiconsole. No errors shown at startup. But it appears that I will need to keep the VNC connection open until it freezes again to see if any errors show up. I’ll have to setup the VNC connection from another computer later today so I can keep it running.
I’m not sure of your exact setup, but I use RealVNC viewer (https://www.realvnc.com/en/connect/download/viewer/) to connect to my Pi and I can happily close the viewer without interrupting the console. This is one of VNCs biggest benefits over SSH.
1 Like
Ahhh, I didn’t know, figured it would just shut down like SSH if I exited. I did restart the wfpiconsole and noticed these errors when starting.
020-04-05 15:20:37-0400 [-] Starting factory <main.WeatherFlowClientFactory object at 0x6fd74990>
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 131 (XInputExtension)
Minor opcode of failed request: 3 (X_OpenDevice)
Device id in failed request: 0x0
Serial number of failed request: 15
Current serial number in output stream: 15
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 131 (XInputExtension)
Minor opcode of failed request: 3 (X_OpenDevice)
Device id in failed request: 0x0
Serial number of failed request: 15
Current serial number in output stream: 15
These are not errors that I have seen before… 
. Do they stop the console from running? It looks like it is something to do with the devices that are attached to your Pi. Do you have something attached that isn’t a regular keyboard or mouse?
The console starts and appears to run normally (other then it stopping to collect data after awhile). The only things attached is the official Pi display and a bluetooth mini keyboard.
OK - if it runs normally then I think we can probably ignore that error.
This I am more concerned about. Is this still the same “freeze up” error you were seeing, when the console stops updating, or is it just a momentary pause when a new observation arrives?
It hasn’t stopped collecting data since the last reboot about 24 hours ago. If / when it happens again I’ll take a look at the console and see if any additional errors show up.
1 Like
I also have upgraded to the newest version 3.1 and had no problems updating about 5 to 6 days ago. But, now the wfpiconsole runs for awhile and then it stops updating data, but the clock and sunrise/sunset is updating. I have to unplug or stop it through SSH. It starts up fine and continues for about a day. I believe I’m using a pi 3 B+. Station ID 5815.
Thanks for info. There is clearly something going on that I need to investigate. It would be very useful if you could share the terminal output when the console next freezes. As I explained to @hankster above, you will need to setup a VNC connection to your pi to do this, and then start the console manually from a terminal using wfpiconsole start rather than the relying on the autostart (you might have to stop the current console that is running first with wfpiconsole stop). This will help shed some light on what is happening.
Ok Peter, I will give it a whirl and report back.
Whew… I’m glad I’m not the only one this is happening to. 
strange as I have it running for … and it just runs. Let’s try to narrow down maybe ?
let’s see if we all run the same os and hardware
first os : in terminal : cat /etc/os-release
**pi@WF_console** : cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
hardware paste this in terminal : cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 76.80
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 76.80
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 76.80
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 76.80
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : BCM2835
Revision : a02082
Serial : 00000000b58ea0d4
Take note of the revision number in the second last line and then refer to the table below.
Revision : a02082 → pi 3 model B made by sony UK
conclusion in my case : Pi 3B running strech
No need to put all the details like I did but for those who didn’t know how to find it … the long story
and if you want to get it quicker
pi@WF_console:~ $ cat /sys/firmware/devicetree/base/model
Raspberry Pi 3 Model B Rev 1.2
1 Like
Like @eric, I’ve had my non-development console running for days and haven’t had any issues. Narrowing down the OS/hardware combinations is a great idea @hankster, @padieter . I am running:
Raspberry Pi 3 Model B Rev 1.2 running Buster
Can you also comment on your network setup? Is it any more complicated than a single router running one WiFi network/wired network.
Here is my info so far:
Nothing weird with my wired/wireless network I think. I have a DSL router that I don’t connect to wirelessly because I lost the password a million years ago, so I just use my wireless router connection for the last million years:) Only other recent changes, are my kids are using the wireless network more for “schooling”.
Pi board version: Raspberry Pi 3 Model B Plus Rev 1.3
PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/”
SUPPORT_URL=“RaspbianForums - Raspbian”
BUG_REPORT_URL=RaspbianBugs - Raspbian
pi@raspberrypi:~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
model name : ARMv7 Processor rev 4 (v7l)
Nothing really special on my end. Used no wired connects as my modem / router is located in a place that isn’t ideal for wired. I do run an extender out in my shed as I have a TOS system there that requires a wired connection. Pdetty much been the same setup for a few years now.
PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/”
SUPPORT_URL=“RaspbianForums - Raspbian”
BUG_REPORT_URL=“RaspbianBugs - Raspbian”
pi@raspberrypi:~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 89.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 89.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 89.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 89.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : BCM2835
Revision : a020d3
Serial : 000000001ca88519
Model : Raspberry Pi 3 Model B Plus Rev 1.3
to be complete, I’m running wired via 2 switches and Ubiquity security gate …
Thanks for the info @hankster, @padieter, and @eric. It looks like we are all running pretty much the same setup. I’m assuming the Rev 1.2 vs. Rev 1.3 on the Raspberry Pi boards doesn’t make a difference. @padieter I am currently running your station with some extra debugging info that tells me the time lag between each SKY observation that is received. So far it hasn’t been greater than 80 seconds, and is matching the rate at which the observations are updated on the web. If you and @hankster can let me know as soon as you see another freeze, and share any errors that you might see on the terminal (there might not be any…), that would be ace!