Author Topic: FOSHKplugin - brief introduction  (Read 5169 times)

0 Members and 1 Guest are viewing this topic.

Offline lemuba

  • Member
  • *
  • Posts: 48
    • Fitzbek-Wetter.de
Re: FOSHKplugin - brief introduction
« Reply #75 on: March 20, 2021, 01:54:27 PM »
Hi Oliver,

thanks again for your hint. The last rare lighting for this season in S-H /Schleswig-Hostein was end of February, but the oldest log entry from March 14.

So I need to wait for the next thunder storm - no problem...
However, Im very happy. PWSDashboard from Wim, Weewx, and Iobroker/NodeRed perfectly served by your plugin :grin: [tup]
Switched over to a potent HP Nuc (hp prodesk 400 g5) end of last year - a 400,- to 600,-machine, via mydealz/Mediamarkt for finally 200,- \:D/
Now everything seperated under Proxmox and backups and quick snapshots are so easy to perform:

  [ You are not allowed to view attachments ]
« Last Edit: March 20, 2021, 02:03:53 PM by lemuba »

Offline lemuba

  • Member
  • *
  • Posts: 48
    • Fitzbek-Wetter.de
Re: FOSHKplugin - brief introduction
« Reply #76 on: March 23, 2021, 12:15:09 PM »
@olicat

Back here now with regard to: https://www.weather-watch.com/smf/index.php/topic,70904.msg571091.html#msg571091

Have updated the foshkplugin to version 07 now and added follwing lines to the config (with reboot):

[Export]
EVAL_VALUES = True
ADD_ITEMS =
OUT_TEMP =
OUT_HUM =
FIX_LIGHTNING = True


[Status]
last_lightning = 20
last_lightning_time = 1615462200
StopTime = 1616513074

Output in the raw-foshkplugin.log:

23.03.2021 17:12:17.884 PASSKEY=xxx&stationtype=GW1000A_V1.6.6&dateutc=2021-03-23+16:12:17&tempinf=76.1&humidityin=34&baromrelin=30.215&baromabsin=30.168&tempf=46.0&humidity=82&winddir=233&windspeedmph=1.12&windgustmph=1.12&maxdailygust=9.17&solarradiation=43.31&uv=0&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.008&weeklyrainin=0.059&monthlyrainin=2.752&yearlyrainin=7.945&totalrainin=7.945&temp1f=3.74&temp2f=69.08&temp3f=53.42&humidity3=67&lightning_time=1615462200&lightning_num=0&lightning=20&wh65batt=0&batt1=0&batt2=0&batt3=0&wh57batt=3&freq=868M&model=GW1000_Pro&dewptf=40.9&windchillf=46.0&feelslikef=46.0&heatindexf=44.2&windspdmph_avg10m=0.7&winddir_avg10m=212&windgustmph_max10m=4.5&brightness=5487.4

But no last lightning data arriving/processed here...?:
https://www.fitzbek-wetter.de/pwsWDxx/index.php?lang=de-dl

Forward:

[Forward]
FWD_TYPE = RAWEW
FWD_INTERVAL = 16
FWD_URL = https://fitzbek-wetter.de/my path...

But then no lightning data arriving at pws dashboard:

Code: [Select]
a:36:{s:11:"stationtype";s:14:"GW1000A_V1.6.6";s:7:"dateutc";s:19:"2021-03-23 16:37:32";s:7:"tempinf";s:4:"76.3";s:10:"humidityin";s:2:"34";s:10:"baromrelin";s:6:"30.212";s:10:"baromabsin";s:6:"30.165";s:5:"tempf";s:4:"45.9";s:8:"humidity";s:2:"84";s:7:"winddir";s:3:"234";s:12:"windspeedmph";s:4:"0.67";s:11:"windgustmph";s:4:"2.24";s:12:"maxdailygust";s:4:"9.17";s:14:"solarradiation";s:5:"31.56";s:2:"uv";s:1:"0";s:10:"rainratein";s:5:"0.000";s:11:"eventrainin";s:5:"0.000";s:12:"hourlyrainin";s:5:"0.000";s:11:"dailyrainin";s:5:"0.008";s:12:"weeklyrainin";s:5:"0.059";s:13:"monthlyrainin";s:5:"2.752";s:12:"yearlyrainin";s:5:"7.945";s:11:"totalrainin";s:5:"7.945";s:6:"temp1f";s:4:"9.50";s:6:"temp2f";s:5:"69.08";s:6:"temp3f";s:5:"51.08";s:9:"humidity3";s:2:"67";s:14:[u][b]"lightning_time";s:0:"";s:13:"lightning_num";s:1:"0";s:9:"lightning";s:0:"";s:8:"[/b][/u]wh65batt";s:1:"0";s:5:"batt1";s:1:"0";s:5:"batt2";s:1:"0";s:5:"batt3";s:1:"0";s:8:"wh57batt";s:1:"3";s:4:"freq";s:4:"868M";s:5:"model";s:10:"GW1000_Pro";}

 
« Last Edit: March 23, 2021, 12:43:44 PM by lemuba »

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #77 on: March 23, 2021, 01:47:09 PM »
Hi Matthias,

