Would be awesome if they could also make strides towards a working fingerprint sensor on their flagship Pixel phones. The accuracy on my P6 is 30% on a good day.
>Not unnaturally, many elevators imbued with intelligence and precognition became terribly frustrated with the mindless business of going up and down, up and down, experimented briefly with the notion of going sideways, as a sort of existential protest, demanded participation in the decision-making process and finally took to squatting in basements sulking
Super bummed, Vangelis got me into electronic music back in the early 90s. I've since made it my mission (obsession) to collect all of his albums, which I'm still working on.
That sensor is also available from Adafruit: https://www.adafruit.com/product/3686
I got it hooked up to a RaspberryPi that exposes sensor readings in Prometheus format.
Do you have a PurpleAir II to compare against? I suspect that there will be some extra calibration or signal processing some to make it more accurate that will be missing in the raw sensor.
EDIT: The link we're discussing says this explicitly: "[...] These particle counts are processed by the sensor using a complex algorithm to calculate the PM1.0, PM2.5 & PM10 mass in ug/m3. [...] PurpleAir PA-II uses two identical PMS5003 sensor units attached to each other and placed in the same shelter. [...]"
I don't think you can recommend the PMS5003 as a substitute for the PurpleAir II.
That sensor available at Adafruit uses the same algorithm for calculating PM levels, it's literally the same chip. Maybe using 2 of them yields more accurate results though.
The Adafruit sensor is just the sensor, the PurpleAir II is two sensors plus extra logic that processes the readings to give extra accuracy.
You can't expect one sensor to give the same performance as two sensors plus correction logic. If it was that easy, PurpleAir could just put a case on a PMS sensor and be done with it.
No kidding... look at the first pass of node applications written by people coming from .Net or Java... (I include myself)... it takes a while to get into the "node way" breaking your code down into discrete modules, and favoring functional flows over OO ones.
That said, once you get into it, some beautiful orchestration patterns emerge[1][2].
