Welcome to the Cumulus Support forum.

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024

Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

Airquality values confusion

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

Post Reply
User avatar
KarlS
Posts: 137
Joined: Tue 30 Nov 2010 3:01 pm
Weather Station: Ecowitt GW1003 / WH32 / WH41
Operating System: 64bit Bookworm on Pi4
Location: Bridge Lake, BC, Canada
Contact:

Airquality values confusion

Post by KarlS »

It is not only dangerously hot here in British Columbia, but we also have dozens of wildfires burning within a 20km radius. So for the first time since I installed the Ecowitt WH41 PM2.5 Air Quality sensor the reported values are anything but “good”.

Code: Select all

      | 30/06/2021  | 01/07/2021
Time  | AQ1 AQ1avg  | AQ1 AQ1avg
------|-------------|-----------
05:00 | 21   14.7   | 37   63.0
05:10 | 22   14.8   | 44   61.1
05:20 | 17   14.8   | 49   61.2
05:30 | 18   14.8   | 48   60.8
05:40 | 16   14.8   | 47   60.3
05:50 | 19   14.9   | 46   59.9
CumulusMX reports these values as Extra Sensors Airquality Sensor1 and Sensor1avg. Since installation, the value for Sensor1 was always higher than Sensor1avg, so I assumed that Sensor1 was the peak value for the reporting time. This morning, the value for Sensor1avg is way higher than Sensor1, so Sensor1 can’t be the peak value. Maybe it is the last reported value by the sensor? But what are the chances that in the days before the last value reported was consistently higher than the average?
Mapantz
Posts: 1820
Joined: Sat 17 Dec 2011 11:55 am
Weather Station: Davis Vantage Pro2
Operating System: Windows 11 x64
Location: Dorset - UK
Contact:

Re: Airquality values confusion

Post by Mapantz »

I presume you have set your country's air quality index in Extra Sensor Settings?
Image
User avatar
KarlS
Posts: 137
Joined: Tue 30 Nov 2010 3:01 pm
Weather Station: Ecowitt GW1003 / WH32 / WH41
Operating System: 64bit Bookworm on Pi4
Location: Bridge Lake, BC, Canada
Contact:

Re: Airquality values confusion

Post by KarlS »

Mapantz wrote: Thu 01 Jul 2021 1:59 pm I presume you have set your country's air quality index in Extra Sensor Settings?
Yes, it is set to Canada-AQHI.

On second or third thought, maybe the AQ average isn't calculated by CumulusMX but is a 1 hour (6 hour, 12 hour ?) average supplied by the Ecowitt gateway??
freddie
Posts: 2477
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 22.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

Re: Airquality values confusion

Post by freddie »

I think the average is a 24-hour average - that seems to be the standard in the AQ world.
Freddie
Image
User avatar
mcrossley
Posts: 12767
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: Airquality values confusion

Post by mcrossley »

As @freddie says, the average AQI standard is 24 hours, and iirc that is also what the Ecowitt supplies.
User avatar
KarlS
Posts: 137
Joined: Tue 30 Nov 2010 3:01 pm
Weather Station: Ecowitt GW1003 / WH32 / WH41
Operating System: 64bit Bookworm on Pi4
Location: Bridge Lake, BC, Canada
Contact:

Re: Airquality values confusion

Post by KarlS »

mcrossley wrote: Thu 01 Jul 2021 9:51 pm As @freddie says, the average AQI standard is 24 hours, and iirc that is also what the Ecowitt supplies.
Right, so the reported Sensor1avg is a 24 h average. Makes sense. That still leaves the question what the Sensor1 value represents. Is it an avg, peak or latest over my 10 minute time span?
Post Reply