I did not (I was in a rush!). Let me check tomorrow and I’ll let you know. Sorry the update has caused issues - I feel your frustration!
1 Like
Clean installed buster, enabled ssh, enabled VNC and have the same error…
[CRITICAL] [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’Could not initialize EGL’
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
[CRITICAL] [App ] Unable to get a Window, abort.
OK, that’s not what I was expecting!
How exactly are you connecting via VNC? Do you first start an SSH session and then start the VNC connection from within that session? If so, others have seen the same error as you when following this route. Instead, try using VNC without the SSH connection at all.
Assuming VNC is enabled on the Pi (run sudo raspi-config , navigate to Interfacing Options → VNC and select Yes ), and that you have downloaded Real VNC Viewer on your PC/laptop (https://www.realvnc.com/en/connect/download/viewer/), you should be able to use VNC Viewer to connect directly to the IP address of the Pi. This is how I do it and I don’t see any errors.
Here are some step-by-step instructions from the Raspberry Pi documentation: Raspberry Pi Documentation - Remote access
I’ve just run these steps and I also don’t see any problems. Sorry!
1 Like
updated mine, kivy took ages to update python but it finally did. At reboot needed to give again my access token and running again. Will keep an eye on how it goes over time
@Peter, Thanks for the great updates!
I’m running into a quirk on my rpi4 with the official touchscreen. I have the console set to autostart, but it isn’t coming up after a reboot. The service shows as active and I see it in the process list, but nothing on screen. If I launch it manually or run a service wfpiconsole restart it does come up fine. I’m not seeing anything of interest in the logs. I’ve tried starting out with a new configuration file and disabled/enabled autostart, so I’m not sure what else to try.
I should also note I’m doing this at the console, not over ssh or vnc.
1 Like
Peter, I’m loving the new forecast! Thanks for getting the daily High and Low temps on there, along with the other info.
I’m also enjoying adding my mods every time. lol. It’s making me try to learn a little python so I can use include statements, etc. I’ve gotten the process down to about 15 minutes.
Anyway, I think my version of your console looks awesome. 
I’d like to make everyone else a little jealous.
The picture in the corner is an animated gif of the most recent 30 mins or so.
2 Likes
If I try and start within a remote SSH session then I get the same “Unable to get a Window, abort” error. If I launch from within an interactive VNC session it works fine.
1 Like
Hi @wxkeith, interesting - I see the same thing on my Pi4. I didn’t think to test this. It looks like the autostart doesn’t like the Fullscreen settings. I will look into this.
As a work around, open the wfpiconsole.ini and set the Fullscreen field under [Display] to 0, and the Border key to 0. Also make sure you have followed these instructions for the Pi 4. You should then be able to reboot and it should show as expected
1 Like
Cool - good to hear you’re running with no problems. I added some code to the update script to make sure everyone was running the same version of Kivy. Yours probably needed updating which is why it took such a long time. I promise you won’t need to enter your Token again
1 Like
That did the trick, thanks!
1 Like
I cannot get the autostart to work, I’m using a Pi 4, and touchscreen
I tried all the suggestions a few steps up and it just will not autostart
It’s not a huge problem it would just be nice if it did 
I’ve got the Weatherflow Air and Sky, and as I live in the UK the chances of me finding another Air unit to use indoors is pretty slim
Has anyone managed to incorporate the DS18B20 temp sensor?
What are the two units you’re thinking of using for the indoors sensor if you don’t mind me asking
A suggestion, I have an Enviro + Air Quality and also the PMS5003 Particulate Matter Sensor with Cable both from Pimeroni
Has anyone used this module successfully to get the indoor temp?
And is willing to share the code and knowledge to get it working
I know the bme self heats but it should be easy to compensate
And the particulate matter readings would be a great addition to the PiConsole as a lot of people are interested in air quality now
Even if it’s a secondary screen with not a huge amount of info
My Station keeps disconnecting from the servers. I have weewx running on a pi4 on the same network and would like to get the data from there. Has anyone been working on a version that could get the pi console data from weewx, via MQTT or other means?
Sorry you’re having problems. I’m looking into it at the moment, but it’s odd that the workaround I provided above isn’t working.
Can you reboot your Pi with autostart enabled. Once it has rebooted open a terminal and run sudo systemctl status wfpiconsole.service. Can you let me know what you see. Also run more ~/wfpiconsole/wfpiconsole.log and let me know what you see
Peter, I had the same problem Implemented your work around. It works great now. Thanks.
Peter
Sorry I should have said it does work but there is a taskbar at the top showing grey with wfpiconsole on it
before autostart there was no taskbar as I did follow your instructions for hiding it
systemctl status wfpiconsole.service gives
wfpiconsole.log shows
[INFO ] [Logger ] Record log in /home/pi/.kivy/logs/kivy_20-10-22_7.txt
[INFO ] [Kivy ] v1.11.1
[INFO ] [Kivy ] Installed at "/home/pi/.local/lib/python3.7/site-packages/kivy/__init__.py"
[INFO ] [Python ] v3.7.3 (default, Jul 25 2020, 13:03:44)
[GCC 8.3.0]
[INFO ] [Python ] Interpreter at "/usr/bin/python3"
[INFO ] [Factory ] 184 symbols loaded
[INFO ] [Image ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[INFO ] [Window ] Provider: sdl2(['window_egl_rpi'] ignored)
[INFO ] [GL ] Using the "OpenGL ES 2" graphics system
[INFO ] [GL ] Backend used <sdl2>
[INFO ] [GL ] OpenGL version <b'2.1 Mesa 19.3.2'>
[INFO ] [GL ] OpenGL vendor <b'Broadcom'>
[INFO ] [GL ] OpenGL renderer <b'V3D 4.2'>
[INFO ] [GL ] OpenGL parsed version: 2, 1
[INFO ] [GL ] Shading version <b'1.20'>
[INFO ] [GL ] Texture max size <4096>
[INFO ] [GL ] Texture max units <16>
[INFO ] [Window ] auto add sdl2 input provider
[INFO ] [Window ] virtual keyboard not allowed, single mode, not docked
[INFO ] [Text ] Provider: sdl2
2020-10-22 18:44:13+0100 [-] Log opened.
2020-10-22 18:44:14+0100 [-] Starting factory <__main__.WeatherFlowClientFactory object at 0xacd8e2b0>
[INFO ] [ProbeSysfs ] device match: /dev/input/event0
[INFO ] [MTD ] Read event from </dev/input/event0>
[INFO ] [ProbeSysfs ] device match: /dev/input/event0
[INFO ] [HIDInput ] Read event from </dev/input/event0>
[INFO ] [Base ] Start application main loop
[INFO ] [MTD ] </dev/input/event0> range position X is 0 - 799
[INFO ] [MTD ] </dev/input/event0> range position Y is 0 - 479
[INFO ] [MTD ] </dev/input/event0> range touch major is 0 - 0
[INFO ] [MTD ] </dev/input/event0> range touch minor is 0 - 0
[INFO ] [MTD ] </dev/input/event0> range pressure is 0 - 255
[INFO ] [MTD ] </dev/input/event0> axes invertion: X is 0, Y is 0
[INFO ] [MTD ] </dev/input/event0> rotation set to 0
[INFO ] [Support ] Starting twisted reactor
[INFO ] [HIDMotionEvent] using <raspberrypi-ts >
[INFO ] [HIDMotionEvent] <raspberrypi-ts > range ABS X position is 0 - 799
[INFO ] [HIDMotionEvent] <raspberrypi-ts > range ABS Y position is 0 - 479
[INFO ] [HIDMotionEvent] <raspberrypi-ts > range position X is 0 - 799
[INFO ] [HIDMotionEvent] <raspberrypi-ts > range position Y is 0 - 479
[INFO ] [GL ] NPOT texture support is available
2020-10-22 18:44:15+0100 [-] Websocket connection retrying
2020-10-22 18:44:15+0100 [-] <twisted.internet.tcp.Connector instance at 0xacd8e370 disconnected IPv4Address(type='TCP', host='ws.weatherflow.com', port=443)> will retry in 5 seconds
2020-10-22 18:44:15+0100 [-] Stopping factory <__main__.WeatherFlowClientFactory object at 0xacd8e2b0>
2020-10-22 18:44:20+0100 [-] Starting factory <__main__.WeatherFlowClientFactory object at 0xacd8e2b0>
2020-10-22 18:44:30+0100 [-] Websocket connection retrying
2020-10-22 18:44:30+0100 [-] <twisted.internet.tcp.Connector instance at 0xacd8e370 disconnected IPv4Address(type='TCP', host='ws.weatherflow.com', port=443)> will retry in 25 seconds
2020-10-22 18:44:30+0100 [-] Stopping factory <__main__.WeatherFlowClientFactory object at 0xacd8e2b0>
2020-10-22 18:44:55+0100 [-] Starting factory <__main__.WeatherFlowClientFactory object at 0xacd8e2b0>
2020-10-22 18:44:56+0100 [-] Websocket connection open
Ah I see! Did you follow the instructions in this post and set the Border key to 0 in wfpiconsole.ini?
I am trying to do the update on my Raspi for laptop. When I enter the command ``wfpiconsole update``` , I get an error of command not found. I tried going to directory and tried using sudo command. Am I missing a step? Thanks
Hi Peter
Yes I did follow them exactly
OK, understood. I was working on the autostart yesterday and I think I can recreate what you are seeing. I’ll try and get a bug fix pushed out in the next few days. By the way, what screen are you using? Is it the official 7 inch touchscreen, or something different?
Hi @fritz614, nope you’re not missing a step. The issue is that because you had to do a manual install on your laptop, the wfpiconsole command is missing. This command is installed when you use the automated one-line installer. As the one-line installer is now compatible with Raspberry Pi OS running on a laptop, all you need to do is “install” the console by running:
curl -sSL https://peted-davis.github.io/wfpiconsole | bash
As you actually have it already installed, it will skip a lot of the steps, but at the end it should update you to the latest version and also ensure the wfpiconsole command is installed.
I think you are going to be the first person (apart from me) to try the one-line installer on anything other than a Raspberry Pi so please let me know how you get on and whether you run into any issues. I tested it pretty extensively, but there is always a chance that there is a bug in the code that I missed.