For the analysis it would have been correct to look in the send log whether lightning_time is being sent from FOSHKplugin to PWSDashboard at all.
But you don't have to do that anymore ...

With the forward type RAWEW you send the unchanged incoming string - without any adjustments by FOSHKplugin. If you use the EW type instead, the lightning data stored by FOSHKplugin should be sent to PWSDashboard.

The documentation says:
Quote
RAWEW  untouched Ecowitt (EW-->EW or WU-->EW)
EW         enhanced Ecowitt (WU-->EW or EW-->EW)
So just change your FWD_TYPE = RAWEW to FWD_TYPE = EW and everything should be fine.

Regards, Oliver

Offline lemuba

  • Member
  • *
  • Posts: 48
    • Fitzbek-Wetter.de
Re: FOSHKplugin - brief introduction
« Reply #78 on: March 23, 2021, 02:34:27 PM »
Hi Oliver, perfect, fixed! Many thanks again!

Matthias

Offline lemuba

  • Member
  • *
  • Posts: 48
    • Fitzbek-Wetter.de
Re: FOSHKplugin - brief introduction
« Reply #79 on: March 28, 2021, 03:51:23 PM »
@olicat

I triend now some features in 0.07:

E.g., saving values to csv:

foshkplugin.conf:

[CSV]
CSV_NAME = /opt/FOSHKplugin/csv-test.csv
CSV_FIELDS = tempc;temp1f;temp2f;temp3f
CSV_INTERVAL = 60

In the output only tempc recorded?:

time;tempc;temp1f;temp2f;temp3f
28.03.2021 21:37:21;8,3;;;
28.03.2021 21:38:29;8,3;;;
28.03.2021 21:39:37;8,3;;;

Question and proposal to the logging:

[Logging]
enable_log = true/false<- Could you add this option?
logfile = /opt/FOSHKplugin/log-foshkplugin.log
rawfile = /opt/FOSHKplugin/raw-foshkplugin.log
sndfile = /opt/FOSHKplugin/snd-foshkplugin.log

Regards,

Matthias



Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #80 on: March 28, 2021, 04:13:57 PM »
Hi!

Quote
CSV_FIELDS = tempc;temp1f;temp2f;temp3f
You can not mix metric and imperial values there. If you would like to save the metric values in the CSV you have to use the metric keys instead:
Quote
CSV_FIELDS = tempc;temp1c;temp2c;temp3c
c = Celsius and f = Fahrenheit

Quote
enable_log = true/false<- Could you add this option?
I will think about it.
At the moment it is implemented in such a way that if a file name is given there, the respective logging is activated. If there is no file name, the corresponding logging does not take place. If you don't need to save the raw lines just disable the raw logging with "rawfile=".

With v0.8 the logging is definitely smarter. There are different log levels (such as with SNMP) that exclude different messages from being written to the log file:
- ALL, as before, all lines are logged
- INFO - all lines except ERROR, WARNING, INFO and OK are suppressed
- WARNING - all lines except ERROR and WARNING and OK are suppressed
- ERROR - only lines with ERROR and OK are output
For reasons of compatibility, ALL is preset - however, I recommend LOG_LEVEL INFO - so everything that was not successful or seems to be informational is logged
You can adjust the log level in runtime via a web browser:
http://ipaddress:port/FOSHKplugin/loglevel=info (or all, warning or error)

Regards, Oliver

Offline lemuba

  • Member
  • *
  • Posts: 48
    • Fitzbek-Wetter.de
