Hello all,
I have a TFA rain meter in operation, type TFA 30.3148. Works fine! Sometimes you just want it to rain to see it work .
When I look at the devices, I see that the data it reports has two values:
Rain-WWH-Buiten Rain TFA 1190;42.7
The first value corresponds with the amount of rain, in my case 11.9 mm (the bucket in my rain meter tipped 17 times, resolution is 0.7 ml).
My question is about the second value... I explored the internet for an answer, no success. Any idea's? ?
update: I looked at the value again and it now says:
Rain-WWH-Buiten Rain TFA 980;43.4
The measured amount is 12.6 mm
The first figure is the *rate* 9.8 mm per hour... still no clue about the second value...
edgarhildering wrote: ↑Sunday 22 July 2018 15:39
Hello all,
I have a TFA rain meter in operation, type TFA 30.3148. Works fine! Sometimes you just want it to rain to see it work .
When I look at the devices, I see that the data it reports has two values:
Rain-WWH-Buiten Rain TFA 1190;42.7
The first value corresponds with the amount of rain, in my case 11.9 mm (the bucket in my rain meter tipped 17 times, resolution is 0.7 ml).
My question is about the second value... I explored the internet for an answer, no success. Any idea's? ?
update: I looked at the value again and it now says:
Rain-WWH-Buiten Rain TFA 980;43.4
The measured amount is 12.6 mm
The first figure is the *rate* 9.8 mm per hour... still no clue about the second value...
--Edgar
It is the total rainAmount for that day as calculated by domoticz.
Hi @waaren, that is a bit strange, since the value is *reported to* domoticz straight from the rain meter. My guess is - since the amount is always a multiple of 0.7 that it is the total mm of rain of all measurements since the last reset of the meter...
the last reported values are
Rain-WWH-Buiten Rain TFA 0;44.8
(yes, it has stopped raining! )
the overall score of today is 14 mm, compared to the measurement 1190;42.7 (11.9 mm) and 980;43.4 (12.6 mm) you see the increase. This morning (the sun was still out) the values were 0;30.8. The measured amount of rain up to this morning could well be 30.8, that is a reasonable amount.
I will keep tracking my meter, come rain, come shine
json.htm?type=command¶m=udevice&idx=IDX&nvalue=0&svalue=RAINRATE;RAINCOUNTER
IDX = id of your device (This number can be found in the devices tab in the column "IDX")
RAINRATE = amount of rain in last hour in [mm x 100]
RAINCOUNTER = continues counter of fallen Rain in [mm]
In the domoticz.db you can see what happens with the values in the raindevice every 5 minutes and daily.
cd domoticzdir
sudo cp domoticz.db tempdatabase.db
sudo sqlite3 tempdatabase.db
.headers on
.tables
select sValue from Devicestatus where ID = 128; -- 128 is my raindevice IDX. Yours is probably different
select * from rain where deviceRowID = 128; -- 5 minute summary
select * from rain_calendar where deviceRowID = 128; -- daily summary
The 'usual' numeric info from Domoticz's sensors is 'Actual'/Latest', and for some types it is also reported (e.g. under svalues) as for LastDay, for LastHour and/or Cumulative. In the SQLite database a saving occurs every 5 minutes.
For meteo-report-uploading I need to calculate/report various running tendency-values over the last x minutes, with x varying between 10 minutes upto 1 or 3 hours.
First need is for precipitation/rain and for air pressure.
Domoticz certainly has not been developed with this functionality in mind, but perhaps it can be 'tweaked' to do the job.
Software version0 to get the variation over 10 minutes seems rather easy, especially if a cumulative coutervalue is available [but 'devil in the details']: Step1 = read the required Domoticz-value and save as User Variable
That Step1 probably can easily be realized with the standard features of RFLinkGateway and a script under application of JSON-calls, svalues etc.. Step2 = wait 10 minutes and read same Domoticz-value Step3 = Compare the read and saved values => difference = jump / tendency => output-value Step4 = Save the latest read value as replacement User Variable for the earlier saved value
Repeat this process for all required sensors with an interval of 10 minutes.
Next version1 is a bit more complicated, aiming at calculation of average, minimum and maximum over those same 10 minutes, which demands that intermediate values are available: Step5= for the intermediate values a frequent/periodic read-out of the sensor-values (interval preferably 1minute):
that Step5 possibly can still be realized with the standard features of RFLinkGateway and a script under application of JSON-calls, svalues etc..
[Whether in this way you get meaningfully valid data, is another matter, because the reading interval may be something different than the measuring interval of the sensor] Step6 = Saving & shifting of the collected intermediate values in a kind of shift-register or database as function of time covering the required 10 minutes.
Because you need to store N sensor-values * T intervals, use of User Variables is not really 'handy', and a database is more appropriate. Step7 = Reading of saved values & processing => output of 'values-over-last-10minutes'
Repeat this process for all required sensors with an interval of 1minute, with output every 10 minutes.
For a realisation for version1 I have sidelooked at the RRA of RRDTool, which functionally has comparable processes, but don't yet see how to translate or apply that RRDTool construction.
Anybody with a more or less proven design & script(s) to get such version1 'values-over-last-xminutes'?
Perhaps one of the developers of the graphics' scripts of Domoticz having hints?
Set1 = RPI-Zero+RFXCom433+S0PCM+Shield for BMP180/DS18B20/RS485+DDS238-1ZNs
Set2 = RPI-3A++RFLinkGTW+ESP8266s+PWS_WS7000
Common = KAKUs+3*PVLogger+PWS_TFA_Nexus plus series of 'satellites' for dedicated interfacing, monitoring & control.
. 
?
)