PiConsole crashes when there is heavy rain

Developers WeatherFlow PiConsole
1

I leave in south Florida, and when we have heavy rain the console crashes all the time. I have to reboot everything.
Is there a log I could send ta take a look at what is happening or a trick to avoid the crash ?

Maxime.

2

Sorry you’re having issues! There is a log file called wfpiconsole.log found in the ~\wfpiconsole\ directory. If you can share the contents of that file, I can take a look. The content of the file is also printed to the terminal if you start the console manually

3

it isn’t waterproof. :wink:

2 Likes
4

here is the content of today’s Log & with heavy rain, the system crashed.
Thank you for your help.

[INFO ] [Logger ] Record log in /home/maxime/.kivy/logs/kivy_23-07-06_2.txt
[INFO ] [Kivy ] v2.1.0
[INFO ] [Kivy ] Installed at “/home/maxime/.local/lib/python3.8/site-packages/kivy/init.py”
[INFO ] [Python ] v3.8.10 (default, May 26 2023, 14:05:08)
[GCC 9.4.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: sdl2
[INFO ] [GL ] Using the “OpenGL ES 2” graphics system
[INFO ] [GL ] Backend used
[INFO ] [GL ] OpenGL version <b’3.0 Mesa 21.2.6’>
[INFO ] [GL ] OpenGL vendor <b’Intel Open Source Technology Center’>
[INFO ] [GL ] OpenGL renderer <b’Mesa DRI Intel(R) HD Graphics (CHV)‘>
[INFO ] [GL ] OpenGL parsed version: 3, 0
[INFO ] [GL ] Shading version <b’1.30’>
[INFO ] [GL ] Texture max size <16384>
[INFO ] [GL ] Texture max units <32>
[INFO ] [Window ] auto add sdl2 input provider
[INFO ] [Window ] virtual keyboard not allowed, single mode, not docked
[INFO ] [Text ] Provider: sdl2
[INFO ] [GL ] NPOT texture support is available
[INFO ] [Websocket ] 2023-07-06 16:54:46 - Opening connection
[INFO ] [ProbeSysfs ] device match: /dev/input/event3
[INFO ] [MTD ] Read event from </dev/input/event3>
[INFO ] [ProbeSysfs ] device match: /dev/input/event3
[INFO ] [HIDInput ] Read event from </dev/input/event3>
[INFO ] [Base ] Start application main loop
[INFO ] [MTD ] </dev/input/event3> range position X is 0 - 9600
[INFO ] [MTD ] </dev/input/event3> range position Y is 0 - 7200
[INFO ] [MTD ] </dev/input/event3> range touch major is 0 - 0
[INFO ] [MTD ] </dev/input/event3> range touch minor is 0 - 0
[INFO ] [MTD ] </dev/input/event3> range pressure is 0 - 255
[INFO ] [MTD ] </dev/input/event3> axes invertion: X is 0, Y is 0
[INFO ] [MTD ] </dev/input/event3> rotation set to 0
[INFO ] [HIDMotionEvent] using
[INFO ] [HIDMotionEvent] range ABS X position is 0 - 9600
[INFO ] [HIDMotionEvent] range ABS Y position is 0 - 7200
[INFO ] [HIDMotionEvent] range position X is 0 - 9600
[INFO ] [HIDMotionEvent] range position Y is 0 - 7200
[INFO ] [Websocket ] 2023-07-06 16:54:47 - Connection open
[WARNING] [request_api ] 2023-07-03 12:59:18 - last_24h call failed
[Websocket ] 2023-06-28 14:42:31 - Closing connection
[INFO ] [Websocket ] 2023-06-28 14:42:31 - Connection closed
[INFO ] [Websocket ] 2023-06-28 14:42:41 - Opening connection
[ERROR ] [Websocket ] 2023-06-28 14:42:51 - General error:
[INFO ] [Websocket ] 2023-06-28 14:43:01 - Opening connection
[ERROR ] [Websocket ] 2023-06-28 14:43:11 - General error:
[INFO ] [Websocket ] 2023-06-28 14:43:21 - Opening connection
[INFO ] [Websocket ] 2023-06-28 14:43:27 - Connection open
[WARNING] [Websocket ] 2023-06-28 14:48:27 - Watchdog triggered obs_st
[INFO ] [Websocket ] 2023-06-28 14:48:27 - Closing connection
[INFO ] [Websocket ] 2023-06-28 14:48:27 - Connection closed
[INFO ] [Websocket ] 2023-06-28 14:48:27 - Opening connection
[INFO ] [Websocket ] 2023-06-28 14:48:28 - Connection open

5

What exactly happens when it crashes, as there is nothing untoward in that log? It doesn’t look like there is an error in the code. What hardware are you using?