Page 1 of 1
'dead' sensor showing figues in actual and day1
Posted: Sun Mar 23, 2008 4:23 pm
by skyewright
As mentioned elsewhere my RFXCOM has been picking up occasional signals from a distant neighbour's anemometer. The last such signal was received 21 hours ago (not a problem!), but on a template based html page, that sensor is still showing values for
actual_wind2_speed_mph
actual_wind2_dir_en
actual_wind2_gustspeed_mph
actual_wind2_dir_en
day1_wind2_speed_mph
day1_wind2_maindir_en
day1_wind2_gustspeedmax_mph
day1_wind2_maxspeeddir_en
and
day1_wind2_gustspeedmax_time (which shows a time from yesterday morning)
Is that expected behaviour?
The 'last60m' figures are blank, as I'd expect.
Re:'dead' sensor showing figues in actual and day1
Posted: Sun Mar 23, 2008 8:58 pm
by skyewright
skyewright wrote:
The day1 values disappeared when the most recent signal was over 24 hours ago.
actual is still showing values.
Re:'dead' sensor showing figues in actual and day1
Posted: Mon Mar 24, 2008 6:34 pm
by admin
As long as the logger is running it collects every thing it gets. Once seen some sensors it reports the last seen values for this until new values occur.
At the moment there is no such concept like invalidating sensors that have not had any signals in the last x hours/minutes.
restarting the logger will make them fade... until you get a reading for them again.
Re:'dead' sensor showing figues in actual and day1
Posted: Tue Mar 25, 2008 12:51 pm
by skyewright
admin wrote:As long as the logger is running it collects every thing it gets. Once seen some sensors it reports the last seen values for this until new values occur.
What I was reporting was a difference in behaviour by different 'time buckets' for what seemed to be an equivalent situation.
i.e. If there are no signals from a sensor in the current 60 minutes, the relevant last60m values report as blank (assuming [blank_the_unknown] is used). That seems quite reasonable.
However, the day1 equivalents still report a value even if there has been no signal in the current day.
Is that explanation any clearer?
Re:'dead' sensor showing figues in actual and day1
Posted: Tue Mar 25, 2008 1:45 pm
by skyewright
skyewright wrote:Is that explanation any clearer?
To illustrate, I've set up a simple table at:
http://www.david-wright.co.uk/demo/temp/meteohub.html
The 'Other' column has cells for the neighbour's rain gauge and anemometer.
At the time of writing there has been no signal from the 'Other' anemometer since the v2.2 install/reboot. Gust Speed/Other show blank for 'actual' and 'last 60 mins', but 'today' does show a value (which would be reasonable if there had been a signal today, but there hasn't).
If it wasn't that I'd included a date in the Gust Speed / Other cell for the 'today' section I would be left thinking that the 'Other' gauge had recorded a speed of 17.9 'today'.
Is that any clearer.