Re: FOSHKplugin - brief introduction
« Reply #81 on: March 28, 2021, 04:25:21 PM »
Luft! Working!

time tempc temp1c temp2c temp3c
28.03.2021 22:24:08 8.4 -16.5 20.9 10.6

Br,

Matthias

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #82 on: March 29, 2021, 06:49:37 PM »
Hi!

Another outlook on the upcoming version v0.08 of FOSHKplugin:
  • 50 forwarding destinations for the custom server
  • better logging with log levels
  • Significantly better transmission security thanks to double repetition in the event of an error
  • Support of a few more weather services (wetter.com, weather365.net, wettersektor.de)
  • Export as realtime.txt (Cumulus) and clientraw.txt (Weather Display) - thus support of further programs and services
  • Export of the current data record as a TXT and/or CSV file - will be overwritten on each receive
  • native support of MQTT - data can therefore be forwarded to an MQTT broker
  • Calculation of additional values (cloudbase, sunhours, min/max values with time information)
  • length of the UDP messages can be limited - with longer datagrams, several partial transmissions are sent
  • When using a WH45, a push notification can be sent if the CO2 value exceeds a configurable limit
If you would like to urgently test one of the above functions, please send me a PM.
The public beta test will still take a moment to begin.

Regards, Oliver

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #83 on: April 05, 2021, 02:53:22 AM »
Hi!

Another new feature of the upcoming version v0.08 of FOSHKplugin is the creation of a CSV file for WSWin, which can be read in by WSWin directly - via file monitoring - without going through the complicated manual creation of an X-CSV.
If you would like to test this in advance, please contact me by PM.

Greetings, Oliver

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #84 on: April 25, 2021, 07:55:54 AM »
Hi!

Another new feature that may be helpful is the creation of a daily CSV with the min/max values on a daily basis. The value and time are stored as a file for all minima and maxima of a day.
Have a look at "Saving of daily values in a separate CSV file" (the last point) in the recipes section:

https://www.loxwiki.eu/display/LOXBERRY/FOSHKplugin+-+generic+version#FOSHKplugingenericversion-CSV-dayfile

Oliver

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #85 on: May 01, 2021, 02:46:58 AM »
Hi!

The public beta test for the new version of FOSHKplugin v0.08 has started.

I think there are some really useful new things in there. Have a look to the Version History.
Users who do not urgently need the new functions can stay with the stable version v0.07 for the time being.
The public beta test is intended to find out any errors in use cases that are difficult to recreate by me and the internal test team.
This version has been running stable for a handful of people for a few weeks, so I don't expect any major problems.

To upgrade:
Change via ssh to the directory in which FOSHKplugin is running - according to my recommendations, it could be /opt/FOSHKplugin.
If you run FOSHKplugin as root, you can do the following commands without sudo - if you run FOSHKplugin in a certain user context, the specification of that user would be important so that the permissions are correct:

Code: [Select]
sudo -u username ./generic-FOSHKplugin-install.sh -upgrade generic-FOSHKplugin-0.0.8Beta.zip
sudo -u username ./generic-FOSHKplugin-install.sh -repair

The "repair" is important this time, because FOSHKplugin has to install two new packages via apt/pip to get MQTT support.
Let me know if there're any problems or you need some explanations of the new functions. Most things should already be described on the website.

For first time (or parallel) installation just use this link and the common installation procedure.
LoxBerry users should download and install this version the usual LoxBerry-installation-way instead.

Have fun!

Regards, Oliver

Offline zoomx

  • Member
  • *
  • Posts: 46
Re: FOSHKplugin - brief introduction
« Reply #86 on: May 01, 2021, 10:17:02 AM »
It is possible to add update to databases like MySQL or InfluxDB?

Maybe multiple GW1000 can be managed using theyr passkey so only one FOSHKplugin can manage multiple GW1000.

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #87 on: May 02, 2021, 02:15:02 AM »
Hi!

Quote
It is possible to add update to databases like MySQL or InfluxDB?
It is possible.
But I don't know which DBMS the user is using or what structure the database is in. If I commit to the support of InfluxDB, the desire for MySQL follows. And other users have the MS SQL Server in operation. A bottomless pit ...
In this respect, I only do CSV, ASCII and MQTT at first - everyone can feed the database of their choice from these formats.
However, if at some point I see a personal application here (or the desire of users gets louder), I take a closer look.

