Likely comes down to how the device deals with lots of queries in a short time frame. This driver seems to by default poll very frequently. Only testing can say if there is any concern.
I ran multiple weewx polling an ecowitt gw1200 with no problems but that device only gets polled every minute. The pi5 will not be your limit. Heck go ahead and run 5 instances on the pi and see what https://github.com/weewx/weewx/wiki/weewx-multi On Friday, January 9, 2026 at 11:14:08 AM UTC-8 DR wrote: > "The six year old one is mine (at > https://github.com/chaunceygardiner/weewx-ip100). > > > I’ve long since moved on to a Vantage Pro, but this IP100 driver will > work on WeeWX 5.2. Let me know if you need any help. > Driving two weewx instances would be an interesting experiment. You’ll > have to try it. You could also get another IP100 or a CC3000. That > would definitely work. I have some lying around. Where are you located?" > > I will try implementing the one you pointed to and with your knowledge > of the WeeWx 5.2 and Python requirements feel that it should work, since > I'm trying to keep several options open and while many have upgraded > their stations to Davis and has a lot of attention. > > I'd be interested in an IP-100 maybe and yet will try to see if there > are collisions with two drivers requesting data from one IP-100 as soon > as I get the driver you pointed to installed on my Pi5. As you imply, > there should be no problem if each WeeWx is pointing to a different IP > address. > > Thanks for you help. Dale > > -- 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 visit https://groups.google.com/d/msgid/weewx-user/ab77ad60-f19a-4394-9a9a-b84223a3111dn%40googlegroups.com.
