I have just found, that actually it was bug. archive_interval was fixed in version 3.9. I use version 3.8.
Dne pátek 3. ledna 2020 15:07:59 UTC+1 Miloslav Pawlica napsal(a): > > Actually it is not. I did that, restarted weewx and nothing has change. I > think that I'm starting to understand that. > > Pooling interval is only used for plugins like RapidFire for WU. So the > best option to lower stress put on station is to leave archive_interval as > default 30 minutes, extended pooling interval from 60s to more and then use > some plugin to export live-pooled data. If we do not use RapidFire or > similar plugin, pooling interval has not really purpose, so you can set it > to longer period to avoid unnecessary usb lockups and weather stations > restarts. I believe that this will significantly extend station lifespan. > > Actually it is funny, how much problems we can get with USB connected > weather stations. This explains why are stations Vendors slowly leaving > this solution and moving to cloud enabled devices. I do not see real > benefit of it for power users, except less hardware problems and conflicts. > > > Dne pátek 3. ledna 2020 14:49:14 UTC+1 Thomas Keffer napsal(a): >> >> The key is to change option record_generation from 'hardware' to >> 'software': >> >> [StdArchive] >> >> record_generation = software >> >> -tk >> >> On Fri, Jan 3, 2020 at 5:03 AM Miloslav Pawlica <[email protected]> >> wrote: >> >>> Hi, I hope that somebody can explain it to me. >>> >>> I use weewx for 3 years now. My first weather stations WH1080 just died. >>> Its memory is completely dead, do not stores any data and Weewx is not able >>> communicate with station over usb. So I got new station. It is again >>> WH1080. >>> >>> With same configuration as before, like 5 minutes archive_interval the >>> station will again die in 3 years. I would like to avoid that. Therefore I >>> have deiced to use archive_interval 30 minutes, to save memory from too >>> many writes.Still I would like to update date by weewx more often then >>> every 30 minutes. >>> >>> If I understand correctly Weewx is able to read just live data from >>> Weather station, so there should be no real reason to use internal memory >>> of device. So when software data generation is configured, pooling is set >>> to 10 minutes weewx should simply created its outputs every 10 minutes from >>> its own software database located on server and then push data to ftp. >>> Still, it does not work like this. Whatever I configure, weewx ignores it >>> and use station hardware archive_interval and output is generated only >>> every 30 minutes. >>> >>> My question is, why does weewx has option like archive_interval if it is >>> ignored or what is the reason for pooling from station every 60 seconds, >>> when archive interval is much longer? >>> >>> I was reading all posts here regarding weewx and Fineoffset stations. >>> Still I do not see a way how to make it work better. >>> >>> Thanks :o) >>> >>> -- >>> 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]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/33ff8dc2-5cf9-49d2-a948-807ebb48c714%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/33ff8dc2-5cf9-49d2-a948-807ebb48c714%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/be4a1a1e-59f8-4c7b-8be3-aa8f64c651ed%40googlegroups.com.