Quote
Maybe multiple GW1000 can be managed using theyr passkey so only one FOSHKplugin can manage multiple GW1000.
That would change the structure of the program so massively that it would make more sense to write a new application for it. I've already thought about it - it would be useful to compare values from different sensors or to merge and forward a selection of sensors. For example, if the WS80 on the GW1000-1 delivers a "strange" value, take the data from the WS68 from GW1000-2 instead.
For the server-side separation of weather data (any weather stations deliver data to a central point) I once made a small PHP script for WSWin that stores the data in different CSVs.
This could of course also be expanded as required.
FOSHKplugin is intended to receive data from ONE weather station. However, any number of instances can be operated in parallel.

Regards, Oliver

Offline zoomx

  • Member
  • *
  • Posts: 46
Re: FOSHKplugin - brief introduction
« Reply #88 on: May 02, 2021, 08:34:02 AM »
InfluxDb is different, you don't have to build tables or anything else before putting data in.
The structure is created on the fly when you put data in.
So it would be more simpler.

But you are right, other people will ask for MySql, Postgres ar other classic DBMS.

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #89 on: May 04, 2021, 06:43:26 AM »
Hi!

Quote
It is possible to add update to databases like MySQL or InfluxDB?
While playing on a connection to InfluxDB, I discovered and corrected two errors in the processing of the requests /STRING and /getvalue and extended /SSV and /SSVHDR to include the optional specification of a separator.
An updated beta is available for download.

On the subject of database connection:
So far there is no direct connection to a specific SQL database.
However, there are innumerable ways to make the data from the weather station available to other programs via FOSHKplugin.
In addition to the support of the MQTT standard, which is supported by various connectors, the http interface should be a good choice.
With a web browser you can just try a few things and see what you can do with this data and how you can transfer this data to the database system of your choice:

http://192.168.15.237:8080/STRING?status&minmax&separator=%20
http://192.168.15.237:8080/JSON?status&minmax
http://192.168.15.237:8080/SSV?separator=%20

Individual values can also be queried specifically:
http://192.168.15.237:8080/getvalue?key=tempf

192.168.15.237:8080 from these examples should be replaced by IP address:port of your host running FOSHKplugin.

Telegraf should, for example, be able to insert the data from FOSHKplugin into any DBMS - also in InfluxDB.
With cron, curl and some bash scripting (or corresponding tools under Windows), one should really be able to do anything.

With the script functionality (FWD_EXEC) all output formats of FOSHKplugin can be intercepted, changed and expanded before the actual output. So it is also possible to add values from your own DIY sensors or from other weather stations.

In the recipes section you should find a few more in-depth hints. Some more export formats are described here.
I am very interested in reports of experiences or success reports.

Regards, Oliver

Offline zoomx

  • Member
  • *
  • Posts: 46
Re: FOSHKplugin - brief introduction
« Reply #90 on: May 05, 2021, 05:40:18 AM »
I am using InfluxDB, telegraf and Grafana with configuration files taken from here
https://github.com/Slocan/weatherDashboard
In this way if all Ecowitt upload of my GW1000 and WN1900 push to it using telegraf and I collect all data from them but I can discriminate the data by the PASSKEY. All GW1000 push data to the same place, the same port, all GW1000 has the same configuration.
But I have only one Ecowitt upload per GW1000 so if I push to Influx I cannot push data in other sites. So FOSHKplugin can be a solution.

I wander if it will be possible for many GW1000 to puush data to only one FOSHKplugin. This way you avoid errors, eg on GW1000 pushing data to the wrong FOSHKplugin and adding another GW1000 or another station is more simple sicne the configuration is the same.

Unfortunately it is not simple for others stations different from the Ecowitt. If they use WiFi or ethernet you have the MAC address but this only if the connection is not only in the same lan but also in the same SSID because if you use a WiFi range extender the MAC can change.
Stations connected by USB or serial port must have an identifier assigned in some way.

There are two version of InfluxDB 1.8.x and 2.x, they differs a little. But since 2.0 was compiled only for 64 bit on the olds RaspberryPi you have to use the 1.8x


Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #91 on: May 08, 2021, 05:03:55 AM »
We're on the way ...
;-)

