I kinda got it working… until it didn’t. All was going fine till the 5. Download the PiConsole:
got a bunch of syntax type errors. I understood what you were trying to do and broke out the commands
separately, and got it downloaded and extracted. Got past the setup questions for my unit. Then all went fine till it tried to obtain a socket…
(kivy_venv) C:\Users\tomc>cd wfpiconsole
(kivy_venv) C:\Users\tomc\wfpiconsole>python main.py
[INFO ] [Logger ] Record log in C:\Users\tomc.kivy\logs\kivy_21-02-28_6.txt
[INFO ] [deps ] Successfully imported “kivy_deps.glew” 0.3.0
[INFO ] [deps ] Successfully imported “kivy_deps.sdl2” 0.3.1
[INFO ] [Kivy ] v1.11.1
[INFO ] [Kivy ] Installed at “C:\Users\tomc\miniconda3\envs\kivy_venv\lib\site-packages\kivy_init_.py”
[INFO ] [Python ] v3.7.10 (default, Feb 26 2021, 13:06:18) [MSC v.1916 64 bit (AMD64)]
[INFO ] [Python ] Interpreter at “C:\Users\tomc\miniconda3\envs\kivy_venv\python.exe”
[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
[INFO ] [GL ] Using the “OpenGL” graphics system
[INFO ] [GL ] GLEW initialization succeeded
[INFO ] [GL ] Backend used
[INFO ] [GL ] OpenGL version <b’4.0.0 - Build 10.18.10.4252’>
[INFO ] [GL ] OpenGL vendor <b’Intel’>
[INFO ] [GL ] OpenGL renderer <b’Intel(R) HD Graphics 2500’>
[INFO ] [GL ] OpenGL parsed version: 4, 0
[INFO ] [GL ] Shading version <b’4.00 - Build 10.18.10.4252’>
[INFO ] [GL ] Texture max size <16384>
[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
2021-02-28 13:17:44-0500 [-] Log opened.
2021-02-28 13:17:44-0500 [-] Starting factory <main.WeatherFlowClientFactory object at 0x00000219382C5048>
[INFO ] [Base ] Start application main loop
[INFO ] [Support ] Starting twisted reactor
[INFO ] [GL ] NPOT texture support is available
2021-02-28 13:18:04-0500 [-] dropping connection to peer tcp4:34.202.254.239:443 with abort=True: WebSocket opening handshake timeout (peer did not finish the opening handshake in time)
2021-02-28 13:18:09-0500 [-] Websocket connection closed
2021-02-28 13:18:09-0500 [-] Websocket connection retrying
2021-02-28 13:18:09-0500 [-] <twisted.internet.tcp.Connector instance at 0x219382c5248 disconnected IPv4Address(type=‘TCP’, host=‘ws.weatherflow.com’, port=443)> will retry in 5 seconds
2021-02-28 13:18:09-0500 [-] Stopping factory <main.WeatherFlowClientFactory object at 0x00000219382C5048>
2021-02-28 13:18:17-0500 [-] Starting factory <main.WeatherFlowClientFactory object at 0x00000219382C5048>
Opps - that was a code formatting error. Different lines were running into each other. I have fixed it in the original post.
The socket issue is different though. Is you internet working OK otherwise, as I don’t see the same issue on my Windows 10 machine using the instructions I gave above?
I wanted to confirm, so as NOT overlooking something that may be a point of confusion. I Found and installed Miniconda from a download I had found on my PC - Miniconda3-latest-Windows-x86_64. didn’t know what version it was/is so from command line …
were all those instructions for version 3.8 ?
EDIT: Nevermind – I went back and uninstalled 3.7 - installed a fresh download of 3.8 – went through the installation again, and it does the same thing.
EDIT: not sure if it matters but this is the build info of Windows 10 Pro - is/was suppose to be 20H
I really don’t know what is going on here. I wiped miniconda off my machine completely, installed a fresh download of 3.8, went through the installation and everything is working fine. The conda version is 4.9.2 and the Python version is 3.7.10
If you are happy too, can you share the Personal Access Token you are using (or generate a new one that you can then delete). I can test that my end and see if somehow it is station specific
Peter, thanks for the guide. I gathered the supplies and downloaded PiConsole, set it up and just that easy I have my dedicated display in the family room.
Previously my Tempest was communicating and updating Pi Console data perfectly. Then, I had to replace my Tempest due to failure (Hub not changed). After updating the Pi Console station ID per the new Tempest, and re-booting the Pi Console, I still have no updates received by the console and the Tempest shows as offline??? Note that the tempest data is being updated when viewed on the IOS App and also via WEB access. Any thoughts? Station ID 21593
I used the “Replace” feature of the iOS App when I swapped the Tempest and the weather data is reported correctly both to the iOS APP and via the WEB reporting so I know the HUB is communicating with the Tempest and with the internet.
For the Raspberry Pi Console, I did update the Tempest Device ID via settings to the new “72102” and confirmed that the station ID had not changed.
The Raspberry PI Console is connected to the internet as I do receive forecast updates.
I don’t think I need to do any API or Token updates.
BTW, I did upgrade the WeatherFlow PI console to the latest version 4.0.4 and Re-booted.
Can you first delete the entire wfpiconsole.ini file. Then restart the console with wfpiconsole start and enter the correct station and device id’s. If it doesn’t work, can you share the logs that are printed to the terminal?
Ok, I deleted the wfpiconsole.ini, restarted wfpiconsole, entered the station and device ID’s, and the original API and Token data. Then I printed out the .ini file and verified correct entries.
I rebooted wfpiconsole and still no data reported.
I’m not sure of which error log you are referring. Is it the error log requested under the wfpiconsole directory or requested under the raspberry pi directory?
I’m thinking to start over from scratch with the whole wfpi install.
As Eric said, the wfpiconsole.log file is in the same directory as all the other files: ~/wfpiconsole/. If you open a terminal manually and run wfpiconsole start, you will also see the same logs printed to the screen. If the PiConsole is already running (i.e. you have it set to autostart on reboot), run wfpiconsole stop first
Thanks for ypu responses. I ended up reinstalling the Raspberry OS and then the wfpiconsole. Now everything is working. I wonder if there were some remnants of the old Tempest ID somewhere??
I wouldn’t think it is corrupt, rather a permission error. Maybe during upgrade something changed (go figure). Depending on where you installed wfpiconsole it will run as user ‘pi’ or as ‘root’ and accordingly the files must be readable by that user.
Can you for exemple go in the directory and do a ls -la (this way you see who is ‘owner’ and ‘group’ + the permission to read/write files.
If you installed under the /home/user/… directory you should see group and owner as the user ‘pi’. Below extract of mine. You see I’m logged in the raspberry as pi which is the usual user running the scripts and then you see a few lines of those icons
Those rw r etc are read and or read/write options
pi@WFconsole:~/wfpiconsole/icons/barometer/icons_hR $ ls -la
total 4080
drwxr-xr-x 2 pi pi 36864 févr. 17 09:48 .
drwxr-xr-x 4 pi pi 36864 févr. 17 09:48 ..
-rw-r--r-- 1 pi pi 1902 févr. 17 09:48 1000.0.png
-rw-r--r-- 1 pi pi 1886 févr. 17 09:48 1000.1.png
-rw-r--r-- 1 pi pi 1898 févr. 17 09:48 1000.2.png
-rw-r--r-- 1 pi pi 1879 févr. 17 09:48 1000.3.png
-rw-r--r-- 1 pi pi 1887 févr. 17 09:48 1000.4.png
-rw-r--r-- 1 pi pi 1881 févr. 17 09:48 1000.5.png
you can change those if needed by chmod and if not the correct user via chown and chgrp
@eric gave a very detailed answer, but the solution is actually a lot simpler (sorry Eric!). The barometer on the Pi cannot display pressures above 1050 mb or 31.01 inHg, so the icon files are missing. Your station recently reached a maximum pressure of 31.189 inHg, maxing out the barometer and causing the errors you see above. I have never seen such a high pressure, so never spotted this bug. I will get a fix in place.
