Thank you for the quick work Gary! Please note that even though the raw data coming from this new sensor is for the PM10 to come first and then the PM2.5 that is not the order that we would typically refer to the sensor as ...it is called the PM2.5, PM10, CO2 sensor in that order. Looking at the GW1000 API documentation it baffles me why the engineers decided to send PM10 data first. Also on the GW1000 mobile app (WS View) and on Ecowitt.net the order is also PM2.5 first and then PM10. I fee therefore that WeeWX should keep the order as PM2.5 first and then PM10.
On Thursday, December 31, 2020 at 8:26:45 PM UTC-5 gjr80 wrote: > WH45 support was coded some time ago though of course not tested with an > actual device. Have had a number of other features I was working on to add > at the same time which delayed release of the WH45 compatible version of > the driver. Rainer now has a copy of a compatible version of the driver to > test and once he confirms it works I will shortly afterwards release the > WH45 compatible version. > > As an aside, and on a technical note, this did highlight that I need to > change the approach the driver uses to dealing with sensor data from the > GW1000. Ideally adding an new sensor type should not cause a driver that > does not know about that new sensor type to crash; rather the driver should > continue to operate but just not provide data for the (to it) unknown > sensor. This will be something to work on for the next version of the > driver, fortunately Ecowitt is not releasing new sensors that often. > > Gary > -- 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/20e59572-c7c1-4f62-b909-82ecdb7c6957n%40googlegroups.com.