I'm able to feed InfluxDB from FOSHKplugin via telegraf and visualize its data with Grafana.
One can pull the weatherstation data on different ways - I use JSON here:
Code: [Select]
telegraf.conf
[[outputs.influxdb]]
  urls = ["http://127.0.0.1:8086"]
  database = "weatherstation"

[[inputs.http]]
  urls = [
     "http://192.168.15.237:8080/JSON?minmax&status&bool"
  ]
  method = "GET"
  timeout = "5s"
  data_format = "json"
  name_override = "weatherdata"
  tag_keys = [
    "PASSKEY"
  ]
  interval = "30s"

See attached pic.

Currently I'm working on a direct connection to InfluxDB without telegraf. It looks very promising - but I'm not sure if it will make it in v0.08. In any case, the test has been running here since yesterday.

Quote
I wander if it will be possible for many GW1000 to puush data to only one FOSHKplugin.
Of course this is possible. In the standard, FOSHKplugin does not check where the data comes from and processes all incoming data according to the forward rules. Every configured forward is executed - regardless of the origin of the data.

Quote
Unfortunately it is not simple for others stations different from the Ecowitt.
That shouldn't be a major problem. With DIY sensors, you can simply send another PASSKEY along with it: PASSKEY=SENSOR1. In the case of data sent by the station in the WU protocol, there is at least one unique field: ID=WU-Id. I use this ID-field as an optional tag for InfluxDB.

If anyone is interested in the native connection to InfluxDB, please contact me. I could use a few testers, ideas and hints.

Regards, Oliver
« Last Edit: May 08, 2021, 05:40:32 AM by olicat »

Offline zoomx

  • Member
  • *
  • Posts: 46
Re: FOSHKplugin - brief introduction
« Reply #92 on: May 08, 2021, 10:17:14 AM »
Question about CSV dayfuile.

I have this configuration
Code: [Select]
[CSV]
CSV_NAME =
CSV_FIELDS =
CSV_INTERVAL =
CSV_DAYFILE = /var/FOSHKplugin/GW1000_868_1.csv

but none file is created. The folder has these permissions rwxrwxrwx

Where is my mistake?

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #93 on: May 08, 2021, 10:53:37 AM »
Hi!

With the dayfile you just have to be patient - it is written exactly once a day shortly after midnight.
This file only contains the values that are difficult to save in the "normal" CSV file: min/max values of the day and the corresponding times as well as the daily values for precipitation and lightning, (...).

If you want to log the values of each reception as CSV, the settings CSV_NAME, CSV_FIELDS and CSV_INTERVAL would have to be filled.
CSV_NAME specifies the name of the output file and CSV_INTERVAL specifies the interval. If CSV_INTERVAL remains empty, the station's send interval is used automatically.
In CSV_FIELDS you have to enter all field names that you want to have in the CSV. Keep in mind that these names are not the original names. In metric mode these are "converted" names (in --> mm, mph --> kmh, hpa instead of in).
For me (metric) it looks like this:
Code: [Select]
CSV_FIELDS = "PASSKEY;stationtype;dateutc;loxtime;tempinc;humidityin;baromrelhpa;baromabshpa;tempc;humidity;winddir;windspeedkmh;windgustkmh;maxdailygust;solarradiation;uv;rainratemm;eventrainmm;hourlyrainmm;dailyrainmm;weeklyrainmm;monthlyrainmm;yearlyrainmm;totalrainmm;temp1c;humidity1;temp2c;humidity2;temp3c;humidity3;temp4c;humidity4;temp8c;soilmoisture1;soilmoisture2;soilmoisture3;soilmoisture4;soilmoisture5;soilmoisture6;soilmoisture7;soilmoisture8;pm25_ch1;pm25_avg_24h_ch1;tc_co2;humi_co2;pm25_co2;pm25_24h_co2;pm10_co2;pm10_24h_co2;co2;co2_24h;lightning_time;lightning_loxtime;lightning_num;lightning;leak_ch1;leak_ch2;leak_ch3;wh65batt;batt1;batt2;batt3;batt4;batt8;soilbatt1;soilbatt2;soilbatt3;soilbatt4;soilbatt5;soilbatt6;soilbatt7;soilbatt8;pm25batt1;wh57batt;leakbatt1;leakbatt2;leakbatt3;co2_batt;freq;model;dewptc;windchillc;feelslikec;heatindexc;pm25_AQI_ch1;pm25_AQIlvl_ch1;pm25_AQI_avg_24h_ch1;pm25_AQIlvl_avg_24h_ch1;co2lvl;pm25_AQI_co2;pm25_AQIlvl_co2;pm25_AQI_24h_co2;pm25_AQIlvl_24h_co2;pm10_AQI_co2;pm10_AQIlvl_co2;pm10_AQI_24h_co2;pm10_AQIlvl_24h_co2;windspdkmh_avg10m;winddir_avg10m;windgustkmh_max10m;brightness;cloudm;sunhours;country;neighborhood;test;softwareType;stationID;tf_ch1c;tf_batt1;ptrend1;pchange1;wnowlvl;wnowtxt;ptrend3;pchange3;wproglvl;wprogtxt"

