Forecast background bug should be fixed now. You’ll just need to re-download the latest release when you get the chance.
I have also edited the the post you pointed too, to account for the change from Py to Pi. Thanks for spotting this!
Forecast background bug should be fixed now. You’ll just need to re-download the latest release when you get the chance.
I have also edited the the post you pointed too, to account for the change from Py to Pi. Thanks for spotting this!
New Release …
Peter;
I installed and it’s up and running fine! The only thing I changed was the Date/Time format to more reflect what I’m used to using
and I commented out your original format
# self.Screen['Clock'] = datetime.now(Tz).strftime("%a, %d %b %Y\n%H:%M:%S") self.Screen['Clock'] = datetime.now(Tz).strftime("%a, %b %d,%Y\n%I:%M:%S %p")
EDIT: I did notice one thing … the Rainfall section still reflects “mm” instead of “inches” hopefully that’s on your to-do-list?
however I did run into another issue (maybe?) I built a new SD card from scratch with a virgin raspain download. Followed the install instructions again and I’m continuing to get this error when attempting to launch:
I built this on a Rpi2 without the 7" touchscreen installed - at the time? perhaps that has something to do with why I’m getting the error? The problem doesn’t seem to have anything to do with your coding - more with the required dependencies ?? and kivy install…
hoping you can help - I wanted to build a new SDcard img on an 8gig card - my current working install is on a 16gig - which is more than I think I need; and it saves space when I image backups.
Again THANKS again for a Great job looks really good!
Interesting! Try running the console with this command:
KIVY_GL_BACKEND=gl python3 main.py
It looks like the setup you have at the moment is using the ‘sdl2’ backend rather than the ‘gl’ backend. If I force my setup to use the ‘sdl2’ backend I get the same segmentation fault.
That seems to work! ?? I’m not positive as I’m running it back on a standard HDMI monitor - and it is running, but of course everything is out of place but it is working.
Glad to hear it is working! Keep running with that command for the time being, and I’ll add some code to the next update that will force the console to use the ‘gl’ backend.
Hi @peter ,
my console (updated to v1.0) gives the follow error:
2018-10-06 19:32:07+0200 [-] Starting factory <main.WeatherFlowClientFactory object at 0x70811670>
[ERROR ] [Image ] Error reading file Icons/Barometer/864.4.png
…the arrow is missing on the barometer graphic
Probably the console reads for the graphic the absolute instead the relative barometric pressure
Peter;
Thanks! – because I’m retired and have NOTHING better to do… I started playing around with the WeatherFlowPiConsole.kv file. I was able to hack/fix the scaling of the background image and location of the MetOffice.png image that was out of place. Now it appears properly - however on a 32" Sony TV monitor (scaled in the bottom left corner of the desktop) pretty neat!
Life used to be so simple. We all had a black telephone.
Good spot! That’s exactly what it was doing. It took a station of your elevation to force the error though! I have just created a new release so if you update again the problem should be solved.
Also watch this space re. the wind units - I promise it is coming soon
@tcichowicz The new release also has a fix for your backend issue. You should be able to update and then just run the console with: python3 main.py
. It will now automatically force the console to use the ‘gl’ backend.
Also nice work getting it to scale on the large screen! How did you manage it? What sort of changes did you make to the .kv file?
well I modified the ‘size’ 800,480
:
name: “CurrentConditions”
orientation: “vertical”
canvas.before:
Rectangle:
size: (800,480)
source: “Background/my_piconsole_background2.png”
relocated the position of MetOffice.png because it was off the background image (way above ?)
also - instead of using my 32" Sony TV as a monitor - I had an old laptop LCD panel that I converted to VGA/HDMI - and changed the resolution of the pi to 800x600 –
Because I had a black empty space at the top - I relocated the ‘clock’ and format/size an put it on top. I also added a credit at the bottom as my laptop screen is NOT touch and couldn’t trigger the credit pop-up.
Thanks for the ‘gl’ backend fix -I’ll give it a try… hoping you can convert ‘Rain’ units to inches at some point too.
EDIT: I can confirm that the ‘gl’ backend issue is fixed on my install THANKS! Oh yeah I forgot to mention that I tweeked a few of the fonts both in size and “not” Thin – they were falling apart on the lower resolution, and the veiwing angle of the old laptop LCD is pretty poor.
Here's my latest ....
Fantastic work. That looks great
Thanks … I’ve attached a link to a zip file that contains the files I’ve changed to make this work.
For anyone interested.... Have FUN!
Looks great! Thanks for sharing your changes as well .
there is still a little typo on your GitHub page, there is Y instead an i in last command
If the console boots and everything is working, stop the console and set the service to start automatically at reboot
sudo systemctl stop WeatherFlowPiConsole.service
sudo systemctl enable WeatherFlowPyConsole.service
@peter
The old bug was resolved, but…
I have found another bug in v1.0 and 1.1:
the high barometer value change after a few minutes to 1229.7
…and after several minutes also the low value to 1229.7
Is the displayed high barometer value not too high on your screen?
@patrick.mussner Gaaaah! That’s the effect of leaving debugging code in the software. It is a simple fix that I’ll push out with the next release, but in the meantime you can fix it by simply changing line 764 in v1.1 of main.py from
Pres = [1050,'mb']
to
Pres = [self.Air['Obs'][1],'mb']
@eric Thanks for spotting the typo. All updated.
applied the fix today, it was running for near 24 inside the network without problems
I’ll let run for a fe days now, see if the time out is solved
I have do it. Bug solved, thanks Peter
6 days later, not a single reboot and … still happy. Guess you can say the socket problem is nailed/solved