Hi,
Over the last few days I have migrated all my data and the PWS dashboard from an old Synology DS212+ to a new DS723+.
The web dashboard loads ok but there is no ‘history’.
For example the wind data. It always shows the Max Gust as the last reading. When the dashboard updates the gust can be lower and the Max Gust lowers too.
This is just an example, I’m sure there are other issues with ‘history’ but hopefully that will be enough to diagnose the issue.
Thanks in advance for help.
Laurie.
What’s the URL of your web page?
Are you running the cron job?
Did you run easyweather setup after switching to the the server?
→ the new website-folder structure needs to be saved in the settings
As soon as you post the URL to your website one can check more detailed information.
I found the URL in the topic the previous time we asked for it
→ Rain history not updating - #3 by dehatter
URL:
South Somerset, UK Home Weather Station (ecoLcl version)
Problem: No CURL support in your PHP setup, so external files can not be loaded
→ Fatal error: Uncaught Error: Call to undefined function curl_init() in /volume1/web/pwsWD/PWS_load_files.php on line 367
Also when I try to access your website I get
→ http://redlands.hopto.org:5000/
Questions:
Did you update the scripts to the letst versions?
What version of PHP are you using?
Succes,
Wim
I’ve obviously made some fundamental mistakes.
I think i’ve got all the right ports open on the router, assuming that there’s nothing special for this traffic.
When you ask if I updated the scripts is that the pwsWD stuff? if so, no. I haven’t changed anything, just move the whole lot via Hyper Backup.
I’ve obviously not set up the web service correctly on the NAS. I can’t see any obvious errors though.
Laurie
Also PHP.
The old NAS was on 7.3 so I assume I should do the same?
The PHP settings are just a part of a webserver.
They need to allow CURL support as all external files are downloaded using CURL.
Without CURL the cron-job and the lowd-files scripts run into a fatal PHP-500 error
I attach two small scripts.
startHere.php.zip (3.4 KB)
startHere.php checks the basic web-server settings
That script is included in the standard PwsDashboard downloads and is the first script which runs after install.
info.php.zip (501 Bytes)
info.php shows the PHP parts installed.
If you still have access to your old NAS you should run it on the old NAS and compare it with the settings of the new server.
I checked and you are using PHP 7.3.x which is relative old.
First remove all problems from this version of your website.
If all is OK run PWS_Updates to download all changed scripts.
Then you can upgrade to PHP 8.
Succes,
Wim
Turns out I’ve done something really stupid in deleting the http user.
So I’ve had to reset the who NAS.
Then I’ll have to rerun Hyperbackup, which took ages.
Hopefully I’ll be back on this by early next week.
And i assume it might be easier to start from scratch with the dashboard.
Wim,
I’ve rebuilt the pws dashboard from scratch.
I can get through to the site now.
Now I have a problem getting the data setup right.
I can’t seem to get any of my data to show, which I assume means there’s none in the pwsWD folder.
I’ve set it up to get data from ecowitt and followed the steps on the WS view app so I don’t know what’s wrong.
The cron job is set up to run every 5 mins so that ought to be ok.
Where should I look next?
TIA,
Laurie.
I’ve sorted it.
The Ecowitt settings on WS View needed changing even though the NAS set up was identical to the old one.
Put in the web address as opposed to internal and hey presto.
I do not think your cron is working so the address to the PWS_stationcron.php in that may also be wrong hence still no graphs or history data being created
Please check your settings.
For your Ecowitt device → WSView
Readme: https://pwsdashboard.com/documentation2012/42_ecowitt.pdf
The server name : http://redlands.hopto.org:8899/
The path (= to the receiving script): /pwsWD/ecowitt/
Do not forget the starting /
For your easyweather-settings:
The location and filename ./ecowitt/ecco_lcl.arr
You can not use any other filename. Be aware of the double cc
After that is correctly set it should work OK.
You can also use the internal IP-address with the correct file path.
F.i. http://192.168.x.y:8899/ as long as your NAS setup point to the root in wich the pwsWD/ folder is located.
Just test in your local browser: http://192.168.x.y:8899/pwsWD/ecowitt/ecco_stats.txt
That should show the log-file with the status messages.
The output should be identical with:
http://redlands.hopto.org:8899/pwsWD/ecowitt/ecco_stats.txt
Thu, 24 Apr 2025 10:46:27 +0000 = Ecowitt data received:
Problem-77: NO PASSKEY found.
Problem-101: Item in upload: with value between next brackets =><= is invalid
Problem-111: No data uploaded.
Succes,
Wim
This one has width=“900”
Thanks Wim,
That’s got the data showing.
Now the cron job isn’t working.
This is what I’m running :
/volume1/web/pwsWD/PWS_cron_stationcron.php
and this is the result
/volume1/web/pwsWD/PWS_cron_stationcron.php: line 1: ?php: No such file or directory
/volume1/web/pwsWD/PWS_cron_stationcron.php: line 7: =: command not found
/volume1/web/pwsWD/PWS_cron_stationcron.php: line 7: //: Is a directory
/volume1/web/pwsWD/PWS_cron_stationcron.php: line 9: syntax error near unexpected token $hr_rll_vr' /volume1/web/pwsWD/PWS_cron_stationcron.php: line 9: if (isset ($hr_rll_vr)) { $hr_rll_vr = (int) $hr_rll_vr;} else {$hr_rll_vr = 0;}’
The cron-server seems to start the cron-script from the wrong folder.
And / Or the cron-server does not supports or allow PHP scripts.
AFAICS it is HTML only
/volume1/web/pwsWD/PWS_cron_stationcron.php: line 1: ?php: No such file or directory
Nearly always the solution is
→ use an external cron server such as https://cron-job.org/en/
If you are forced to use your “webserver internal cron” make sure that the cron-server
executes /pwsWD/PWS_cron_stationcron.php
and not /PWS_cron_stationcron.php
The cronjob needs to run from within the main folder of PwsDashboard.
Not from any other “lower” folder.
Succes,
Wim
if you are trying to run the cron locally, you might try the command like this,
/usr/bin/php /path/to/script.php
I find it easier to use cron-job.org though
I was having a similar issue on my Synology NAS and using https://cron-job.org fixed it.
Wim,
I found the solution in a 2013 page on the Synology community.
I had to prefix the file with php.
So if anyone else has the same issue, on Synology the user defined script field is
php /volume1/web/pwsWD/PWS_cron_stationcron.php
Hope that helps.
Thanks for your help as ever.
Laurie.
Isn’t that what @blainec suggested?