# PiConsole: Key Error 'METAR'

**URL:** <https://community.tempest.earth/t/piconsole-key-error-metar/28073>\
**Category:** WeatherFlow PiConsole\
**Created:** [February 24, 2026, 3:52pm UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073 "2026-02-24T15:52:30Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![fxblake](https://avatars.discourse-cdn.com/v4/letter/f/7993a0/32.png) [@fxblake](https://community.tempest.earth/u/fxblake)\
**Post date:** [February 24, 2026, 3:52pm UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/1 "2026-02-24T15:52:31Z")

</div>

I’ve been using WF PiConsole for well over a year and love it…worked great. I power it up in the morning and everything boots and I power it down at night. All of a sudden it stopped. The Pi boots but the WF PiConsole won’t start. I ran start and I see the script…then it just stops and won’t display my weather station. I grabbed a new card, installed the latest Pi software, and reinstalled PiConsole and got it running again. A week later, same thing. Only boots to the Pi software and no WF at all. I tried deleting the ini file to see if it would let me re-enter the data as if it were a new install…nope. I’m using a Pi 4b with a 10” screen. The last lines in the script that’s displayed are:  
KeyError: ‘METAR’  
INFO ….. Closing connection  
INFO ….. Connection closed

The only “warnings” displayed in the script are:  
[INFO] [GL] NPOT texture support is available  
WARNING: running xinput against an Xwayland server. See the xinput man page for details. (listed two times)  
[INFO] [Websocket] (date and time) - Opening connection  
WARNING: (same as above, listed eight times)

---

<div class="post-metadata">

**Author:** ![vreihen](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/vreihen/32/13217_2.png) [@vreihen](https://community.tempest.earth/u/vreihen)\
**Post date:** [February 24, 2026, 4:23pm UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/2 "2026-02-24T16:23:28Z")

</div>

There seems to be a problem with getting METAR data, as others have pointed out here:

[https://community.tempest.earth/t/wfpiconsole-crashing-key-error/26673/21?u=vreihen](https://community.tempest.earth/t/wfpiconsole-crashing-key-error/26673/21)

I don’t use WF PiConsole, nor do I know if @peter is checking in here regularly from his summer outpost in Antarctica to troubleshoot this…

---

<div class="post-metadata">

**Author:** ![btah02](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@btah02](https://community.tempest.earth/u/btah02)\
**Post date:** [February 22, 2026, 9:19pm UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/3 "2026-02-22T21:19:10Z")

</div>

Hello,

I just recently started getting this error.

Traceback (most recent call last):  
File “/home/bnewman/wfpiconsole/main.py”, line 613, in  
wfpiconsole\_app.run()  
File “/home/bnewman/wfpiconsole/venv/lib/python3.12/site-packages/kivy/app.py”, line 956, in run  
runTouchApp()  
File “/home/bnewman/wfpiconsole/venv/lib/python3.12/site-packages/kivy/base.py”, line 574, in runTouchApp  
EventLoop.mainloop()  
File “/home/bnewman/wfpiconsole/venv/lib/python3.12/site-packages/kivy/base.py”, line 339, in mainloop  
self.idle()  
File “/home/bnewman/wfpiconsole/venv/lib/python3.12/site-packages/kivy/base.py”, line 379, in idle  
Clock.tick()  
File “/home/bnewman/wfpiconsole/venv/lib/python3.12/site-packages/kivy/clock.py”, line 733, in tick  
self.post\_idle(ts, self.idle())  
File “/home/bnewman/wfpiconsole/venv/lib/python3.12/site-packages/kivy/clock.py”, line 776, in post\_idle  
self.\_process\_events()  
File “kivy/\_clock.pyx”, line 620, in kivy.\_clock.CyClockBase.\_process\_events  
File “kivy/\_clock.pyx”, line 653, in kivy.\_clock.CyClockBase.\_process\_events  
File “kivy/\_clock.pyx”, line 649, in kivy.\_clock.CyClockBase.\_process\_events  
File “kivy/\_clock.pyx”, line 218, in kivy.\_clock.ClockEvent.tick  
File “/home/bnewman/wfpiconsole/lib/sager.py”, line 77, in fetch\_forecast  
threading.Thread(target=self.generate\_forecast(), daemon=True).start()  
^^^^^^^^^^^^^^^^^^^^^^^^  
File “/home/bnewman/wfpiconsole/lib/sager.py”, line 284, in generate\_forecast  
self.get\_dial\_setting()  
File “/home/bnewman/wfpiconsole/lib/sager.py”, line 414, in get\_dial\_setting  
METAR = self.sager\_data[‘METAR’] # Closet METAR information to station location  
~~~~~~~~~~~~~~~ ^^^^^^^^^  
KeyError: ‘METAR’  
[INFO] [Websocket] 2026-02-22 15:09:35 - Closing connection  
[INFO] [Websocket] 2026-02-22 15:09:35 - Connection closed

A few weeks ago I changed my CheckWX API key to 0 and that seem to fix it.

Today I noticed Wfpiconsole was not running, so I tried starting from command line and got the same error. I tried putting my CheckWX API key back in. It still gives me the same error.

Running on Pi4 system.

Tried it on Ubuntu 24.04.4 LTS with the same issue.

I even tried reinstalling on the PI4 with no change.

Any ideas?

Thanks.

---

<div class="post-metadata">

**Author:** ![c.michael.gamble](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@c.michael.gamble](https://community.tempest.earth/u/c.michael.gamble)\
**Post date:** [February 24, 2026, 11:42am UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/4 "2026-02-24T11:42:53Z")

</div>

Having this same error this morning. I have completed the update. No resolution. I have backed up my wfpiconsole.ini file, wiped the directory, reinstalled via the script, and no resolution.

Any pointers? Not asking anyone to fix it for me, just a nudge to the next idea to try. Thanks in advance!

Of note, I did regenerate and update my checkwx api key as well. Same results.

File “/home/pi/wfpiconsole/lib/sager.py”, line 284, in generate\_forecast  
self.get\_dial\_setting()  
File “/home/pi/wfpiconsole/lib/sager.py”, line 414, in get\_dial\_setting  
METAR = self.sager\_data[‘METAR’] # Closet METAR information to station location  
~~~~~~~~~~~~~~~ ^^^^^^^^^  
KeyError: ‘METAR’  
[INFO] [Websocket] 2026-02-24 07:02:18 - Closing connection  
[INFO] [Websocket] 2026-02-24 07:02:18 - Connection closed

---

<div class="post-metadata">

**Author:** ![peter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/peter/32/1365_2.png) [@peter](https://community.tempest.earth/u/peter)\
**Post date:** [February 25, 2026, 8:24am UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/5 "2026-02-25T08:24:17Z")

</div>

Hi all, sorry you’re running into trouble. Something has happened with one of the APIs that the PiConsole hits to get METAR reports (CheckWX). This is causing the console to crash and not start.

Unfortunately I am currently travelling back from Antarctica and don’t have any means to troubleshoot the issue. I will try and get to it as soon as I can.

In the mean time, as a work around you can edit line 503 of `main.py` to prevent the crash from occurring. Replace `self.app.Sched.sager = …` with `#self.app.Sched.sager = …`. The `#` turns the line into a comment and prevents it from being executed

---

<div class="post-metadata">

**Author:** ![btah02](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@btah02](https://community.tempest.earth/u/btah02)\
**Post date:** [February 25, 2026, 3:57pm UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/6 "2026-02-25T15:57:05Z")

</div>

No worries. I understand. I have been running using UDP in the meantime. Thank you for the update. I will make that change and get back running.

Thank you!

---

<div class="post-metadata">

**Author:** ![c.michael.gamble](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@c.michael.gamble](https://community.tempest.earth/u/c.michael.gamble)\
**Post date:** [February 28, 2026, 11:54am UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/7 "2026-02-28T11:54:31Z")

</div>

For me, the error is resolved. Dang nightly reboot prompted the error. If I had just left well enough alone!

---

<div class="post-metadata">

**Author:** ![fxblake](https://avatars.discourse-cdn.com/v4/letter/f/7993a0/32.png) [@fxblake](https://community.tempest.earth/u/fxblake)\
**Post date:** [February 28, 2026, 3:16pm UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/8 "2026-02-28T15:16:08Z")

</div>

I was about to make the change Peter suggested…when I started running again. Been running for the last few days.

---

<div class="post-metadata">

**Author:** ![vinceskahan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/vinceskahan/32/2785_2.png) [@vinceskahan](https://community.tempest.earth/u/vinceskahan)\
**Post date:** [March 1, 2026, 8:42pm UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/9 "2026-03-01T20:42:22Z")

</div>

Hope you get frequent flyer (and floater) miles. Stay warm !

---

<div class="post-metadata">

**Author:** ![user293](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/user293/32/13484_2.png) [@user293](https://community.tempest.earth/u/user293)\
**Post date:** [March 11, 2026, 4:43pm UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/10 "2026-03-11T16:43:07Z")

</div>

Speaking of errors. My piconsole that is running off win11 every couple of days spits out warnings like the last 24 hours have failed. This has been happening for the last 5 months. I have off loaded python and set it all back up. I have changed routers, changed the token and I still get the warnings. I have also cleared the wfpiconsole. I’ve called Tempest and they said the station and hub are fine. I am at a complete loss.

---

<div class="post-metadata">

**Author:** ![rleeden](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/rleeden/32/13174_2.png) [@rleeden](https://community.tempest.earth/u/rleeden)\
**Post date:** [March 19, 2026, 10:18am UTC](https://community.tempest.earth/t/piconsole-key-error-metar/28073/11 "2026-03-19T10:18:16Z")

</div>

I wasn’t aware of this issue, and didn’t have the problem despite several reboots when this was first seemingly reported. But I did experience it for the first time yesterday evening (18/3/26).

Before seeing this post and suggested workaround, I removed my CheckWX API key from wfpiconsole.ini file which got my console back up and running.

I don’t remember exploring the Sager panel, so not sure what it showed, or what I’m now missing!

As, ever thanks for the quick response from Peter - even on your travels back from Antarctica! ❄
