I just noticed that the display was frozen and less than 2 minutes later it started back up. I’ve checked the load average on the pi and it’s around 1.1 or so, typically. The Python process is around 30% as well.
As I was typing this, it froze again at 9:14:45 and came back about 65 seconds later. I’m going to monitor the pi processes to see if anything is going on during the times it hangs for a short time.
Yeah, I’ll be glad to help. I’ll back up the files and make the changes.
Made the changes. The time is the only thing updating.
Monitoring.
As I was monitoring, the console was not hanging. I slowly added a couple of components back and then remembered that I had entered an invalid API Key under Darksky in the ini file a few days ago. I’m pretty sure the hanging problems started after that. I removed the API Key and so far it’s been up for 1 1/2 hours with no hangs. If it hangs again, I’ll go back to the troubleshooting, but I have a hunch that’s what broke it.
Glad to hear we might be making some progress 
Yes, that could be it. Downloading a forecast is done in the main thread, so its possible that a hanging API request could block the console and make it “freeze”. I do have timeouts set on the API requests at 20 seconds, but perhaps these are not working as expected. I will have a look into it. Could you perhaps send me the invalid API key (perhaps in a private message)? If it recreates the behaviour I can harden the code against it. Cheers!
Upgraded with no issues. Also wanted to say that I love the new solar/uv panel!
Great Job!
Just wanted to say i haven’t followed the thread for a few days but loved to see the update message in the lower right corner. Attention to detail is great. I thank you!
Maybe it is not really your code but depending on what size SD card Stevecody used, the log filles up.
I had this with an update once where I did some wrong code and the /var/log filled up and I ended with a frozen situation. I think it was daemen.log that blew up.
One thing I learned over time with PI, get logrotate running on most log files, once a day, retention of max 5 days or you end with problems sooner or later.
My freezing issue is resolved. I had placed an invalid API Key in the Darksky line in the ini file. Once I removed the key, the hanging issue stopped. It’s been running solid now since I fixed the ini.
This is great news! Also thanks for sending me the invalid key - I will have a look at see what the console was doing with it and why it was locking up.
An issue I noticed the Feeling Hot icon doesn’t match up with the temperatures I have set in the ini file.
I’m using F temperatures. Currently 65.8 here, feels like 65.8 and says “Feeling hot”.
I think this is working as expected. The temperatures in the .ini file are the maximum temperature for each category. So temperatures between 64 F (the maximum temperature for “Feeling Warm”) and 85 F (the maximum temperature for “Feeling Hot”) will be reported as “Feeling Hot”. So 65.8 F is correctly reporting “Feeling Hot”.
Temperatures > 95 F will report “Extremely hot” and all temperatures < 24 F will report “Extremely cold”.
Ohhh. I thought the temperatures in the ini were the min for when it reached a threshold. Ok. Thank you for the clarification.
But something is still off:-( My Temp is currently showing as 30.9C/87.7F and the text show ‘Feeling extremely hot’ ?! Not really 
OK, the default for VeryHot cutoff is 28C So in that case, it’s working as expected;-)
There is always going to be personal opinion when it comes to what is “really hot” and what is " extremely hot"! The default values are only my personal opinion, so that’s why they are adjustable in the settings
Right now, these are my thresholds:
Cold = 48
Mild = 65
Warm = 75
Hot = 85
VeryHot = 95
It is 67.8F and says “Feeling Hot”.
That’s not right! Have you just adjusted the cut-offs in the settings screen? It takes a new observation to arrive for the new cutoffs to be applied. If you restart the console, does it also read wrong?
The settings I listed have been in place for several days and multiple restarts. I did a restart as I type this and it came up correct. It says Feeling Warm now. I’ll monitor as the temperature goes up and down and see if it goes wrong again. I have had these settings for awhile and in the morning, when it’s cooler, it almost always still says Hot.
Definitely sounds like a bug - I will do some investigating. I have your station running on my test setup so hopefully will see the same behaviour. Is there any chance you can share your .ini file in a PM (once you have removed your private API keys)? That way we can be sure we are running using the same settings.
Peter, mine froze somewhere today
temp and wind are frozen, forecast ok, solar/ uv index is half frozen
clock is ticking normally
I wonder if isn’t again the lightning as we had a storm daytime and the panel shows last strike 1 minute ago and that was several hours ago.
I leave as is for tonight. Logs show nothing as usual 
I wait in case you want me to check something before I reboot.
I don’t work Thursday … will be near keyboard
Hmmmm, this freezing really is getting annoying! Did you start the console from a terminal or was it an auto-start? If you started it from a terminal, I assume there are no error messages that you can see?
