Hi…I did a search in the forum, but did not come up with a clear solution. I keep getting warnings about no data in the 3 and 24 hour windows. I am running python 3.1 off of a win11 laptop. I have unloaded and reloaded the piconsole sw and I am still receiving those warnings. Another odd thing I was seeing 103.5 degrees in the trend area of the temp block. Everything else seems correct. The temps are now where they should be in the 40s. I have rebooted the piconsole as well as the hub. So far i am stumped after trying all of the prerequisite resets. Any ideas will be appreciated. Thank you
These warnings happen when the PiConsole cannot fetch data from the API for the period of interest (3 hours, 24 hours etc.). Assuming there is no API issue, it is usually because data is not being reported by your station. Please can you confirm your station ID?
Hi Peter. Thank you for your reply. My station ID is 65599. When I woke up this morning my station was off line. I rebooted my router and the station hub and all is back on line. I checked the sensor status and had all green lights. Last week I enabled sudo, but then I read that it could be a security risk for my laptop. I then disabled it. So, I don’t know if I corrupted anything in the process. Right now I am at a loss for a solution. Maybe my station is ready to bite the dust:grimacing:![]()
Any help will be appreciated.
This isn’t really an issue with the console. Looking at your station there are large gaps with no data, and the console is just reporting an error when it requests data from those gaps. Once the console stops requesting data from those gaps, the errors will go away. It’s possible your station might be about to bite the dust, but sometimes it is just random glitches
Thank you Peter. Im going to reach out to customer service to see if they can run diagnostics on it.
Hi Peter,
I figured out the problem. The power supply to the Tempest hub went bad. I noticed the green light was flickering and going to red. So I tried another power supply and everything is back on line. I’ll keep an eye on things to make there are no more warnings.
Well, that was part of the problem. I’m still receiving the warnings. Customer service hasn’t contacted me as of yet. I’ll have to sit tight for now.
Remember that these warnings are because there are past gaps in your data stream within the last 24 hours. For example, your station reported no data between 11/12/2025 2:25 AM and 11/12/2025 9:15 AM. If you are still getting these warnings after 24 hours with no significant data gaps, I will take another look
Thank you Peter. I will keep an eye on it. I really appreciate your assistance on this.
Hi Peter, Well, Tempest customer service said my station 65599 is operating as it should. The hub is now working since I changed out the power supply. However, I am still getting the no data in the 24 hour window warnings. Maybe it would help to delete the console version I am running and reinstall it? Or the other issue could be the Script app I am running to report to Weather underground? I am at a loss now. Thank you for any additional support that you can provide.
Ok, I’ll look into this a bit more. Please can you send me a PM with the contents of your wfpiconsole.ini file?
I just sent over the file content to you. Thanks very much. ![]()
OK, this is strange as I don’t get any warnings when I run your station. Can you check the timestamp of the warning. Is it recent or are they old warnings that are just left behind in the terminal?
Ok, If you’re not seeing any warnings now that’s good. The data coming from your station looks good and there are no data gaps in the last 24 hours. You shouldn’t start to see the warnings again unless gaps appear in the data from your station. If you do see a warning again, please share the contents of the wfpiconsole.log file before you stop or restart the console
Sounds good. Cheers and thanks again. I’ll be buying a cup of coffee soon ![]()
Hi Peter….It appears my Piconsole cleared out the warnings. I only have 1 that said the pin fail but it appears it reestablished the connection as you can see by the log data I copied below. Have a great weekend.
[WARNING] [Websocket ] 2025-11-14 09:22:07 - Ping failed
[INFO ] [Websocket ] 2025-11-14 09:22:07 - Closing connection
[INFO ] [Websocket ] 2025-11-14 09:22:07 - Connection closed
[INFO ] [Websocket ] 2025-11-14 09:22:17 - Opening connection
[INFO ] [Websocket ] 2025-11-14 09:22:18 - Connection open
Hi Peter …here we go again next ill send you the logs. If nothing can be done. I can live with the errors. I just might do a fresh install.
[Keys]
WeatherFlow = 73e3a7af-e941-4ebf-b46d-541ed18d03c9
CheckWX = ee88bb2507d24139bb8fd61610
[Station]
StationID = 65599
TempestID = 178845
TempestSN = ST-00155961
SkyID =
SkySN =
OutAirID =
OutAirSN =
InAirID =
InAirSN =
TempestHeight = 8.53440010547638
SkyHeight =
OutAirHeight =
Latitude = 41.51522
Longitude = -73.57993
Elevation = 250.7707061767578
Timezone = America/New_York
Name = Zero North 40 007
[Units]
Temp = f
Pressure = inhg
Wind = mph
Direction = cardinal
Precip = in
Distance = mi
Other = imperial
[Display]
TimeFormat = 12 hr
DateFormat = Mon, 01 Jan 0000
UpdateNotification = 1
PanelCount = 6
LightningPanel = 1
lightning_timeout = 0
IndoorTemp = 0
Cursor = 1
Border = 1
Fullscreen = 1
Width = 800
Height = 480
[FeelsLike]
ExtremelyCold = 15
FreezingCold = 28
VeryCold = 32
Cold = 45
Mild = 59
Warm = 68
Hot = 80
VeryHot = 86
[PrimaryPanels]
PanelOne = Forecast
PanelTwo = Temperature
PanelThree = WindSpeed
PanelFour = SunriseSunset
PanelFive = Rainfall
PanelSix = Barometer
[SecondaryPanels]
PanelOne = Sager
PanelTwo = Forecast
PanelThree =
PanelFour = MoonPhase
PanelFive =
PanelSix = Lightning
[System]
Connection = Websocket
rest_api = 1
stats_endpoint = 0
SagerInterval = 2
Timeout = 20
Hardware = Other
Version = v25.9.2
I’ve just checked your station again and there was a 10 minute gap in your data between 3:25 and 3:35 AM, which explains the warnings you see in the terminal. You are also seeing a lot ping errors - these happen when the console is unable to reach the WF servers. You might want to check your internet connection. It would explain the missing gaps in your data and all the ping errors being thrown by the console



