Closed obra closed 4 years ago
Ooh, yeah this is definitely a problem. I reformatted that JSON a bit nicer and nothing jumps out as easy to detect as "degraded" other than all of the pm_n_n
values being 0
.
Maybe it's worth ignoring the overall PM2_5
value from a sensor if it's out of a specific range or if it's 0
and the other value is more than like 3
away?
I mean, I think that if one of the sensors is zeroed out and the other sensor is not, we should probably just ignore that sensor
On Sep 8, 2020, at 6:15 PM, Mike Skalnik notifications@github.com wrote:
Ooh, yeah this is definitely a problem. I reformatted that JSON a bit nicer and nothing jumps out as easy to detect as "degraded" other than all of the pm_n_n values being 0.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
End-user reports that the new code appears to work. (Though comments that the color scheme doesn't seem to match PA)
(Though comments that the color scheme doesn't seem to match PA)
Yeah I think this is tracked over in https://github.com/skalnik/aqi-wtf/issues/5. PA does a nice gradient adjustment of the color, where as we just have the one specific color per level.
A friend in Seattle reported that aqi.wtf didn't match purpleair.
It appears that this sensor has one "degraded" channel, so it's only getting AQI data from the B sensor. I believe aqi.wtf is doing the wrong thing when averaging the good and bad channels.
The bad sensor is at https://www.purpleair.com/map?opt=1/i/mAQI/a0/cC1&select=20759#13.18/47.5699/-122.39299
Raw sensor data from what purpleair's map is currently seeing is inline below: