I don’t have an answer for your question directly as I don’t have the screen switched on all day. Do you actually want the screen on all day, or are you looking for ways to turn if off without powering down the Pi? If it’s the latter, have a look at this message for some suggestions: Announcements & Updates - #64
It should not be a problem. But iff you want, you can turn the display on & off as needed. The following two lines in the crontab power my display down over night 
pi@weatherpi:~ $ crontab -l | egrep -v ‘^#’
0 7 * * * export DISPLAY=:0.0; xset dpms force on; xset s noblank; xset s off; xset s -dpms >/dev/null 2>&1
30 23 * * * export DISPLAY=:0.0; xset dpms force off >/dev/null 2>&1
You can change the times as you need, of course or even run those commands via other triggers;-)
I just put together one of these and my screen turns off after a period of time. I can wake it up by pressing on the touchscreen. This seems to be the default behavior.
Yes, that’s the default behavior. The xset commands in my crontab lines change that Everybody can find the best setup for their own needs.
Yes, no problem, mine has been on for months. There is no burn in problems with any modern LED monitor.
Handled via PM. I’m not trying to hide my changes but since they are experimental, I’m not really advertising them either.
– Marco
Thanks for the info. I feel better knowing I won’t regret leaving it on all the time.
Is there the ability to pull forecast data from say Weather Underground or another site that provides API keys? I’m not currently getting Sager or Current Forecasts. everything else seems to be working ok.
Hi @brian.vargo, thanks for checking out the console! The plan is to pull data from WeatherFlow’s own forecast once they have finalised the details of the public API. They haven’t done so yet, but as soon as they have I will push out an update.
The Sager forecast should be working, however. Can you double check that your CheckWX API key has been copied to the wfpiconsole.ini file correctly? If so, can you let me know your station ID so I can investigate further?
Alright I got it up and running. Hardest part for me was trying to figure out how to assemble it and get the operating system installed. Once I did that, it was easy as pie to get the console going. My Sager forecast is not working either. I can’t figure out how to take a screenshot yet LOL so the pic is from my iPhone. I moved a few of the panels around through your settings menu. Tempest station #21612.
I decided to get a little creative and added a Raspberry Pi Camera Module to our Pi Console, then used Motion (GitHub - Motion-Project/motion: Motion, a software motion detector. Home page: https://motion-project.github.io/) to trigger the screen to wake up when someone walks by. Complete overkill, but I didn’t want the screen on all the time and didn’t want to have to tap the screen before glancing at it. 
3 Likes
with darksky api going away… does using https://openweathermap.org/ help fill in the gaps?
Glad you managed to get up and running 
. I’ve just tested your station, and the Sager Forecast is working fine for me. Are you sure you pressed the Sager button in the bottom left? The “Current Forecast” screen is different to the Sager Forecast, and isn’t working because of problem with DarkSky. I am just waiting for WF to finalise their own forecast API, and then I will be switching to that.
1 Like
Hi @idaband, my plan is to incorporate the forecast direct from WeatherFlow (the same one as in the Tempest app). They are still finalising the details of the API, however, but as soon as they are ready I will update the console.
Yes, I know the darksky isn’t working, but when I click on Sager, it says METAR currently unavailable or something to that effect. I must have entered something incorrectly?
Hmmm, interesting. Double check that you copied your CheckWX API key into the wfpiconsole.ini file correctly. If there is an error there that would stop the console from downloading the METAR information.
and triple check for an eventual space before or after the key
1 Like
The cheaper way would probably be the integration of an PIR sensor (something well known from all the Halloween props or from motion-activated light switches;-) That would trigger a GPIO pin when it detects motion and then the RasPI can decide, how long the display should stay on.
1 Like
Definitely! I might do that for one I’m throwing together for my office elsewhere in the house. The touchscreen case I’m using in the kitchen had a spot for the camera module, so it’s doubling as a security camera. 
1 Like