system
March 5, 2023, 12:12pm
1
Discussions about the PWS Dashboard template.
Some of the old pinned topics
Yes, the names look similar but there is a big difference between two “historical-data” sets which are used in PWS_Dashboard.
The reason: We have two different needs for historical data.
We want to make graphs of our weather-data. Those graphs should show todays values, a month, a year a.s.o.
The data used by graphs can not be “realtime” as it is often calculated with a low frequency by the data-provider.
We want to have the high-lows of our weather-data but those should be as “real-time”…
Sometimes this occurs:
You invested your precious time in changing a block to better fit your needs. But after a routine PWS_updates job your enhanced script is replaced with the dull original without even a warning.
Rule 1: Always change the first line of a block you modify. Line 1 normally reads:
<?php $scrpt_vrsn_dt = ‘One_normal_block.php|01|2021-05-14|’;
Change that version number |01| to |09| and the PWS_updates script will warn you that your version is not a standard version.
Now …
Following extra products are available to expand/ enhance your “standard” PWS_Dashboard.
Those add-ons are not included in the full download and are not “automatically” updated with the standard scripts.
[li]WH45 CO2 sensor blocks/popup as developed by @olicat
=> more info here [/li]
[li]Forecast pop-ups including an all value graph
=> more info here [/li]
[li]Extensive banner / sticker script as developed by @lacasettabio
=> more info here [/li]
[li]Very simple 1 page dashboard alternati…
In this topic we should try to move the more common problems encountered when installing the PWS_Dashboard
Starting with the January 11 download there is a small test-script which is excuted the first time the fresh download is started.
It will do a few checks, such as “CURL” installed, and if all OK one can click to go to easyweathersetup.
Checks for other problem situations will be added to catch them with this test script
check 1 : $_SERVER["DOCUMENT_ROOT"]: result = OK, server = xyz.c…
Read more: https://en.wikipedia.org/wiki/KISS_principle
I was trying to find a solution for “to much information and rubbish in a far to small space”
The PWS_Dashboard is not always easy readable, even with the &KISS and &round option switched on.
And, on the other hand, I am to old to read the small print of a decent console also.
They cram to much sensors, different colours, graphs in a 7" screen
I just got a WH2320-console from the kids to add to my working area so I can read the weathe…
Based on this user request:
User has a fine weather-station which is not expandable.
Want to use extra sensors AirQuality, lightning, soil without buying a complete new station and scrapping the old one…
Wants to add an “inexpensive” GW1000/DP1500 with only the AirQuality-sensor and / or a lightning sensor.
And then those new sensors should be merged with the current upload.
First solution: Some weather-programs (MB, WD) support this
=> then for use with the PWS_Dashboard: extra-sensor …
@ALL
The current 2012_lts dashboard becomes “free-ware” as from November 1,
2022.
The last few updates will be online at October 31.
I personally will continue to answer questions for pwsWD dashboard, same as I still do for the Leuven-template users and the Leuven-forecast scripts .
Anybody can alter and update the current pwsWD 2012_lts version and redistribute that version under ones own name.
But it is not possible to ask money for any pwsWD version, as the licences of some integral scripts prohibit that.
I trust that new authors will support their adapted version here on this “forum” also.
If you have any question about my version of PWS_Dashboard 2012_lts:
PLEASE INCLUDE A LINK TO THE WEBSITE YOU ARE QUESTIONING ABOUT.
As of today I will not answer questions without a link to your pwsWD website.
Those links are needed to check the problem or to inspect scripts or text files.
Having to scan old user-posts one by one if a website-link is included is a waste of time.
Best regards,
Wim