LoxBerry-Plugin: FOSHKplugin - Wettergateway Froggit DP1500 / Ecowitt GW1000 anbinden
Einklappen
X
-
I'm not really sure what kind of forward I am using. I have my gateway configured with this:
and the plugin with this:
.3 is Miniserver, .5 is Loxberry, .35 is GW2000
is this a special forward or automatic configuration?
So anyway, I wanted to have that data also under generic names in case I would add WH40 to my system in the future. But I might misunderstood their purpose.
Shell I just use the input in the left column on previous screenshot and forget about the inputs in the right column?Einen Kommentar schreiben:
-
Hi!
Your FWD_REMAP line is correct (I also corrected mine above).
Have you set up a special forward to send the data to Loxone via UDP?
Or do you use the automatic function of sending to Loxone - without a special forward?
The FWD_REMAP only works with forward destinations. When sending to Loxone, I saw no need for remapping, as you can determine yourself at the destination which data you process and how.
Therefore, I do not understand why you want to remap the fields at all.
But:
If you change UDP_ENABLE in the config file to False and create a separate forward like this:
the remap function should work.Code:[Forward-1] FWD_ENABLE = True # to deactivate this forward temporarily just set to False instead of deleting the URL (default: True) FWD_CMT = this forward sends the converted data via UDP to the destination:port FWD_URL = 192.168.15.255:12355 # URL of destination - broadcast datagrams on port 12355 FWD_TYPE = UDP # WU/UDP/LD/RAW/EW/RAWEW/RAWUDP/AMB/RAWAMB/WC/MT/AWEKAS/WETTERCOM/WEATHER365/REALTIMETXT/CLIENTRAWTXT/CSVFILE/TXTFILE/WETTERSEKTOR/MQTTMET/MQTTIMP FWD_SID = FOSHKweather # username for forward if necessary (SensorID for luftdaten.info) FWD_STATUS = False # FWD_TYPE=UDP only: if set to True attach current status on each outgoing datagram (default: False) FWD_WARNINT = 10 # threshold of unsuccessful forward attempts before warning FWD_REMAP = rainratein=@rrain_piezo,eventrainin=@erain_piezo,h ourlyrainin=@hrain_piezo,dailyrainin=@drain_piezo, weeklyrainin=@wrain_piezo,monthlyrainin=@mrain_pie zo,yearlyrainin=@yrain_piezo
But it is not really necessary to set up a special UDP forward and I see no reason why you should change any field names for Loxone.
Can you explain what you expect from this?
Regards, Oliver
Einen Kommentar schreiben:
-
olicat Thanks, I've tried this
and this (my templates expects names with mm so I've tried to change in to mm)Code:root@loxberry:/opt/loxberry# cat config/plugins/foshkplugin/foshkplugin.conf|grep REMAP FWD_REMAP=rainratein=@rrain_piezo,eventrainin=@erain_piezo,hourlyrainin=@hrain_piezo,dailyrainin=@drain_piezo,weeklyrainin=@wrain_piezo,monthlyrainin=@mrain_piezo,yearlyrainin=@yrain_piezo FWD_REMAP=rainratein=@rrain_piezo,eventrainin=@erain_piezo,hourlyrainin=@hrain_piezo,dailyrainin=@drain_piezo,weeklyrainin=@wrain_piezo,monthlyrranin=@mrain_piezo,yearlyrainin=@yrain_piezo
Code:root@loxberry:/opt/loxberry# cat config/plugins/foshkplugin/foshkplugin.conf|grep REMAP FWD_REMAP=rainratemm=@rrain_piezo,eventrainmm=@erain_piezo,hourlyrainmm=@hrain_piezo,dailyrainmm=@drain_piezo,weeklyrainmm=@wrain_piezo,monthlyrainmm=@mrain_piezo,yearlyrainmm=@yrain_piezo FWD_REMAP=rainratemm=@rrain_piezo,eventrainmm=@erain_piezo,hourlyrainmm=@hrain_piezo,dailyrainmm=@drain_piezo,weeklyrainmm=@wrain_piezo,monthlyrainmm=@mrain_piezo,yearlyrainmm=@yrain_piezo
But nothing works. Im running out of ideasEinen Kommentar schreiben:
-
Hi!
You have to use this remap scheme:
Within FOSHKplugin, first the remapping and then the conversion into the metric system (with it own variable names) takes place.Code:rainratein=@rrain_piezo,eventrainin=@erain_piezo,hourlyrainin=@hrain_piezo,dailyrainin=@drain_piezo,weeklyrainin=@wrain_piezo,monthlyrainin=@mrain_piezo,yearlyrainin=@yrain_piezo
Only afterwards the output takes place via UDP (with metric variable names).
Oliver -
I've tried again with common names without @ (as they do not exist yet):
Code:FWD_REMAP=rainratemm=@rrain_piezomm,eventrainmm=@erain_piezomm,hourlyrainmm=@hrain_piezomm,dailyrainmm=@drain_piezomm,weeklyrainmm=@wrain_piezomm,monthlyrainmm=@mrain_piezomm,yearlyrainmm=@yrain_piezomm FWD_REMAP=rainratemm=@rrain_piezomm,eventrainmm=@erain_piezomm,hourlyrainmm=@hrain_piezomm,dailyrainmm=@drain_piezomm,weeklyrainmm=@wrain_piezomm,monthlyrainmm=@mrain_piezomm,yearlyrainmm=@yrain_piezomm
and still no successEinen Kommentar schreiben:
-
olicat my mistake, coping to clipboard the raw in UPD monitor was also coping Hex data and Objects column. So they are actually not doubled (see full UDP monitor text data below).
But I still have a problem with remaping. I've corrected it based on documentation to this (added missing @ before names:
Code:root@loxberry:/opt/loxberry# cat config/plugins/foshkplugin/foshkplugin.conf|grep REMAP FWD_REMAP=@rainratemm=@rrain_piezomm,@eventrainmm=@erain_piezomm,@hourlyrainmm=@hrain_piezomm,@dailyrainmm=@drain_piezomm,@weeklyrainmm=@wrain_piezomm,@monthlyrainmm=@mrain_piezomm,@yearlyrainmm=@yrain_piezomm FWD_REMAP=@rainratemm=@rrain_piezomm,@eventrainmm=@erain_piezomm,@hourlyrainmm=@hrain_piezomm,@dailyrainmm=@drain_piezomm,@weeklyrainmm=@wrain_piezomm,@monthlyrainmm=@mrain_piezomm,@yearlyrainmm=@yrain_piezomm
Then I've restarted plugin and still get only this:
so no data for values such as rainratemm, etc. What am I missing here?Code:SID=FOSHKweather PASSKEY=533791E575xxxxxxxxxxxxxxxxxxx stationtype=GW2000A_V2.2.4 runtime=122006 dateutc=2023-06-23+19:21:52 loxtime=456787312 tempinc=24.0 humidityin=71 baromrelhpa=1022.59 baromabshpa=1005.59 tempc=21.8 humidity=63 winddir=242 windspeedkmh=0.0 windgustkmh=6.12 maxdailygust=10.44 solarradiation=0.24 uv=0 rrain_piezomm=0.0 erain_piezomm=4.09 hrain_piezomm=0.0 drain_piezomm=4.09 wrain_piezomm=4.09 mrain_piezomm=4.09 yrain_piezomm=4.09 ws90cap_volt=5.1 ws90_ver=133 wh90batt=3.28 freq=868M model=GW2000A interval=60 isintvl=61 isintvl10=61 dewptc=14.4 windchillc=21.8 feelslikec=21.8 heatindexc=21.7 windspdkmh_avg10m=2.9 winddir_avg10m=236 windgustkmh_max10m=6.12 brightness=30.4 sunhours=6.75 ptrend1=2 pchange1=1.6 wnowlvl=3 wnowtxt=sunny ptrend3=-1 pchange3=1.1 wproglvl=5 wprogtxt="nice for a long time"
Zuletzt geändert von TomekWaw; 23.06.2023, 21:42.Einen Kommentar schreiben:
-
These names going to be with mm suffix.
I guess you see them twice because the Loxone-UDP monitor shows them (also) as the Loxone-variables - the names of the virttual inputs.
Regarding the remap function have a look to the help pages - the input names may be different - so just use in instead of mm.
Oliver -
potentiell gabs auch weniger Fälle, weil es auch einige gab, die dann lieber gleich komplett neuinstalliert haben, statt auf langwierige Fehlersuche zu gehen (denke der Fehler wird durch eine ältere Zwischenversion o.ä. schon länger bei mir drin gewesen sein https://www.loxforum.com/forum/proje...323#post391323) -
Gerrit, danke fuer die Info.
Ich hoere zum ersten Mal von diesem Problem. Wenn aber auch andere Plugins betroffen waren, liegt ein uebergeordnetes Problem nahe.
Als Rat an die Nutzer kann man dann wohl beim Upgrade des LoxBerry von v2 auf v3 die moeglichst zeitnahe Pruefung, ob alle Plugins funktionieren, zusammenfassen.
Vielleicht sollte ich kuerzere Release-Zyklen einfuehren, damit haeufiger ein Update gemacht werden kann ...
;-)
Oliver
Einen Kommentar schreiben:
-
ich hatte erst spät festgestellt, dass das FOSHK Plugin nach dem Loxberry Update von 2.2.2.2 auf 3.0.0.6 nicht mehr funktioniert hatte. Ein Restart des Plugins (Über WebFE) hatte nicht geholfen. Die Links zu den 3 Logfiles konnten alle nicht aufgelöst werden = keine Logfiles vorhanden.
Ich hab dann das Plugin neu bzw. drüber installiert (gleiche 0.0.9), danach funktionierte das Plugin wieder normal. Da es auch mit anderen Paketen beim Loxberry-Update auf v3 ein Problem gab (Ursache war root-folder hatte falsche Rechte - loxberry User statt root), gab es eventuell auch bei dem Update der FOSHK Pakete beim Loxberry v3 Update ein Problem. Durch die nochmalige Installation wurde es dann repariert.Zuletzt geändert von Gerrit; 23.06.2023, 15:45.Einen Kommentar schreiben:
-
Thanks! Are those names going to be with mm suffix or without in the future?
What values should I use?
I see drain_piezomm=4.09 and FOSHK-drain_piezo [4,09] in the UDP monitor (and all data in pairs for that) and I'm a bit confused
Btw, strangely I'm unable to remap those values to translated names as you suggested on wxforum (but with translated names with mm not in[ch])
I've added
In sections [Forward] and [Forward-1] and restarted plugin to reread conf file. But still translated data don't show in the UDP monitor nor in the ConfigCode:FWD_REMAP = rainratemm=@rrain_piezomm,eventrainmm=@erain_piezomm,hourlyrainmm=@hrain_piezomm,dailyrainmm=@drain_piezomm,weeklyrainmm=@wrain_piezomm,monthlyrainmm=@mrain_piezomm,yearlyrainmm=@yrain_piezomm
Zuletzt geändert von TomekWaw; 23.06.2023, 14:00.Einen Kommentar schreiben:
-
Hi!
Thanks for the info. You have found the error!
It was not noticed until now because very few users of a WS90 use its rain values (they are too bad).
I have fixed the error here for v0.10.
Thank you!
Oliver
Einen Kommentar schreiben:
-
And by the way, I have v0.0.9 that's why conversion doesn't work in my setup (I've read that it will be fixed in v0.0.10).
But piezo data is enough for me as I currently don't plan to use other rain sensorEinen Kommentar schreiben:
-
Hi!
So the data is there but you can't pull these values out of the UDP stream? This is really strange! Never seen this before.This is what UDP monitor shows I am receiving:
Perhaps Loxone has problems with the "_" in the variable name?
Beside this: you should calibrate your relative pressure ...
Oliver
Einen Kommentar schreiben:
Einen Kommentar schreiben: