Hmm, a service that performs catchup for the gw3000
Or A driver that loads MQTTSubscribe’s MQTT processing Sounds like fun projects I might have to get a gw3000. Where is the api doc? I should be able to write a lot of the code without the hardware. rich On Friday, 16 January 2026 at 11:37:26 UTC-5 Vince Skahan wrote: > Is it possible to break up monolithic drivers into components that do > pieces of the puzzle ? > > Using ecowitt as an example, the vendor has been updating their gateways > to be able to publish readings to MQTT. Using Rich's mqttsubscribe as a > driver works great. > > But...some ecowitt gateways now support backfill capability from SD card, > and some backfilling via queries to the vendor's ecowitt servers also is > possible. So there are multiple backfill scenarios that are possible > (including no backfill). > > What I'm wondering is if it possible to have a two-component driver > notionally. One piece that would handle backfilling on weewx startup and > then exit. A second that would then take over and do the continual > readings after that. > > In other words, follow the unix philosophy of having small utilities that > do one thing well. > > Is that kind of pluggable setup possible (or crazy), or would the weewx > way be to have a driver that 'only' does backfill and a service that does > the realtime readings to the db ? > > -- 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/ac406275-fd89-4128-9a81-6ef5f00b8defn%40googlegroups.com.
