Closed ArendPWS closed 3 years ago
I think the behaviour of weewx has been changed from my early testing (mostly using an early weewx 4.0 beta build) as I had to change record_generation to hardware. I'll leave this issue open for the moment. At the next release (none planned in the short term) I'll update the readme.txt with your work around. The other workaround (if your database is up to date) is to clear the data buffer on the console. If I'm testing and likely to restart weewx multiple times I backup the database first and then clear the console before starting my testing.
I have added a note in the readme.txt for version 0.9 with the no_catchup = True work around
First of all: thank you for providing this driver, it works very well.
I ran into some issues when using your driver, but it could als be related to the behaviour of WeeWX, I am not sure.
In your readme.txt you write:
When I look at the original WeeWX-configuration file it reads:
https://github.com/weewx/weewx/blob/master/weewx.conf
But it doesn't matter which mode I use, weewx starts downloading the memory contents from the console anyway. It makes no difference which configuration option I am using. I have no idea why my configuration is behaving differently. For testing purposes it can be somewhat annoying that with each restart all memory contents is downloaded each time. Accidentally I found a way to (temporary) stop this downloading behaviour by means of an undocumented weewx option in [StdArchive]. Adding
[StdArchive] no_catchup = True
solved it. https://groups.google.com/g/weewx-user/c/z94fmNeuEIc/m/GRdT09e6AQAJ