Hello, it is not possible to bring data to PWSdashbord via ecowitt. When I log in to my server nothing is posted there either. I’m currently using meteobridge but it doesn’t work very well there with the extra sensors and the lightning. What am I doing wrong. See screenshot.
Greetings Alexander
Hi Alexander,
Your PWS_Dashboard website is https://manhaeghe.com/pwsWD/index.php
In your ecowitt / WSVIEW Plus you enter for server without www
Your path should then be entered without httpsdocs and with the correct folder name of the URL.
/pwsWD/ecowitt/
Remarks:
Succes,
Wim
Thank you Wim for your answer.
The file htaccess is not in my root folder but it is in my httpdocs. See screenshot. Can I edit it here?
regards Alexander
Probably yes, it is always difficult to find the root of your website between different webservers.
But if there is a httpdocs, it is often the one to use.
You can test with typing in the browser http://manhaeghe.com/pwsWD/ecowitt/index.php?test
If it remains http when it shows a message, then it works OK.
Ecowitt data received:
Problem-77: NO PASSKEY found.
Problem-109: Invalid data:
Wim
this is in the file :
RewriteEngine on
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
<Files config.json>
order allow,deny
deny from all
The first two lines can be replaced by the ones in my post.
Currently all http → https
Ours wil do http (all but not ecowitt/" → https
Result is the same.
But i do not know what the blank line contains, neither where the config.json is used.
Contact your provider as I have no access and it seems the displayed text in your post is not what is in the file.
Show them what you want to add, it is a bypass for all trafic to the pwsWD/ecowitt/index.php script.
Wim
Ok I have sent an email. Now waiting for the answer. I’ll keep you informed.
Alexander
I’ve already tried modifying the .htaccess while waiting for an answer. Not working for now.
Options +FollowSymLinks
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} !^/pwsWD/ecowitt/
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
<Files config.json>
order allow,deny
deny from all
I tested for you also.
It does not work in your case.
Seems the conversion from http to https is done at a higher " level " than httpdocs
Or maybe it is not a standard linux apache server and it does not use .htaccess
Check your cPanel if there is a switch to “enforce HTTPS”
Those problems should be handled by support personel of your provider as they know th ins and outs of their servers.
Wim
Seems to work now 
This morning the http accesses http://manhaeghe.com/pwsWD/ecowitt/ remain http in the browser
So now the question:
Is your ecowitt custom upload setup active?
I see only my own test accesses in the error log file http://manhaeghe.com/pwsWD/ecowitt/ecco_stats.txt
If “custom upload” is disabled, switch it to enable.
It it is already enabled, post a “screenshot” of your phone / tablet with the settings.
If you did not change it:
In your ecowitt / WSVIEW Plus you enter for server without www
Your path should then be entered without httpsdocs and with the correct folder name of the URL.
/pwsWD/ecowitt/
Wim
It works :
It works. Only the max and minimum values not yet. Thank you. My website hoast also changed something in the setting. Greetings Alexander
The data upload appears to have stalled and some blocks off line the station cron needs to be running to sort the history and get the metar data file
Sadly the http bypass fails again.
Click the link from my previous post and it is re-routed to https
As the https protocol definitions forbids re-routing http post data the data is dropped by the webserver and the pwsWd/ecowitt/ scripts only get an empty access.
The website will not receive any data as long as the pwsWD/ecowitt/index.php script is not accessible via http.
Described here, a small script has to run automatically every 5 minutes to update high-lows.
It also pre-loads all outdated files so that you and your visitors do not see old outdated data.
It seems the OP switched to another website Oost vlaanderen rand Vlaamse ARdennen. Home Weather Station (MB_rt version)
And abandoned the pwsWD/ecowitt version for now.
Wim
[quote=“pwsdashboard, post:13, onderwerp:71971”]
Het lijkt erop dat het OP overgestapt op een andere website Oost vlaanderen rand Vlaamse ARdennen. Home Weerstation (MB_rt versie)
En voorlopig de pwsWD/ecowitt versie verlaten.
Wim
[/citaat]
this is the MeteoBridge version. Unfortunately, it is not possible to get the lightning values online. However, the lightning values can be found in Meteobridge. That is why I switched to Ecowitt with the necessary problems.
Any version of the PWS_Dashboard can use the ecowitt lightning and AQ sensor by using in easyweather setup the tab “Devices” and answer the questions at “Use Ecowitt extra-sensors with another weather-program”
Also weather-programs such as WD, Meteobridge, Cumulus can read the ecowitt sensors directly as an extra station of their main weather-station.
As the realtime data of those weather-programs do not support lightning, extra soil, temp AQ sensors there is a second upload possible described in 36_extra_sensors.pdf
Easyweathersetup tab DATA:
The extra data files your weather-program has to process and upload, can be downloaded from a.o. here
Using Meteobridge to " upload extra sensors" is in your case maybe easier as you do not need the “http bypass https” access.
And you are already using your Meteobridge for other website-templates.
WARNING
You changed something in line 3 or 4 in pwsWD/ecowitt/index.php and made a typo.
Parse error : syntax error, unexpected ‘=’ in /var/www/vhosts/manhaeghe.com/httpdocs/pwsWD/ecowitt/index.php on line 4
Wim
it would indeed be easiest to continue working via meteobridge. I know the extra file. The extra sensors work but only the lightning data I can’t retrieve from meteobridge see screenshots.
Check the extra-data file your Meteobridge processing:
https://manhaeghe.com/pwsWD-2/meteobridge/extra_mb.txt
These are the lines for lightning:
#
|lightning|light|[lgt0total-act:--]|!
|lightningtime|light|--]|!
|lightningkm|light|[lgt0dist-act.1:--]|!
You have to adapt those lines as probably the lightning is not on station 0.
Your ecowitt lightning seems to be on station 2 or is it mapped?
If it is on station 2 modify the lines to the ones you see on the screenshot.
I have no idea what the lightning time is, as i do not see that one in your Meteobridge screenshot.
Maybe it is lgt2!0energy
#
|lightning|light|[lgt2!0total-act:--]|!
|lightningtime|light|--]|!
|lightningkm|light|[lgt2!0dist-act.1:--]|!
Always check the mapping you used in your Meteobridge.
Wim
It is indeed station 2. I had not adjusted that. The number of lightnings is now displayed + the distance but the date does not work. Could it be that it is not displayed in meteobridge. I don’t see it displayed in meteobridge either. Can this still be resolved?
Information I found here.
https://forum.meteohub.de/search.php?keywords=ecowitt+lightning+time
It is not 100% clear to me what should be the correct tag, probably lgt2!0total-nonzerotime=epoch:0
Or ask the same question on the Dutch forum, there are dozens of MB and Ecowitt users and it is easier to explain in ones native language.
Succes,
Wim
Tried everything but still failed. If I read it all like this then meteobridge does not deliver lightning times. I don’t see it displayed in my meteobridge itself either. Stupid because now there is always a date of 1970
