No data in 24 hour window striketime is none

Sorry if this has been answered before, but I have looked through all the documentation I can find, but can’t find anything like this in the posts.

I just installed piconsole yesterday.

When I start up the console, I get the following and the display never starts.

I thought at first the station needed some time to accumulate some data, but no change after 18 hours.

pi@raspberrypi:~ $ wfpiconsole start
[INFO ] [Logger ] Record log in /home/pi/.kivy/logs/kivy_23-08-29_1.txt
[INFO ] [Kivy ] v2.1.0
[INFO ] [Kivy ] Installed at “/home/pi/.local/lib/python3.7/site-packages/kivy/init.py”
[INFO ] [Python ] v3.7.3 (default, Jun 29 2023, 18:03:57)
[GCC 8.3.0]
[INFO ] [Python ] Interpreter at “/usr/bin/python3”
[INFO ] [Logger ] Purge log fired. Processing…
[INFO ] [Logger ] Purge finished!
[INFO ] [Config ] Verifying station details
[INFO ] [Factory ] 189 symbols loaded
[INFO ] [Image ] Providers: img_tex, img_dds, img_sdl2, img_pil (img_ffpyplayer ignored)
[INFO ] [Window ] Provider: egl_rpi
[INFO ] [GL ] Using the “OpenGL ES 2” graphics system
[INFO ] [GL ] Backend used
[INFO ] [GL ] OpenGL version <b’OpenGL ES 2.0’>
[INFO ] [GL ] OpenGL vendor <b’Broadcom’>
[INFO ] [GL ] OpenGL renderer <b’VideoCore IV HW’>
[INFO ] [GL ] OpenGL parsed version: 2, 0
[INFO ] [GL ] Shading version <b’OpenGL ES GLSL ES 1.00’>
[INFO ] [GL ] Texture max size <2048>
[INFO ] [GL ] Texture max units <8>
[INFO ] [Window ] virtual keyboard not allowed, single mode, not docked
[INFO ] [Text ] Provider: sdl2
[INFO ] [GL ] NPOT texture support is available
[INFO ] [Websocket ] 2023-08-29 09:38:58 - Opening connection
[INFO ] [Base ] Start application main loop
[INFO ] [Websocket ] 2023-08-29 09:38:59 - Connection open
[WARNING] [tempDiff ] 2023-08-29 09:39:01 - no data in 24 hour window
[WARNING] [strikeDeltaT] 2023-08-29 09:39:02 - strikeTime is None
[WARNING] [tempDiff ] 2023-08-29 09:39:24 - no data in 24 hour window
[WARNING] [strikeDeltaT] 2023-08-29 09:39:24 - strikeTime is None
[WARNING] [tempDiff ] 2023-08-29 09:40:24 - no data in 24 hour window
[WARNING] [strikeDeltaT] 2023-08-29 09:40:24 - strikeTime is None
[WARNING] [tempDiff ] 2023-08-29 09:41:24 - no data in 24 hour window
[WARNING] [strikeDeltaT] 2023-08-29 09:41:25 - strikeTime is None
[WARNING] [tempDiff ] 2023-08-29 09:42:24 - no data in 24 hour window
[WARNING] [strikeDeltaT] 2023-08-29 09:42:24 - strikeTime is None

Does anyone have any ideas or suggestions?

Thanks,
Alan

Might be a wild guess but think the script is looking for 24 hours historical data and there isn’t yet any since your station was set up less then 24 hours ago ?

That was my first guess as well. If that’s it, I will know in a few more hours. The script can’t display data it doesn’t have.

I didn’t see any kind of coldstart option that would populate zeros in the appropriate places.

@peter maybe add some catch for this case ? Think you had already coded some for another part I think in the past.

Just an update:

After approximately 21 hours ( not totally certain) the logged messages changed to just
WARNING] [strikeDeltaT] 2023-08-29 14:24:20 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-29 14:25:20 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-29 14:26:20 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-29 14:27:20 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-29 14:28:20 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-29 14:29:20 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-29 14:30:19 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-29 14:31:20 - strikeTime is None

The no data in 24 hours message has stopped.

Thanks @eric and @alan.gerhardt, I will give this situation some more thought. In general though, it is hard to distinguish between a new station that hasn’t been online for 24 hours and an existing station that is no longer reporting just from the flow of observations. There have been cases in the past where users think there is an issue with the console, only for us to find that their device is offline or no data is been sent to the WF servers. Hence the warnings printed to the screen. I can see for new users though that this can be misleading, and it would be better to suppress the warnings. How I do that though, will require some thought!

Thanks Peter!

I will just let it run for a while and see if anything changes over the next few hours. It appears that the lightning strike counter is the last item to go away, as apparently enough data has been received to stop the other warning.

The only solution I can think of offhand is a “coldstart” flag that someone could run on initial weatherstation install to suppress the warnings and possibly initialize any pertinent counters, etc.

I appreciate all of your work on this project.

Cheers,
Alan

No change today. Still showing the strike time warning.

WARNING] [strikeDeltaT] 2023-08-30 12:05:58 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-30 12:06:58 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-30 12:07:58 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-30 12:08:58 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-30 12:09:58 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-30 12:10:58 - strikeTime is None
[WARNING] [strikeDeltaT] 2023-08-30 12:11:58 - strikeTime is None

I wouldn’t worry about this. It is going to persist until your station detects a lightning strike. Until that point the last strike time is always going to be none. It’s not having any impact on the operation of the PiConsole

That’s good.

Maybe I am chasing the wrong issue.

The log is the only thing I see on the display at the moment, no panels etc. I am using windows remote desktop into the pi.

I have ordered a pi touchscreen. Maybe that will help.

Ah ok, I see. Are you using a Pi3 or a Pi4? On a Pi3 you won’t be able to see the console remotely (it’s a graphics hardware limitation), but you will see it on the screen you ordered. The fact you are seeing those warnings suggests the console is running perfectly fine (you just can’t see it)

Problem solved.

I set auto start to on, connected an external hdmi monitor, and rebooted. Works great!

I guess windows remote desktop was the issue all along.

Thanks again for your support, I really appreciate it.

Cheers,
Alan

2 Likes

You are right, it is a pi3. I had not used it in a while and thought is was a Pi4.

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 : 0000000053465b57
Model : Raspberry Pi 3 Model B Plus Rev 1.3
pi@raspberrypi:~ $

1 Like