Regards, Oliver

Offline zoomx

  • Member
  • *
  • Posts: 46
Re: FOSHKplugin - brief introduction
« Reply #94 on: May 08, 2021, 11:34:43 AM »
Thank you very much.

I have another problem. It seems that configuration to forward to the PWSdashboard is incorrect. The PWSdashboard  is on the same host as the plugin.

The conf is this one
Code: [Select]
[Forward]
FWD_ENABLE = True
FWD_CMT = To PWSdashboard at 192.168.1.35
FWD_URL = 192.168.1.35:80/pswWD/ecowitt/
FWD_INTERVAL =
FWD_IGNORE =
FWD_TYPE = RAWEW
FWD_SID =
FWD_PWD =
FWD_STATUS = True
FWD_EXEC =

in log I found
Code: [Select]
<ERROR> FWD-00: 192.168.1.35:80/pswWD/ecowitt/ post: PASSKEY=
Previous configuration was slighty different
Code: [Select]
FWD_URL = 192.168.1.35/pswWD/ecowittbut I got same error
Code: [Select]
<ERROR> FWD-00: 192.168.1.35/pswWD/ecowitt
I hope this is the last help I ask you.

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #95 on: May 08, 2021, 11:51:56 AM »
Hi!
I would enter a http:// in the FWD_URL.
For me it looks like this:

Code: [Select]
[Forward-11]
FWD_TYPE = EW
FWD_ENABLE = True
FWD_INTERVAL = 30
FWD_CMT = PWSDashboard
FWD_URL = http://192.168.15.236:80/pwsWDxx/data/report/

Otherwise I recommend setting EW as the forward type. At least in the current version, PWSDashboard takes on a few extended fields - generated by FOSHKplugin - which the GW1000 itself does not provide. With RAWEW, only the values received from the weather station are forwarded. At EW also those calculated by FOSHKplugin.

Regards, Oliver

Offline zoomx

  • Member
  • *
  • Posts: 46
Re: FOSHKplugin - brief introduction
« Reply #96 on: May 08, 2021, 01:22:43 PM »
Hi Oliver,

Unfortunately it doesn't work, I tryed some different URLs

These were my tests
Code: [Select]
<ERROR> FWD-00: http://192.168.1.35:80/pswWD/ecowitt/ post: PASSKEY=
<ERROR> FWD-00: http://192.168.1.35:80/pswWD/ecowitt post: PASSKEY=
<ERROR> FWD-00: http://192.168.1.35:80/pswWD/ecowitt/index.php post: PASSKEY=

I beleve that the error is under my eyes but I am not able to see it!


I checked again the path and the passkey.

Edit: tested also these.
Code: [Select]
<ERROR> FWD-00: http://192.168.1.35/pswWD/ecowitt post: PASSKEY=
<ERROR> FWD-00: http://127.0.0.1/pswWD/ecowitt post: PASSKEY=

Edit2: also this
Code: [Select]
<ERROR> FWD-00: http://127.0.0.1/pswWD/ecowitt/ post: PASSKEY=
Edit3
with all my attempts I get 404 in the log So I am sure that apache is reached. But something different happens.

Checked path again and found the error!!!
FWD-00: http://127.0.0.1:80/pwsWD/ecowitt/

I wrote pswWD instead of pwsWD!!!
Sorry for my silly mistake!
« Last Edit: May 08, 2021, 01:45:31 PM by zoomx »

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #97 on: May 10, 2021, 05:26:27 AM »
Hi!

