i was about to pinch john’s code for the AQI side of things - i get PM2.5 values via gw1000 - when i see this new driver announced. (i have found ecowitt’s purported 24 hour average values very unreliable - drifting, random resets, etc - but the actual pm2.5 values seem fine → derive the averaged values myself)
can i suggest that acquiring PMx.x values and deriving AQI values be kept as separate services? the AQI service would provide AQI xtype (mainly for cheetah) and convert PMx.x values in weewx packets to equivalent AQI values inserted into weewx packet (this is what i was going to implement). design-wise this would also allow support of AQI values derived from multiple pollution types (NO, etc) as well as abstracting the pollutant monitors > On 27 Sep 2020, at 1:43 pm, John Kline <[email protected]> wrote: > > Hi Rich, > > I’ve created the github project here: > https://github.com/chaunceygardiner/weewx-airlink > <https://github.com/chaunceygardiner/weewx-airlink> > > I haven’t had any issues with the extension, but it’s not a priority for me > until more is known about the AirLink. > > Cheers, > John > -- 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 on the web visit https://groups.google.com/d/msgid/weewx-user/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%40gmail.com.
