ok didn’t look at the value @Peter 
but I’m afraid you’re going to have to add quite some icons
“The highest barometer reading recorded in the world is 1083 mb at Agata, Siberia on 31st December 1968.”
“The lowest sea level air pressure ever recorded was 870 mb (25.69 in.) in the eye of Typhoon (Tip) over the Pacific Ocean”
Hi Peter! Thank you for your work with the console, it really makes the Tempest much more user-friendly!
I updated the console and RPI OS today and broke the rig. Here’s my log on attempted startup:
<pi@raspberrypi:~ $ wfpiconsole start
[INFO ] [Logger ] Record log in /home/pi/.kivy/logs/kivy_21-03-06_10.txt
[INFO ] [Kivy ] v1.11.1
[INFO ] [Kivy ] Installed at “/home/pi/.local/lib/python3.7/site-packages/kivy/init.py”
[INFO ] [Python ] v3.7.3 (default, Jul 25 2020, 13:03:44)
[GCC 8.3.0]
[INFO ] [Python ] Interpreter at “/usr/bin/python3”
[INFO ] [Factory ] 184 symbols loaded
[INFO ] [Image ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[INFO ] [Window ] Provider: sdl2([‘window_egl_rpi’] ignored)
[CRITICAL] [Window ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - RuntimeError: b’Could not initialize EGL’
File “/home/pi/.local/lib/python3.7/site-packages/kivy/core/init.py”, line 71, in core_select_lib
cls = cls()
File “/home/pi/.local/lib/python3.7/site-packages/kivy/core/window/window_sdl2.py”, line 152, in init
super(WindowSDL, self).init()
File “/home/pi/.local/lib/python3.7/site-packages/kivy/core/window/init.py”, line 981, in init
self.create_window()
File “/home/pi/.local/lib/python3.7/site-packages/kivy/core/window/window_sdl2.py”, line 290, in create_window
self.get_gl_backend_name())
File “kivy/core/window/_window_sdl2.pyx”, line 224, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window
File “kivy/core/window/_window_sdl2.pyx”, line 74, in kivy.core.window._window_sdl2._WindowSDL2Storage.die
[INFO ] [Text ] Provider: sdl2
2021-03-06 11:33:53-0600 [-] Log opened.
[CRITICAL] [App ] Unable to get a Window, abort.>
Any suggestions?
Thank you!
Sorry you’ve run into trouble. Can you let me know what hardware you are running (Raspberry Pi version), and can you open a terminal, run the command below and share the output with me?
cat /etc/os-release
Also make a backup of you details in wfpiconsole.ini, then delete that file and start the console again with wfpiconsole start. You will need to re-enter your details, but that might be enough to fix it.
Sorry, I can’t seem to share the requested output as the forum tells me that I can’t share more than 2 links as I’m a new user…
Here’s the output sans the “links”:
<i@raspberrypi : ~ $ cat /etc/os-release
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>
I’ve removed and reinstalled wfpiconsole, created a new token, re-entered the details and still no joy. I’m running a RPI 4.
Thanks!
OK, in the wfpiconsole.ini file under [System], what does the Hardware key read?
Sorry, cut and paste error. See below:
< [System]
BarometerMax = 31.0
BarometerMin = 28.0
Timeout = 20
Hardware = Pi4
Version = v4.0.4>
No worries - just delete the post above as you don’t really want to be sharing your API keys 
The error is weird as everything looks correct. The Hardware key matches your physical hardware and everything should be OK. Can you try “installing” the console again using:
curl -sSL https://peted-davis.github.io/wfpiconsole | bash
It is possible something got messed up during the update and this will fix it. If not, I can test on a Pi4 here, but you might just have to go for a full OS wipe and restart. Sometimes this is the simplest way to fix these unexplainable bugs!
Hmm, ok. After your last suggestion, still no love. I guess I’ll try a wipe and clean install of everything as this is the only app running on the Pi.
Thanks!
Sorry! I know how annoying this can be. If it still doesn’t work after a clean install, let me know and I will dig out my Pi4 and do some testing
People always said that Los Angeles was a high pressure environment. And here I thought they were just being metaphorical 
hello
Can any help pi-console is not pulling all of the data, showing some. Done a few things, rebooted, tried updating, reset api keys, nothing seem to work
Thanks
the usual, what shows the wfpiconsole.log ? (same directory as the rest of the wfpiconsole files)
@peter @twincreeks.exeter we’ve discovered a bug in the web socket rate limit that was causing this issue. We hope to have a fix in place this week.
ok here is what i think is going on
2021-03-09 14:44:25+0000 [-] Websocket connection open
2021-03-09 14:44:25+0000 [-] Unknown message type: {“status_code”: 5, “status_message”: “AUTHORIZATION_REQUIRED - Rate limit exceed or your API Key or Oauth2 Access Token missing”}
2021-03-09 14:44:25+0000 [-] Websocket connection closed
2021-03-09 14:44:25+0000 [-] Websocket connection retrying
2021-03-09 14:44:25+0000 [WeatherFlowClientProtocol (TLSMemoryBIOProtocol),client] <twisted.internet.tcp.Connector instance at 0xac7b6830 disconnected IPv4Address(type=‘TCP’, host=‘ws.weatherflow.com’, port=443)> will retry in 5 seconds
2021-03-09 14:44:25+0000 [-] Stopping factory <main.WeatherFlowClientFactory object at 0xac7b6730>
2021-03-09 14:44:30+0000 [-] Starting factory <main.WeatherFlowClientFactory object at 0xac7b6730>
Thnaks
@dsj Thanks for the update. Been missing it
@waycooldue, it looks like your token is being rate limited. There are two possible reasons for this:
I did have one other app, delete the key few days ago
I found out what was happening on my new Windows 10 Pro 20H2 - install. I have two ethernet adapters in my computers. I have a failover setup - using two networks. It was using the NIC that is assigned to the network that my WF was not on locally. I hadn’t modified the NIC ‘metric’ to prioritize that card/network. So everything appeared fine as it did have internet connectivity, but no connectivity to my WF’s network locally?
At least that is all I can figure out. I changed the metric setting on my NICs and it’s now working as it should.
Sorry for the trouble…
@waycooldue it sounds like the second cause is probably most likely then. Let’s give it this week for the WF developers to fix the bug on their end, and the hopefully you’ll be able to get up and running.
@tcichowicz, thanks for the update, and glad you managed to track down the issue. I was really scratching my head over it, so I’m glad we have been able to sort it
Is it ok to the use the same API keys for more than one PiConsole? I built two of them, one for me and one for my parents, and I don’t know if it’s a coincidence, but since adding the second one, seems like I need to quit out of PiConsole and start it up again for it to continue to update.
