The warnings shows up once, after the ecowitt_http.py was altered when a new pycache object is created, only showing up when starting weewxd manually. It is console output not being logged.
vince schrieb am Montag, 14. Juli 2025 um 20:03:48 UTC+2: > On Monday, July 14, 2025 at 9:29:24 AM UTC-7 steepleian wrote: > > @Werner > I find it very confusing that hail is used for p_rain. > My database has columns for p_rain etc from mods I made for GW2000 driver. > > > Agree. I notice that weewx doesn't directly support multiple wind nor > rain sensors, so folks with a combination if piezo and old-style > spinning/tipping sensors have issues mapping database elements. > > Rather than requiring modifying the as-delivered weewx schema, I'm > wondering if an alternate approach might be to create an ecowitt-specific > schema and a secondary db for whatever ecowitt supports. Granted, skins > would need to explicitly reference the ecowitt db binding, but it would > make the database mapping issue a non-issue. > > FWIW - the purpleair extension I use as well as a couple other extensions > create these alternate databases on first use, so it's not a big deal. > You might consider taking the same approach for ecowitt which has a growing > list of uniquenesses as they add more and more sensor types users can > purchase. > > That said, I do not know offhand if it is possible to have a driver's > sensor_map use a secondary db rather than the default db. That might be > helpful to be able to do, or even to map each sensor_map item to the chosen > db+element to read from. > > -- 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/6f71aceb-1ef6-4128-8761-8cb88c978943n%40googlegroups.com.
