Last Strike 19903 days ago

Developers WeatherFlow PiConsole
1

It is currently storming here.
The Strike Count is incrementing as I am typing this.
However, the Last Strike is stuck on 19903 days ago.
Has anyone had this issue?
Reboot did not resolve the issue…
image

2

19903 days ago was day 0, unix time. I suspect this is just the way for the interface to say ‘no lightning strikes recorded for this station’ - I don’t know how long it takes for the ‘last strike’ time to sync.

3

I would hope it is quicker than an Epoch…
:grin:

3 Likes
4

There is definitely something wrong here! Are you using the UDP interface? (the - I see for strike frequency would suggest you are)

5

I know what you did there. I did the math too :slight_smile:

6

Yes. Am using the UDP interface.

7

Also noticing missing Rain info, Temps Hi/Lows, and Barometer High/Low/Trend:

image
image1920×1105 114 KB

8

Ok I’ll take a look and see if I can see what is going on. I’m travelling at the moment so it won’t be until next week unfortunately

1 Like
9

image

10

WeatherFlow PiConsole v24.6.2

Still missing details such as:
Temperature High/Low/Difference/Trend
Solar Peak Sun Hours
and Lightning still says 19937 days ago

am using UDP with local (LAN) Tempest

Also looking for a way to turn off the Rainfall “Year” measurement,
as it is way off because I changed out from Air/Sky to Tempest…

11

Couple of things going on here.

  1. temperature difference, trend and peak sun hours will not populate in UDP only mode. They require historical data to calculate and the PiConsole has no built in cache. It fetches the historical data from the API. Therefore REST API services need to be enabled alongside UDP to populate these fields

  2. I have been unable to recreate the 19937 days ago issue. On UDP only mode, my test setup shows the correct time since the last evt_strike packet was received. I would suggest restarting the console to see if that fixes the issue.

  3. the rainfall Year measurement cannot be easily turned off without editing the code. If you restart the console in UDP only mode, however, it should reset to zero.

If a reset doesn’t fix these issues, I would suggest trying to reinstall the console. It’s possible something has become corrupted in the install

1 Like
12

How do I determine if this is currently turned on and working?

13

You can look at the bottom of your wfpiconsole.ini file for one way to do it…

Older versions would include this:

[System]
Connection = UDP
rest_api = 1

I think you need your values also present in the [Keys] section which used to be at the top of the file…

14

The rest_api was already on.

Now that I know that it is turned on, how can I determine if it is doing anything?

15

Please can you share the content of your wfpiconsole.log file?

16

wfpiconsole.txt (2.2 MB)

Here it is.

17

OK, there is a lot going on here.

Firstly, all the API calls are failing. Either your personal access token is incorrect, or there is no data being returned in the call

[WARNING] [request_api ] 2024-08-26 12:49:15 - last_6h call failed
[WARNING] [request_api ] 2024-08-26 12:49:17 - last_24h call failed
[WARNING] [request_api ] 2024-08-26 12:49:17 - Today call failed
[WARNING] [request_api ] 2024-08-26 12:49:18 - Yesterday call failed
[WARNING] [request_api ] 2024-08-26 12:49:18 - Month call failed
[WARNING] [request_api ] 2024-08-26 12:49:19 - Month call failed
[WARNING] [request_api ] 2024-08-26 12:49:19 - Year call failed

Secondly, out_temp is returning as None, which is why many of the temperature fields are not populating.

[WARNING] [feelsLike   ] 2024-07-19 00:34:02 - out_temp is None
[WARNING] [dewPoint    ] 2024-07-19 00:34:02 - out_temp is None
[WARNING] [temp_diff   ] 2024-07-19 00:34:02 - out_temp is None
[WARNING] [temp_trend  ] 2024-07-19 00:34:02 - out_temp is None
[WARNING] [temp_max    ] 2024-07-19 00:34:02 - temp is None
[WARNING] [temp_min    ] 2024-07-19 00:34:02 - Temp is None

My suggestion would be to stop the console and delete the wfpiconsole.ini file. Then restart the console and go through the process of generating a new one. If this doesn’t fix the warnings, I would make sure that your Tempest is actually reporting data, particularly temperature data (can you share your station ID?).

18

You should post your wfconsole.ini file as well (with the keys at the top obfuscated). At a minimum save your old .ini file just in case there are more questions

19

Here is the station ID:
https://tempestwx.com/station/147356/grid

20

Here is the .ini - with the [Keys] removed
wfpiconsole.ini.txt (1.2 KB)