Nope, it’s a new font . I spent ages trying to find one that was similar to the old one, but that was also better for display on small screen. This is what I settled on: Inter font family
It looks good! Unfortunately the squashing is hard to deal with. Although the console can be resized to whatever shape you want, it is still fundamentally designed for a 800x480 resolution/aspect ratio. If you try and resize it such that the aspect ratio is changed to dramatically (in your case it has been stretched vertically with no increase in the width), then you can get these artefacts that you are seeing (like the Sunrise and Sunset labels overflowing).
I thought about fixing the aspect ratio to stop this from happening (a black border would be used to pad the display), but I decided against this in the end.
Peter
I know nothing about programming other than basic which I learnt in 1977 and I basically learn as I go
Python is completely new to me so I know nothing about Kivy or anything else, but it all seems easy enough to modify once I figure out where to add the bits I want to change
As I did with the Sager update (which took a while to find)
I’m getting an si7021 temp and humidity sensor on Tuesday and I’m going to add it to my Pi 4
Can you tell me the files I need to modify to get the sensor read at regular intervals and get the results displayed on the screen?
I should be able to figure out how to do it once I know which files I need to play with
I did the update a few days ago and it ran fine until tonight where my Forecast tab now says “Forecast currently unavailable…” Not the Sager forecast, the new forecast from the update.
I have V4 running for a few now and it seems all stable on a good old pi3 with the standard 7" screen. Just had a closer look and I (finally ) found something to say . It’s cosmetic and can for sure wait a next iteration. And maybe to be confirmed by others since other screenshots don’t show it here.
Good spot! This seems to be very screen specific. I saw it once or twice during testing, and fixed it on my screens, but clearly that wasn’t enough. I know how to fix it though, so I will sort it for the next version
Are you still seeing this? It usually happens because the API call is failing which is often down to some temporary glitch. If it is still failing I will look into it further
Hi @lewtesco , there is some useful information on what you need to do in this post: Announcements & Updates - #1058. The line numbers I refer to might have changed slightly, but you should find the line I am referring to nearby.
Essentially you need to start by writing a new function that gets and returns the temperature and humidity from your si7021. Exactly how you do this will depend on the hardware, but the key thing is that the function should be non-blocking. Don’t use any sleep statements or anything similar. Once you have that function you should use clock.schedule_interval to call it at set intervals, and then you need to assign the output to the inTempObs property.
In the post above I have referenced several functions already written for the console that use a very similar process to what you need to implement. You will find their source code in the lib directory. Hope this helps!
This might seem a stupid question to most of you but it’s been puzzling me
Why is the forecast button labelled “Sager”?
I know it’s an algorithm for weather forecasts but why label the button Sager?
Wouldn’t Forecast and then Current be more realistic names for the buttons?
Like I said it’s probably a stupid question but I had to look up what Sager actually was
OK, I had look into this and I can see what the problem is. Essentially the precip_type field in the next hourly forecast is not always present, and this is causing the forecast to fail. I guess this is a hazard of using an undocumented API! I will get a fix in place, but in the meantime it will continue to fail until that field is present again in the next hourly forecast (which should be in a few hours looking at the raw API data)
Definitely not a stupid question. I guess when I designed this I wanted to differentiate between the WeatherFlow forecast (or back when I designed it the UK MetOffice or DarkSky forecast) and the Sager Weathercaster forecast. Obviously “WeatherFlow forecast” and “Sager Weathercaster forecast” are too long to be the button labels, so instead I settled on “Forecast” and “Sager”. I can appreciate the confusion if you have not heard of the Sager algorithm.
I would like to avoid using a “Current” label though. Ultimately both are forecasts, and I don’t want users to confuse the forecast panels with the actual data that their station is currently reading.
I was able to get my Mini 8" (non-touch)HDMI monitor to work with my rpi4B. I will be using that image I created once I receive a new rpi4 (2gig) I ordered. Don’t want to waste my 4gig rpi4B where it’s not needed.
Followed the instructions from scratch for installing on an rpi4. The aspect ratio is MUCH better. I think I can still see a slight squashing in the Wind circle image, but that’s about it. As close to PERFECT as I hope to get.
I am not sure if this a piconsole problem or a vnc problem. I am running pi on a laptop and everything is fine there. The odd behavior comes in when I try to remote in. I have teamviewer and tightvnc running on there. If the console is displayed on the screen, as soon as I remote in with teamviewer, it shuts down. It will also do that if I reopen it while remoted in and leave remote session.
Then, this one concerns me more, is I am trying to get the display onto a Galaxy2 tablet. I am able to get in with the tightvnc, but get an error when trying to open wfpiconsole. Not sure even if this is a feasible thing to do? This is my error I get:
[e[1;32mINFOe[0m ] [Logger ] Record log in /home/pi/.kivy/logs/kivy_20-10-24_13.txt
[e[1;32mINFOe[0m ] [Kivy ] v1.11.1
[e[1;32mINFOe[0m ] [Kivy ] Installed at “/home/pi/.local/lib/python3.7/site-packages/kivy/init.py”
[e[1;32mINFOe[0m ] [Python ] v3.7.3 (default, Jul 25 2020, 13:03:44)
[GCC 8.3.0]
[e[1;32mINFOe[0m ] [Python ] Interpreter at “/usr/bin/python3”
[e[1;32mINFOe[0m ] [Factory ] 184 symbols loaded
[e[1;32mINFOe[0m ] [Image ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[e[1;32mINFOe[0m ] [Window ] Provider: sdl2([‘window_egl_rpi’] ignored)
Xlib: extension “RANDR” missing on display “:1.0”.
[e[1;31mCRITICALe[0m] [Window ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - RuntimeError: b’GLX is not supported’
File “/home/pi/.local/lib/python3.7/site-packages/kivy/core/init.py”, line 71, in core_select_lib
cls = cls()
File “/home/pi/.local/lib/python3.7/site-packages/kivy/core/window/window_sdl2.py”, line 152, in init
super(WindowSDL, self).init()
File “/home/pi/.local/lib/python3.7/site-packages/kivy/core/window/init.py”, line 981, in init
self.create_window()
File “/home/pi/.local/lib/python3.7/site-packages/kivy/core/window/window_sdl2.py”, line 290, in create_window
self.get_gl_backend_name())
File “kivy/core/window/_window_sdl2.pyx”, line 224, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window
File “kivy/core/window/_window_sdl2.pyx”, line 74, in kivy.core.window._window_sdl2._WindowSDL2Storage.die
[e[1;32mINFOe[0m ] [Text ] Provider: sdl2
2020-10-24 18:02:01-0500 [-] Log opened.
[e[1;31mCRITICALe[0m] [App ] Unable to get a Window, abort.
This should definitely be possible, and it works for me on my Android smartphone. I use RealVNC instead of tightvnc, however. I’m not sure exactly how you are creating the remote connection, but whenever I have seen this error before it is because a user is initially using an SSH connection to connect to the remote machine, and then starting the VNC connection from within that SSH session. Instead the remote connection should be entirely managed with the VNC software. There is some Raspberry Pi documentation that explains how it should be done: Raspberry Pi Documentation - Remote access
I am not sure or if it makes a difference, but I am unable to install realvnc, that is why I installed the tightvnc. I get an error
sudo apt-get install realvnc-vnc-server realvnc-viewer
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package realvnc-vnc-server
E: Unable to locate package realvnc-viewer
I know I am asking alot from you, but I am lost when it comes to this stuff, kind of
Is it not already installed on Raspberry Pi OS? Certainly whenever I have setup a new Raspberry Pi it already is. I’m not sure if this is true when running Raspberry Pi OS on a laptop/PC though. It is possible to download it directly from here: https://www.realvnc.com/en/connect/download/vnc/linux/ (I assume you will need the Linux version as you are not using Raspberry Pi hardware)
. I spent ages trying to find one that was similar to the old one, but that was also better for display on small screen. This is what I settled on: Inter font family
) found something to say . It’s cosmetic and can for sure wait a next iteration. And maybe to be confirmed by others since other screenshots don’t show it here.