enable_log = true/false<- Could you add this option?
With next public beta of FOSHKplugin (and thus in v0.08) there will be a switch in the Config-file to enable/disable the logging globally:

LOG_ENABLE = True/False

which defaults to True. So you can keep the configuration of the log files and still switch off the logging.

Regards, Oliver

Offline olicat

  • Forecaster
  • *****
  • Posts: 399
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #98 on: May 11, 2021, 10:43:56 AM »
Hi!

There's a updated version of FOSHKplugin v0.08 available.
Since last public Beta there're some minor changes but a new key feature: direct support of InfluxDB!

Running a local InfluxDB-server and locally installed Grafana you may create a fine dashboard yourself. Easily!
You may arrange all graphs or compare any value with others and you are EVEN able to include sensor values from other systems that provide data according to InfluxDB in your considerations.
This makes it very easy to compare different weather stations or sensors of different types.
For the test (and because I've always wanted to evaluate the quality of the TFA shield) I compared the TFA weather protection against the original WH65 here as metric or here in imperial.
In summary: The TFA-Shield may protect against rain and wind. In direct sunlight, however, it performs significantly worse (5K!) than the shield built into the WH65.

Adding another sensor to this diagram is just a few clicks!
The chronological sequence can also be changed very easily with a click. So especially for people who would like to compare the various anemometers or temperature sensors with each other, InfluxDB together with Grafana or Chronograf is an extremely helpful tool. And FOSHKplugin can provide this data to the database.

Among the minor changes:
There's a new switch Logging\LOG_ENABLE to enable/disable the complete logging. The STRING output function did not work quite as expected. getvalue also apparently had problems finding keys from the other measurement system. I have now used the revision immediately to give all requests (where it makes sense) the possibility to also include minmax or status as an option and to change the separator via "separator=". The bool option is also new to output the Boolean values 0/1 as False/True.
A few examples to help you developing ideas about what is possible (replace IP address and port with your values):

get all values as JSON in metric system with True/False as state:
http://192.168.15.237:8080/JSON&minmax&boolstatus&units=m

get a string output for all metric values with a separator " - " between fields
http://192.168.15.237:8080/STRING&minmax&boolstatus&units=m&separator=%20-%20

same as UDP-output but for imperial values:
http://192.168.15.237:8080/UDP&minmax&boolstatus&units=e&separator=%20-%20

download the status only and save it locally with linefeed as status.txt
wget http://192.168.15.237:8080/FOSHKplugin/status/bool/separator=%0A -O status.txt

create a plain text file with all known data (each per line) from Windows cmd:
curl http://192.168.15.237:8080/FOSHKplugin?boolstatus^&minmax^&bool^&units=e^&separator=%0A -o complete-e.txt

just get the current state of todays (so far) max. temperature of sensor #4
curl http://192.168.15.237:8080/getvalue?key=temp4c_max -o temp4c_max.txt

To upgrade:
Change via ssh to the directory in which FOSHKplugin is running - according to my recommendations, it could be /opt/FOSHKplugin/.
If you run FOSHKplugin as root, you can do the following commands without "sudo -u username" - if you run FOSHKplugin in a certain user context, the specification of that user would be important so that the permissions are correct:

Code: [Select]
sudo -u username ./generic-FOSHKplugin-install.sh -upgrade generic-FOSHKplugin-0.0.8Beta.zip
sudo -u username ./generic-FOSHKplugin-install.sh -repair

The "repair" is important this time, because FOSHKplugin has to install a new package via apt/pip to get InfluxDB support.
Let me know if there're any problems or you need some explanations of the new functions. Most things should already be described on the website.

For first time (or parallel) installation just use this link.
LoxBerry users should download and install this version the usual LoxBerry-installation-way instead.

Have fun!

Regards, Oliver
« Last Edit: May 11, 2021, 11:33:59 AM by olicat »

Offline zoomx

  • Member
  • *
  • Posts: 46
Re: FOSHKplugin - brief introduction
« Reply #99 on: May 11, 2021, 05:30:54 PM »
 :sad: Link goes to a 404 page.
But if I remove the Beta from the link it works
https://foshkplugin.phantasoft.de/files/generic-FOSHKplugin-0.0.8.zip
 :grin:

Edit: link updated so my link doesn't work anymore.
« Last Edit: May 12, 2021, 03:39:34 AM by zoomx »