WXforum.net
Weather Station Hardware => Ambient Weather and Ecowitt and other Fine Offset clones => Topic started by: Maximux on July 06, 2021, 08:48:13 AM
-
Hi, I installed a remote weather station using the WH6003/WH6006/WH6007 GSM / 3G device by Misol/Fineoffset 433 mhz.
But as Custom Server provides only sending data via WU protocol, (it is not possible to select Ecowitt), this puts me in detail to connect it to the "PWSWD" weather system which receives data only from Ecowitt protocol, in optre I also tried to use The "Foshkplugin" which I managed to get them received but then I can't set them into a protocol / code readable by the "PWSWD" system.
Can anyone help me connect the "WH600X" device to the "PWSWD" system? Thank you.
I look forward to a kind reply, thank you.
Regards.
PS: Reading some posts say that you can solve using the "WEEWX" system but I didn't understand how to install it and configure it.
I hope there is way to do it with the Foshk Plugin.
-
Hi!
Which firmware version are you using? I thought that the Ecowitt protocol is now also supported in the custom server.
You might also ask the Ecowitt support about this. If the Ecowitt protocol is displayed, it should probably be selectable as well.
If you mean PWS Dashboard: it supports different ways of data submission. It is almost certain that the WU protocol that your station sends is also supported.
So FOSHKplugin is not needed at all if you only want to feed PWS dashboard. But it could be used to enable more than one custom server target or to convert to other formats (e.g. Ecowitt).
Regards, Oliver
-
Did you try to post your question in the pwsWD forum ?
Wim, the pwsWD moderator or someone will surely come up with a response.
https://www.weather-watch.com/smf/index.php/board,77.0.html
And pwsWD has many different ways to receive data. They are described in the setup instructions.
-
Hi, I installed a remote weather station using the WH6003/WH6006/WH6007 GSM / 3G device by Misol/Fineoffset 433 mhz.
But as Custom Server provides only sending data via WU protocol, (it is not possible to select Ecowitt), this puts me in detail to connect it to the "PWSWD" weather system which receives data only from Ecowitt protocol, in optre I also tried to use The "Foshkplugin" which I managed to get them received but then I can't set them into a protocol / code readable by the "PWSWD" system.
Can anyone help me connect the "WH600X" device to the "PWSWD" system? Thank you.
I look forward to a kind reply, thank you.
Regards.
PS: Reading some posts say that you can solve using the "WEEWX" system but I didn't understand how to install it and configure it.
I hope there is way to do it with the Foshk Plugin.
You can use the FOSHK-plugin to get data and upload it to other formats such as ecowitt.
It has a "ton of features" and it runs on a Raspberry.
There is a separate topic about it on this forum.
You do not need to use custom upload if all data is already on WeahterUnderground
The PWS_Dashboard can read the data directly from WeatherUnderground using your free API-key.
===
I think the Foshkplugin should be able to do what you want also, but I am not sure.
I will point the author to your topic,
Wim
@Gyvate @olicat
My connection was extremely slow, so I did not see that you already answered.
All three in the same minute.
-
The WH6006 can upload data to Wunderground - see chapter "Upload" of the manual.
If you do that already - or will do so, you can use the pwsWD feature @Wim mentioned before to retrieve the data from wunderground.com.
As far as I know this is described in the pwsWD setup documentation.
If you follow these and it still doesn't work, come back here (or open a thread in the pwsWD forum - link see above in my earlier reply)
@Wim: all good - no harm done 8-)
-
The WH6006 does not support the Ecowitt protocol, it only has the Custom Server support for WU protocol.
To clarify, the WH6006 technically does upload to Ecowitt with the Ecowitt protocol, but this option is not available in the Custom Server Upload.
-
Hi George,
The WH6006 does not support the Ecowitt protocol, it only has the Custom Server support for WU protocol.
then I apparently misunderstood the sentence in the WS6006 manual (https://osswww.ecowitt.net/uploads/20201219/WS6006%204G%20Version%20Manual.pdf) on page 44:
Customized Website
Supports uploading to your customized
website, if the website has the same
protocol with Wunderground or
Ecowitt
I interpreted it to mean that the Ecowitt protocol is also supported in the custom server - but I don't know this station.
Sorry!
Oliver
-
Hi Oliver
the WH6006 and the WS6006 are very different stations - the WH6006 is limited to Wunderground only, whereas the WS6006 can upload to ecowitt.net, WU and WOW and has the customized server option (WU protocol only].
What makes the confusion perfect is that the WH6006 is nowadays named by Ecowitt WS6006 2G/3G and the WS6006 is named WS6006 3G/4G. ](*,)
So, when we speak of the WS6006, we always have to look at whether it's the 2G/3G version (no longer sold) or the WS6006 3G/4G.
But when someone speaks of a WH6006, it's the older 2G/3G model.
On the station page at Ecowitt.com you find two different manuals - one for each "type".
-
Now my head is spinning. But I did know that there was a 2G/3G version and then a newer 3G/4G version. I recently worked with someone that had a newer 3G/4G version and I remoted into the computer to help with the install. I was surprised to learn from working on it that it uploaded to Ecowitt.net (obviously with Ecowitt.net protocol), but under Customized Server it only had WU protocol option. And yes I updated the firmware to the most recent version. Incidentally during this project I discovered some firmware bugs with the upload protocol. If I remember correctly I think it was related to the barometer uploading station pressure instead of Relative pressure. Ecowitt made some firmware updates which everyone is now enjoying, if you update your firmware. This was about a year ago or year and half ago. It is possible that since then Ecowitt has updated the station firmware further to now allow for Ecowitt protocol with the Customized Server feature. I have not worked on a WH6006 since then.
-
Hi, thank you for your support, I confirm the module I have is the WH6006 2G / 3G not 4G. The FW version is ultimately available at the moment and does not have the Ecowitt protocol on the custom server, but it loads the data both on Ecowitt and Wu.
I just wanted to know if there is no way to convert Wu data, sent from the device to a server to Raspberry type the Foshkplugin, in EcoWitt data that I can then send to the PWSWD station.
Or if I can get other files readable from the PWSWD station as "Clientraw or RealTime TXT". Foshkplugin only generates the "CSV and TXTFile" files that are not recognized by the PWSWD station.
PS: Realtime data from the Wu server are not all available there are no related ones, there are additional temperature sensors (internal / external) the ground and the air.
-
Hi!
I just wanted to know if there is no way to convert Wu data
FOSHKplugin should be able to convert WU to Ecowitt. Beside that FOSHKplugin should be able to generate a realtime.txt and a clientraw.txt.
But I have never tested this way (source WU) particularly intensively - it may still contain a few bugs.
Oliver
-
. . .
PS: Realtime data from the Wu server are not all available there are no related ones, there are additional temperature sensors (internal / external) the ground and the air.
I am not sure if and how those extra sensors are uploaded to WU.
- Can you post the WU-ID of your station, so I can check what data is returned by WU and what is shown on the WU_dashboard.
- Do you have the contents of the file (or the complete URL) which is uploaded to WU?
Maybe you can check that in the Foshk-plugin.
I will check if it is sensible to make a ecowitt-WU-format receiving script. That will only take a day or two.
And if possible, it should :idea: solve your problem.
Wim
-
Hi!
I just wanted to know if there is no way to convert Wu data
FOSHKplugin should be able to convert WU to Ecowitt. Beside that FOSHKplugin should be able to generate a realtime.txt and a clientraw.txt.
But I have never tested this way (source WU) particularly intensively - it may still contain a few bugs.
Oliver
Hi Olicat, I tried with the FOSHKPLG but I don't generate the RealTime.txt and clientraw.txt file, configured it as the HP1000SE Pro station that transmits via Ecowitt protocol, but does not save those file formats.
I put this configuration:
[Forward-10]
FWD_CMT = save as local realtime.txt
FWD_TYPE = REALTIMETXT
FWD_ENABLE = True
FWD_INTERVAL = 20
FWD_URL = /opt/FOSHKplugin-CF/report/
[Forward-11]
FWD_CMT = save as local clientraw.txt
FWD_TYPE = CLIENTRAWTXT
FWD_ENABLE = True
FWD_INTERVAL = 20
FWD_URL = /opt/FOSHKplugin-CF/report/
[Forward-14]
FWD_CMT = save as local realtime.txt
FWD_TYPE = CSVFILE
FWD_ENABLE = True
FWD_INTERVAL = 20
FWD_URL = /opt/FOSHKplugin-CF/report/
[Forward-15]
FWD_CMT = save as local clientraw.txt
FWD_TYPE = TXTFILE
FWD_ENABLE = True
FWD_INTERVAL = 20
FWD_URL = /opt/FOSHKplugin-CF/report/
I also tried to send the data to the PHP module to generate the "ecco_lcl.arr" file but it does not work gives me passkey error not found...
[Forward-16]
FWD_TYPE = EW (or RAWEW)
FWD_ENABLE = True
FWD_INTERVAL = 20
FWD_URL =/var/www/html/pwsWD-CF/ecowitt/index.php
This has generated in the php script that I attach to the post.
[ You are not allowed to view attachments ]
If you can use place, attached also files generated by Foshkplugin.
[ You are not allowed to view attachments ]
Let me know if Foshkplugin logs are also needed.
-
. . .
PS: Realtime data from the Wu server are not all available there are no related ones, there are additional temperature sensors (internal / external) the ground and the air.
I am not sure if and how those extra sensors are uploaded to WU.
- Can you post the WU-ID of your station, so I can check what data is returned by WU and what is shown on the WU_dashboard.
- Do you have the contents of the file (or the complete URL) which is uploaded to WU?
Maybe you can check that in the Foshk-plugin.
I will check if it is sensible to make a ecowitt-WU-format receiving script. That will only take a day or two.
And if possible, it should :idea: solve your problem.
Wim
Hello wvdkuil, station wu id is: icarlofo2
The Wu data you need maybe are in the attached files in the previous post.
I am attaching these two foshkplugin log files where there are data you hope you are useful to solve the problem, thank you very much for yours, indeed, for your availability.
[ You are not allowed to view attachments ]
-
. . .
PS: Realtime data from the Wu server are not all available there are no related ones, there are additional temperature sensors (internal / external) the ground and the air.
I am not sure if and how those extra sensors are uploaded to WU.
- Can you post the WU-ID of your station, so I can check what data is returned by WU and what is shown on the WU_dashboard.
- Do you have the contents of the file (or the complete URL) which is uploaded to WU?
Maybe you can check that in the Foshk-plugin.
I will check if it is sensible to make a ecowitt-WU-format receiving script. That will only take a day or two.
And if possible, it should :idea: solve your problem.
Wim
Hello wvdkuil, station wu id is: icarlofo2
The Wu data you need maybe are in the attached files in the previous post.
I am attaching these two foshkplugin log files where there are data you hope you are useful to solve the problem, thank you very much for yours, indeed, for your availability.
[ You are not allowed to view attachments ]
1
At first look, both "ecowitt" and "wu" log-files do not contain any extra sensors, only the standard ones.
So if there are no extra sensors currently attached to your station, you could use the Foshk-Ecowitt upload if @olicat could add a "PASSKEY" item with some contents.
I am currently not at my computer, so i did not check the exact names of the posted items.
Will do that later today.
Wim
-
Hi!
you could use the Foshk-Ecowitt upload if @olicat could add a "PASSKEY" item with some contents.
No problem.
Static values can be added to the output line as required. To do this, simply enter a pseudo PASSKEY in the config file under Export\ADD_ITEMS - for example:
[Export]
ADD_ITEMS = PASSKEY=000102030405060708090A0B0C0D0E0F
Keep in mind to restart the FOSHKplugin-service after changing the config file.
BTW:
I would modify the EW-forward a bit:
[Forward-16]
FWD_TYPE = EW
FWD_ENABLE = True
FWD_INTERVAL = 20
FWD_URL =http://127.0.0.1/pwsWD-CF/ecowitt/
but perhaps it also works with your config.
Oliver
-
Hi!
you could use the Foshk-Ecowitt upload if @olicat could add a "PASSKEY" item with some contents.
No problem.
Static values can be added to the output line as required. To do this, simply enter a pseudo PASSKEY in the config file under Export\ADD_ITEMS - for example:
[Export]
ADD_ITEMS = PASSKEY=000102030405060708090A0B0C0D0E0F
Keep in mind to restart the FOSHKplugin-service after changing the config file.
BTW:
I would modify the EW-forward a bit:
[Forward-16]
FWD_TYPE = EW
FWD_ENABLE = True
FWD_INTERVAL = 20
FWD_URL =http://127.0.0.1/pwsWD-CF/ecowitt/
but perhaps it also works with your config.
Oliver
Ok, thanks olicat I made the changes as you advised me,
I confirm that now the whole system works well without problems, the "here_lcl.arr" file is generated well without problems and recognized by the "PWSWD" station correctly,
now it is to be verified that all data are correctly recognized and loaded by "PWSWD".
Thanks again for the support.
-
. . .
PS: Realtime data from the Wu server are not all available there are no related ones, there are additional temperature sensors (internal / external) the ground and the air.
I am not sure if and how those extra sensors are uploaded to WU.
- Can you post the WU-ID of your station, so I can check what data is returned by WU and what is shown on the WU_dashboard.
- Do you have the contents of the file (or the complete URL) which is uploaded to WU?
Maybe you can check that in the Foshk-plugin.
I will check if it is sensible to make a ecowitt-WU-format receiving script. That will only take a day or two.
And if possible, it should :idea: solve your problem.
Wim
Hello wvdkuil, station wu id is: icarlofo2
The Wu data you need maybe are in the attached files in the previous post.
I am attaching these two foshkplugin log files where there are data you hope you are useful to solve the problem, thank you very much for yours, indeed, for your availability.
[ You are not allowed to view attachments ]
1
At first look, both "ecowitt" and "wu" log-files do not contain any extra sensors, only the standard ones.
So if there are no extra sensors currently attached to your station, you could use the Foshk-Ecowitt upload if @olicat could add a "PASSKEY" item with some contents.
I am currently not at my computer, so i did not check the exact names of the posted items.
Will do that later today.
Wim
Ok, thanks wvdkuil, I verified and the extra sensors (pm2.5 and soil) at the moment they are docked, surely there are reception problems, but at the moment I can't verify because they are several km away.
As Olicat said I entered the passkey value and now the php (ecowitt) script works properly and generates the "ecco_lcl.arr" file, but checking the station data I noticed that it does not recognize the barometric data, it seems to be a single section that remains to zero.
I am attaching the file data ".arr" so you can check what the conversion from Wu to EW is wrong.
I put the station on the online site so you can check the problem.
Link: https://maxmeteofruttidoro.altervista.org/CF/index.php
The rest seems correct but I'm not sure.
If here ( https://www.ecowitt.net/home/share?authorize=6HGPFK ) you can verify official EW data.
Thank you for your help and support.
[ You are not allowed to view attachments ]
-
Hi!
I noticed that it does not recognize the barometric data, it seems to be a single section that remains to zero.
The WH6006 sends in a not entirely valid WU format in the custom server - but at least in a somewhat unusual way.
The absolute air pressure is transmitted as "absbaro" and the relative air pressure as "barominrelin" - FOSHKplugin expects other key names and does not convert these keys to Ecowitt so far.
That will come with the next version. Let me know if you want to try the current beta.
Oliver
-
@olicat
I assume there will be other field-names which are inconsistent. I changed the live data script to cope with the pressure name for now.
But probably there will be more field names to change if the station will be uploading extra sensors.
For now those sensors do not appear on the ecowitt site, therefor there is no prove that the station will be uploading those sensors in WU format.
If the ecowitt API to retrieve data from the ecowitt website becomes available, I will add that API also then that API can be used without custom upload. The dashboard already supports the Ambient API.
IMHO it would be best if your plugin does the renaming as you already have all the code for that.
@Maximux
Attached the adapted script to test.
@ALL
I will be unavailable from Saterday 10 - Sunday 18, without decent internet, probably no grid at all.
Just post the problems and I will look into them when I am back.
Wim
-
@Maximux
Attached the adapted script to test.
@ALL
I will be unavailable from Saterday 10 - Sunday 18, without decent internet, probably no grid at all.
Just post the problems and I will look into them when I am back.
Wim
Ok, thanks Wvdkuil, I replaced the "PWS_LIVEDATA" file with the updated one you have attached, and now it seems to work properly without poweries.
When they then restore the extra sensors to the WH6006 device we could also verify operation with those incoming data.
For the moment the system has no obvious problems, if known some other anomaly informed you.
For the moment many thanks for your support.
Regards.
PS: If Ecowitt also implemented the APIs would be much faster and more easily, the conversion, upgrade and loading of data, from any system / format / protocol of the devices, we hope they will soon bring these and other updates that improve ecowit system with all the Function that also lack compared to the ambient system.
-
Hi!
That will come with the next version. Let me know if you want to try the current beta.
Oliver
Hi Olicat, I don't know if a later version of Foshkplugin out, at the moment I installed the "0.0.8" version.
However, there is another version that I can test I am available.
Thank you.
Regards.
-
Hi!
Currently there's no newer version out than v0.08.
But in my internal beta I made already some adjustments for the WH6006.
Since Wim adjustet PWSD there's no need to go for a FOSHKplugin-Beta for now. Except you want to use the conversion from WU to Ecowitt-Protocol for other targets (like Personal Weather Tablet).
I'll let you know if there are some more interesting changes worth for testing.
Regards, Oliver
-
1
At first look, both "ecowitt" and "wu" log-files do not contain any extra sensors, only the standard ones.
So if there are no extra sensors currently attached to your station, you could use the Foshk-Ecowitt upload if @olicat could add a "PASSKEY" item with some contents.
I am currently not at my computer, so i did not check the exact names of the posted items.
Will do that later today.
Wim
Hi Wvdkuil, resuming this discussion, I added the quality sensor of the air PM2.5 to the WH6007 device, but on the "PWSWD" site when I insert the sensor from this error: "Problem 46: No PM Sensor Number 1 Found Check Settings and Date"
How can this problem solve? Thanks.
Greetings.
PS: I am attaching Foshkplugin's Raw weather data logs and Ecowitt PWSWD Data file.
[ You are not allowed to view attachments ]
-
Hi!
The key AqPM2.5 is not converted through FOSHKplugin yet. I'll send you a link to my internal Beta which already is able to.
So this is not a problem of PWSDashboard at all!
I wish Ecowitt would finally allow uploading in Ecowitt format for this station as well ...
Please all WH6006/WH6007/WS6006 users: Please report to Ecowitt that you would like uploading in Ecowitt format via custom server very much!
Regards, Oliver
-
Hi!
The key AqPM2.5 is not converted through FOSHKplugin yet. I'll send you a link to my internal Beta which already is able to.
So this is not a problem of PWSDashboard at all!
I wish Ecowitt would finally allow uploading in Ecowitt format for this station as well ...
Please all WH6006/WH6007/WS6006 users: Please report to Ecowitt that you would like uploading in Ecowitt format via custom server very much!
Regards, Oliver
Hi Oliver, I noticed from the log of the plugin that the PM2.5 data is received from the device and sent to the PWSDashboard site in fact also the "ecco_lcl.arr" file also succeed, but the PM2.5 Module of the PWSD is not recognizing him perhaps because I Tags of this are different from those normally used by the standard Ecowitt protocol.
However this must be verified by WVDKUIL.
Thank you for your answer.
PS: it would be nice that they directly implement data sending data via Ecowitt protocol as it deny the other devices but still do not. The firmware of this device still possesses many bugs and gaps compared to the other devices.
-
Hi Oliver, I noticed from the log of the plugin that the PM2.5 data is received from the device and sent to the PWSDashboard site in fact also the "ecco_lcl.arr" file also succeed, but the PM2.5 Module of the PWSD is not recognizing him perhaps because I Tags of this are different from those normally used by the standard Ecowitt protocol.
. . .
However this must be verified by WVDKUIL.
. . .
I verified your uploaded file. . ./PWS_listfile.php?file=./ecowitt/ecco_lcl.arr&type=arr
[windgustmph_max10m] => 5.1
[pm25_AQIlvl_ch1] => 2
[pm25batt1] => 5
[pm25_AQIlvl_avg_24h_ch1] => 2
[pm25_avg_24h_ch1] => 19.1
[pm25_AQI_avg_24h_ch1] => 66
[pm25_AQI_ch1] => 61
[pm25_ch1] => 21.0
The field-names used pm25_ch1 , pm25_avg_24h_ch1 and pm25batt1 are OK and are translated into correct weather-values
[pm25_24avg1] => 19.1
[pm25_crnt1] => 21The PWS_Dashboard needs to calculate the AQ-index itself as different indexes can be used.
When I test the AQ-block script with . . . /_test.php?test=AQ_station_block.php all is OK.
Wim
-
Hi wvdkuil, I checked how you suggested, returns the following message:
" Notice: Undefined index: model in /membri/maxmeteofruttidoro/CF/PWS_livedata.php on line 314
Problem 46: No PM sensor number 1 found
Check settings and data "
I look forward to instructions, thank you.
Greetings.
-
Hi wvdkuil, I checked how you suggested, returns the following message:
" Notice: Undefined index: model in /membri/maxmeteofruttidoro/CF/PWS_livedata.php on line 314
Problem 46: No PM sensor number 1 found
Check settings and data "
I look forward to instructions, thank you.
Greetings.
It seems you have multiple sites.
I was checking https://maxmeteofruttidoro.altervista.org/
Your error message points to https://maxmeteofruttidoro.altervista.org/CF/index.php
You are right that the needed data is not there
[uv] => 2
[dailyrainin] => 0
[dewptf] => 65.8
[AqPM2_5] => 11.0
[yearlyrainin] => 11.41
[humidity] => 72
[winddir] => 142
[rainratein] => 0
[barominrelin] => 30.056
[tempf] => 75.6
[absbaro] => 29.648
[dateutc] => 2021-09-08 08:24:17
[windspeedmph] => 0.895
[tempinf] => 79.5
[battery] => 80
[solarradiation] => 172.36
[stationtype] => MAXWEATHER-CF-3G V1.1.26
[windgustmph] => 2.461
[weeklyrainin] => 0
[humidityin] => 66
[monthlyrainin] => 0.41
[wh65batt] => 1
The error message about "model" can be discarded.
We need to have the pollution values in um3 with labels pm25_ch1 and pm25_avg_24h1
The device is not uploading both values in WU-type uploads.
https://support.weather.com/s/article/PWS-Upload-Protocol?language=en_US
Only one "AqPM2.5 - PM2.5 mass - UG/M3"
That AqPM2.5 fields should be renamed to pm25_ch1
I will check what to be changed in the script when only current value is available.
Wim
-
Hi!
That AqPM2.5 fields should be renamed to pm25_ch1
Should work with latest beta which Maximux will install soon.
Oliver
-
Hi!
That AqPM2.5 fields should be renamed to pm25_ch1
Should work with latest beta which Maximux will install soon.
Oliver
Hi Oliver,
OK, the block script will work OK when only the current value pm25_ch1 is in the upload.
Maybe you could rename stationtype to model also?
Wim
-
Hi Wim,
Maybe you could rename stationtype to model also?
of course (probably).
But in the data coming from the WH600x there is neither stationtype nor model:
ID=MaxMeteo-CF
PASSWORD=XXXXXX
indoortempf=80.1
indoorhumidity=66
tempf=72.3
humidity=76
dewptf=64.4
winddir=114
windspeedmph=3.803
windgustmph=4.921
rainin=0
dailyrainin=0
weeklyrainin=0
monthlyrainin=0.41
yearlyrainin=11.41
solarradiation=72.27
UV=1
baromin=30.041
absbaro=29.633
AqPM2.5=13.0
battery=75
wh65batt=1
dateutc=2021-09-08+06:35:17
softwaretype=MAXWEATHER-CF-3G%20V1.1.26
action=updateraw
realtime=1
rtfreq=5
PASSKEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Only softwaretype is available but this seems to be user defined.
But there's already a solution in FOSHKplugin to define some static keys. Just add in the Export\ADD_ITEMS line the phrase &model=WH6006 (or whatever it is):
[Export]
ADD_ITEMS = &PASSKEY=thecorrespondingkeyinPWSD&model=WH6006&stationtype=whateveryouwant
This string will be added to every outgoing line.
Regards, Oliver
-
Hi Wim,
Maybe you could rename stationtype to model also?
of course (probably).
But in the data coming from the WH600x there is neither stationtype nor model:
. . .
Only softwaretype is available but this seems to be user defined.
But there's already a solution in FOSHKplugin to define some static keys. J
. . .
Hi O)liver,
Probably that is used as I can only check the uploaded data to the website
. . . /CF/PWS_listfile.php?file=./ecowitt/ecco_lcl.arr&type=arr
[uv] => 3
[dailyrainin] => 0
[dewptf] => 68.9
[AqPM2_5] => 10.0
[yearlyrainin] => 11.41
[humidity] => 71
[winddir] => 129
[rainratein] => 0
[barominrelin] => 30.053
[tempf] => 79.0
[absbaro] => 29.645
[dateutc] => 2021-09-08 09:10:26
[windspeedmph] => 6.040
[tempinf] => 79.5
[battery] => 87
[solarradiation] => 328.27
[stationtype] => MAXWEATHER-CF-3G V1.1.26
[windgustmph] => 7.605
[weeklyrainin] => 0
[humidityin] => 66
[monthlyrainin] => 0.41
[wh65batt] => 1So the user should change it to model then.
Wim
-
Ok, thanks to all for these clarifications.
I will update Foshkplugin as soon as possible to test the correct operation of the parameters with PWSD. Thanks.
Talk to you soon.
Greetings.
-
Hi, I wanted to inform you that I updated Foshkplugin to version 0.09, with the related changes to the CFG file as suggested by Oliver, and now the PSWS PM2.5 module works correctly.
Thanks.
Greetings.
-
[tup]
Hi, I wanted to inform you that I updated Foshkplugin to version 0.09, with the related changes to the CFG file as suggested by Oliver, and now the PSWS PM2.5 module works correctly.
Thanks.
Greetings.
[tup]
-
... just to clarify this, there's no official v0.09 or public beta of FOSHKplugin yet. I'm still working on this.
But if anybody needs a working solution for WH600x give me a sign.
Oliver
-
... just to clarify this, there's no official v0.09 or public beta of FOSHKplugin yet. I'm still working on this.
But if anybody needs a working solution for WH600x give me a sign.
Oliver
But in any case, for now this version seems to work smoothly.
Great job, as always.
For whatever test I remain available.
I look forward to further software updates, thanks.
Greetings.
PS: soon also added last to the 600x console the Soil Sensor WH51 so also verify the correct operation with those data.
-
Hi everyone, especially in Wvdkuil and Olicat, I wanted to inform that I also enabled the Soil Moisture Sensor in the WH600X unit, but on PWSWD returns the following error: "Soil Sensors Not Available, script ends".
Can this script data recognition problem be solved? Thanks.
Greetings.
The site in question is as follows: https://maxmeteofruttidoro.altervista.org/CF/index.php
Attached the data of the weather sent received from the device:
-
Hi!
I see the problem and have to analyze it. The key soilmoisture has to be renamed to soilmoisture1 in Ecowitt.
Nothing to do on PWSDashboard-side - it is a problem of FOSHKplugin. Will check and send you a new Beta.
@Maximux
Attached the data of the weather sent received from the device:
Is the string "WU -> EW Data sent by Foshkplugin" in attached file Data_File.txt coming from the raw- or the sndlog of FOSHKplugin? It seems to be the data coming from the station and thus BEFORE converting to Ecowitt.
Oliver
-
Hi!
I see the problem and have to analyze it. The key soilmoisture has to be renamed to soilmoisture1 in Ecowitt.
Nothing to do on PWSDashboard-side - it is a problem of FOSHKplugin. Will check and send you a new Beta.
Oliver
OK thank you. I await your news and new updated plugin files, thanks.
Greetings.
-
Hi!
I see the problem and have to analyze it. The key soilmoisture has to be renamed to soilmoisture1 in Ecowitt.
Nothing to do on PWSDashboard-side - it is a problem of FOSHKplugin. Will check and send you a new Beta.
@Maximux
Attached the data of the weather sent received from the device:
Is the string "WU -> EW Data sent by Foshkplugin" in attached file Data_File.txt coming from the raw- or the sndlog of FOSHKplugin? It seems to be the data coming from the station and thus BEFORE converting to Ecowitt.
Oliver
Hi Olicat, I installed update of the plugin you sent me and now it works, everything ok, thanks.
Greetings.
-
Hi!
in Ecowitts own forum they answered (https://www.ecowitt.com/shop/forum/forumDetails/403) my question regarding the support of Ecowitt protocol via custom server:
You can assign a port other than 80. It is user-definable.
The path is fixed with /weatherstation/updateweatherstation.php.
Due to processor resources limitation, the current model is supporting WU protocol only.
But there're also some interesting details regarding the used WU protocol variant.
Worth to read!
Oliver