If you want to go from v2.15 to v2.16 then you’ll need to use the full install command curl -sSL https://peted-davis.github.io/wfpiconsole | bash. If you lose access to the wfpiconsole directory after the update you’ll need to run sudo chown -fR pi wfpiconsole and sudo chgrp -fR pi wfpiconsole
If you are happy to wait for v3.0 which is a few days away, then wfpiconsole update should be used, and the ownership bug should be fixed. wfpiconsole update will also be used for all future releases.
Are there directions somewhere for what we need to tweak if our display doesn’t match the 800x480 resolution that wfpiconsole likes? My raspberry says the only resolutions available are 1920x1080, 1024x720, and 640x480.
@chris.king What type of screen do you have attached to your Pi? Is it the official 7inch touchscreen, or is it something larger? For the touchscreen you shouldn’t have to adjust anything - just leave the resolution settings on their default option.
You could try setting a custom resolution in /boot/config.txt.
Open a terminal and type sudo nano /boot/config.txt. Find the line hdmi_group=.... and set it to hdmi_group=2. Make sure hdmi_mode=... is is set to hdmi_mode=87 and then add this line: hdmi_cvt 800 480 60 0 0 0 0. Save the file by pressing ctrl-x, followed by y to save and then enter.
NOTE: I haven’t tested this, and there is a chance that it could mess the display up completely. If this happens you will need to pull out the SD card, plug it into a working computer and edit the config.txt file back to it’s default. Or you will need to re-flash the SD card completely. Please be aware of this.
Shouldn’t I be able to ssh into the pi and be able reset the file if things go sideways?
Nevermind, that worked perfectly and the display looks wonderful! Thanks!
Okay, this a bit odd. The lower left Sun | Moon panel is showing that it’s 19 hours and 4 minutes until Sunrise, despite it being 11:35 in the morning, the sunrise/sunset times seem to be accurate however. I don’t think Southern California has technically ever had a night that lasted over 19 hours.
Hmmmm - that’s a bit weird! I have tested your station here and it seems to work perfectly OK for me. I don’t think it matters what timezone the Pi is set to, as the timezone is taken from the config file. Have you just switched to daylight saving time perhaps? Can you stop and restart the console to see if that fixes it?
PS - you can also update to Version 3 using wfpiconsole update
I took eric’s suggestion and updated time region and then rebooted. Everything looked good at that point though apparently my post to that effect didn’t go through.
Peter, Thanks for updating to include Indoor temp. I ran the wfpiconsole update, and it got to updating WeatherFlow PiConsole to \e{1;32mv3.0\e{0m, then showed “Error: Unable to install WeatherFlow PiConsole”.
Updated to 3.0 and the update went normally. When I start the console it reads the data and fills in the info but it doesn’t update after that. Also not reading the indoor Air unit but I figure that is because it needs some time to read the data for that and since it’s not updating it never gets that info. The clock is working and the sunrise/sunset is also changing as it should.
I believe I know the problem. The Pi is connecting to the 5G network and since the hubs use the 2.4G side it can’t read the UDP packets. What threw me that it does read data when first started.
Both use the same SSID and not sure why the Pi is suddenly deciding to connect to the 5G side of things where it never has before. I’ll have to investigate further when I get a chance.
