Hi, Cameron. Thanks, but it's not the reason you think. Now weewx wind data correctly downloads the WMR300, with your new driver (wmr300-v19rc6 + f3.py). But I have another problem, one day this month there has been no rainfall data and it has rained a lot. I have backed up the database, I deleted all the data for this month and it was reinserted when we started weewx. Still I have data loss so I have to check the rain gauge.
Greetings and thanks. El sábado, 13 de octubre de 2018, 3:04:30 (UTC+2), Cameron D escribió: > > Juan, > I presume you are referring to the WMR300 and missing wind speed. > If you have a 5-minute archive period then the console storage will > increase by close to 1% per day. > > If you use the default history clear at 20% then you have *up to* 20 > days, however it is not possible to *partially *clear the history, so > depending when the buffer was cleared, you might or might not have much > data. > > I tend to set it at 6% and I am not certain which setting you are using. > To be more sure of saving archive/history you could set the parameter: > history_limit = 90 > > My rule would be - if the live data is working well then use a low > percentage for: > > 1. to leave an empty buffer in case the computer goes down for a long > time > 2. each clear is shorter and less interruption to live data flow > > but use a high percentage if: > > 1. your live data is unreliable and you need to go back over some days > worth of data. > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
