Since my last message, the humidity was displayed as 48% (last 3 hours) even though we had rain and the direct sensor reading was 94%.
Just out of desperation I stopped the weewx engine and restarted and the humidity updated. So for some reason it only updates when the weewx engine starts. On Tuesday, 23 July 2019 13:39:42 UTC+2, Andrew Milner wrote: > > that is correct. BUt you really should not see much difference between > polling values if you are polling at 2.5 seconds!! But the value which is > archived will be the average value over the 3 minute archive period. > > If you are displaying the LOOP packets - the values written to the > database are in the REC packet - which should occur once every 3 minutes - > and they are ALL averaged values for values received in the LOOP packets of > the interval - pressure, temperature, humidity etc etc > > On Tuesday, 23 July 2019 14:32:17 UTC+3, Danie Cillie wrote: >> >> The archive period you refer to, is that the value set in the weewx.conf >> file? I have reduced that to 240 or 3 minutes. If I understand you >> correctly, the average is over the 3 minute period until the next write is >> done to the database. >> If I run weewxd directly, (sudo weewxd weewx.conf) the LOOP values are >> correct. >> Then I assume the values read (poll_interval is 2.5 seconds) in the 3 >> minute period is averaged and written to the database, is that correct? >> I'll monitor the readings over a few days to see if I can make any sense >> out of this. >> >> On Tuesday, 23 July 2019 11:45:46 UTC+2, Danie Cillie wrote: >>> >>> It will stay at a certain value for example 51% for a long time even >>> though the loop value has changed drastically. Both the loop and archive >>> record values are correct when displayed on the terminal but that is not >>> what is written to the database. >>> How does one determine the archive period over which the values are >>> averaged? >>> >>> On Tuesday, 23 July 2019 11:33:33 UTC+2, Andrew Milner wrote: >>>> >>>> how do you know it is 'stuck'?? the archived value is the AVERAGE of >>>> readings received during the archive period. What values are displayed >>>> that you say are correct - the loop value or the archive record value?? >>>> Remember that humidity does not change very quickly. >>>> >>>> On Tuesday, 23 July 2019 12:15:20 UTC+3, Danie Cillie wrote: >>>>> >>>>> Morning, >>>>> >>>>> I use a Raspberry Pi with the GroveWeatherRack and sensors and weewx. >>>>> >>>>> The grovePi driver sends the data directly to weewx. >>>>> >>>>> The LOOP data and the archive data as printed on the terminal when >>>>> weewxd runs is correct and updates correctly, but the humidity data is >>>>> stored correctly the first time in the database and then gets stuck. >>>>> Sometimes after a long time (hours) it changes to a new value and sticks >>>>> to >>>>> that again. >>>>> >>>>> I can not understand why the data is read and displayed correctly but >>>>> not stored in the database. >>>>> >>>>> The data on this page illustrates what the problem is >>>>> https://www.pwsweather.com/obs/IBLUERID2.html >>>>> >>>>> Please find the config file and log file attached. >>>>> >>>>> Any suggestions appreciated. >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d66520ec-257d-4438-9207-dc4927f57e1b%40googlegroups.com.
