> On Jan 16, 2026, at 19:05, Greg Troxel <[email protected]> wrote: > > Vince Skahan <[email protected]> writes: > >> Using ecowitt as an example: >> >> - you might have a gw3000 driver which backfills from SD card >> - or you might have a driver that backfills from API query of the >> ecowitt server >> - or you might want a null driver that does nothing at all (no backfill) > > That's a great argument for having a backfill class definition and three > implementations (in separate .py files) and then config to say which one > you want, with the code that calls it being simple. Basically I'm > saying that traditional module design tames the complexity, or at least > encapsulates it and prevents extra spaghetti connections.
for a long time i have wanted to write a standalone 'weectl upload' that is analogous to the 'weectl import'. the upload would take data from the weewx database and push it to the desired data storage. my specific use case is influx, but any uploader that supports other-than-just-live-data is a candidate. think wunderfixer, but generically written to use an uploader to drive it. a 'weectl backfill' would be a similar, useful tool. that would pull data from some source, whether it is online or hardware, and put the data into the weewx database. this is a bit more tricky, since the source could be defined by an uploader *or* a driver. but it probably just means massaging the api a little bit for each. m -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-development/163A2B44-27F8-4EB8-A819-B7380007F9F0%40gmail.com.
