Latest Update is installed & running without a hitch.
The cursor issue is all fixed now too.
Thanks for the quick replies & ongoing support.
Cheers
Rob
I notice that same exact behavior on mine too. . .every now and again. Basically. . .I just do a “wfpiconsole start” to bring it back up to the display.
@germy and @storm_tracker, are you able to reproduce this crash? I have observed it sporadically too, but it has been too infrequent and I can’t reproduce it in order to troubleshoot
Occasionally. . .the it will bounce-out of the Display screen back to the command screen prompt: pi@wfpiconcole:~$
for no reason at all. It just catches my eye because I sit where I can see the console. . .then all-of-the-sudden the command screen pops up (similar to his image above.)
Then
pi@wfpiconcole:~$ wfpiconsole start
to get the Display screen back.
but I don’t remember if there was a “ReferenceError:” line on mine or not. Will increase my Situational Awareness if it happens again and take some notes on it and post info here. Unable to replicate this because (when it does occur). . .it occurs without notice and without touching any screen buttons etc. It just happens!
@peter quick question. I have a RPi4 with a 7 inch official touch screen currently running CumulusMX for my Tempest data. Would it be possible to run WFPiConsole at the same time on the same Pi? Or would they conflict? The only thing I would want from CumulusMX is the webserver bit. I think I prefer the WFPiConsole for the actual Pi, I do like being able to get the info from a browser though. Does that make sense?
Also, I have an Adafruit Humidity Temp Sensor for indoor temps. How do you get that data in WFPiConsole? I have a Python script to grab the data, just need to know where to put it.
@user209 I am running WeeWX and wfpiconsole on the same pi with no problems. Network, processor, and RAM utilization is quite low. So unless there is some peculiar with CumuluxMX (not familiar with it) it should be fine.
Can’t help with your second question.
@user359 Thanks for the data point. I may try it separately then try them together.
At 20:43 UTC today (Fri April 1st). . .while looking a wfpiconsole . . .it bounced-out of the Display screen and back into the command screen prompt as shown below. . the.same exact thing as shown by @germy above.
The last line above the command prompt is identical. . .
ReferenceError: weakly-referenced object no longer exists
I didn’t touch a thing. . .alls I did was just Look at it!
I then did wfpiconsole start as normal to get back to the regular Display.
Again. . .it happens Randomly. . .maybe once a day. . . .maybe once or twice every other day or every other 3rd day. Totally without notice and no Predictability.
I’ve had multiple crashes today, all during heavy rain and storms, if that helps any.
@user359 Been using CumulusMX and WFPiConsole on the same Pi and there haven’t been any issues that I can see.
@germy and @storm_tracker, thanks for the updates. I *think the cause of the issue is the device and station status panels that are visible when you click the menu button. For some reason they are being collected by the Python garbage collector, which generates the ReferenceError. I don’t know why this is happening though 
. To pin this down further, I have disabled these panels in the beta branch of the code. Would you mind switching to it, and letting me know if the errors go away? The only visual difference you should see is that the main menu page will be blank. You can switch by running these commands:
wfpiconsole stop followed up wfpiconsole beta
You can switch back to the stable branch at any point using the command wfpiconsole stable
As others have reported, there should be no issues running these together. The only downside is that if the PiConsole or CumulusMX requires you to reinstall the operating system (corruptions can happen from time to time), you will have to reinstall the other.
There are a couple of posts above that suggest approaches to pulling your own data into the Console. Here’s an example: Announcements & Updates - #2174. The line numbers in that post have changed though. Look on lines 435 and 436 for examples of Clock.schedule_interval(), and assuming you add you function call below line 420, you can access the indoor temperature variables as self.Obs['inTemp']
@peter Thanks for the response. I currently have CumuluxMX and wfpiconsole running concurrently on my Pi4 with no issues. CumulusMX is updating Windy.com and weatherunderground.com as well. I’ll probably take a image of the working SD as you are correct, I get a lot of dead sd cards, and have to reload, it is helpful to have a working image so you don’t have to start from scratch.
Also, thanks for the hints on the main.py. My python skills are pretty weak, but I’ll give it a go. Thanks!
I switched to the beta branch a few minutes ago and will let you know how it goes. Thank you!
-germ
I switched over to ‘wfpiconsole beta’ at 14:45 UTC on Sunday April 3rd. The script lines ran thru quickly. . .but. . .I thought I saw something quickly go by at that stated 22.3.4 but it went by so quickly.
The Menu screen is blank (as mentioned above). . .only items seen are:
Device Status Last Observation Battery 24hr Observvational Count
Will increase my “wfpiconsole_situational_awareness” over the coming days and take notes should it happen again [hopefully Not!]
@peter
First Followup. . .24hrs now and my WF PiConsole has NOT burped once! i.e. it has not bounced out of the Display screen back to the " pi@piconsole:~$ " command prompt screen once since ‘wfpiconsole beta’ was initiated. I will just leave it on the ‘beta’ UFN (Until Further Notice) or you deem otherwise.
JL
@peter
Second Followup. . .after having my ‘wfpiconsole’ on the “beta” version for over 30 hours…it was just fine with no bounce-outs of the Display screen. So…I switched it back to ‘wfpiconsole stable’ and it’s been running now slightly over 24 hours (as of 19:41 UTC on Apr 6th) and it, too, so far, has not bounced-out of the Display screen. . .like it had before. Will continue to monitor. Ooops (Ruh Roh!) Just had one (bounce-out) at 21:52 UTC…but quickly got back in to Display with ‘wfpiconsole start’. If these don’t happen continuously. . .then they don’t bother me. IF it becomes a chronic problem. . .will have to revert back to “beta.”
Is there something changed about the updates of the weather icon? I changed this line:
self.app.Sched.metDownload = Clock.schedule_once(self.fetch_forecast, 60)
But still not within 60 seconds?
13:57 UTC on 04/07/22. . .was forced to switch back to ‘beta branch’ because the “stable” branch is tooo UNstable. Will leave it on ‘wfpiconsole beta’ for the remainder of time.
