You override the archive interval by switching to software record generation. (record_generation = software). If WeeWX is not doing this, there is something else wrong. Could you please show the log with debug=1, from when you start up WeeWX? It will show details of what record generation it is using.
As for your desire to replicate the last data point, WeeWX does not do this for two reasons: drivers do not "make up" data, and they try not to use caching <http://weewx.com/docs/customizing.htm#General_guidelines>. So, this is not part of the shipping version of WeeWX. However, the WeatherUnderground RESTful services does something similar, so writing an extension to do this would be super easy [NOT TESTED]: import weewx.restx class GapFiller(StdService): def __init__(self, engine, config_dict): super(GapFiller, self).__init__(engine, config_dict) self.cached_values = weewx.restx.CachedValues() self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record) def new_archive_record(self, event): self.cached_values.update(event.record, event.record['dateTime']) event.record = self.cached_values.get_packet(event.record['dateTime'], 600) -tk On Sat, Nov 3, 2018 at 2:32 AM Per Edström <[email protected]> wrote: > No, I have 300 seconds = 5 minutes as archive interval but the WMR200 > overrides it. > > I tried software generation but Weewx still stores every minute (I guess > the HW-interval can not be overridden in weewx.conf): > > Nov 3 10:20:36 RPi-3B_Skalet weewx[9980]: ftpgenerator: ftp'd 33 files in > 13.16 seconds > Nov 3 10:21:16 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:21:00 CET (1541236860) to database 'weewx.sdb' > Nov 3 10:21:16 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:21:00 CET (1541236860) to daily summary in 'weewx.sdb' > Nov 3 10:22:16 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:22:00 CET (1541236920) to database 'weewx.sdb' > Nov 3 10:22:16 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:22:00 CET (1541236920) to daily summary in 'weewx.sdb' > Nov 3 10:23:17 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:23:00 CET (1541236980) to database 'weewx.sdb' > Nov 3 10:23:17 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:23:00 CET (1541236980) to daily summary in 'weewx.sdb' > Nov 3 10:24:17 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:24:00 CET (1541237040) to database 'weewx.sdb' > Nov 3 10:24:17 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:24:00 CET (1541237040) to daily summary in 'weewx.sdb' > Nov 3 10:25:17 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:25:00 CET (1541237100) to database 'weewx.sdb' > Nov 3 10:25:17 RPi-3B_Skalet weewx[9980]: manager: Added record > 2018-11-03 10:25:00 CET (1541237100) to daily summary in 'weewx.sdb' > Nov 3 10:25:18 RPi-3B_Skalet weewx[9980]: cheetahgenerator: Generated 15 > files for report StandardReport in 1.18 seconds > > I would prefer that the DB-writing was made more seldom i.e. at the > archive interval. Weewx could keep these 1-minute-values in memory until DB > is to be written. > > Also, as this thread was started as, I would prefer Weewx to take the last > received sensor value if there is one expected but missing i.e. the WMR200 > is not presenting it in the 1-minute-pull.. > > -- > 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. > -- 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.
