At the time, my Basic kit with the sensor I purchased conflicted with the display, but maybe the newer sensors direct from AG will work, so that is what I’m going to give a shot and see if the display works with it.
sounds great! thank you
Looks like you are still using 2 min interval for PMS5003.
I am using “0s” interval and just doing moving average window.
Airgaradinet folks did not recommend stoping fan of PMS5005. Any specific reason you’ve decided not to use short interval?
Another suggestion is to shutdown LCD screen at night. It is too bright in my night stand
Oops, I was misremembering. In my experience with the Basic kit, it was the SGP30 that wasn’t working with the display, which is a TVOC sensor, but the SHT31 sensor for temp and humidity was fine. In the YAML file, to change it to support the SHT41, it would be just changing the line - platform: sht3xd to - platform: sht4x and the rest should be fine.
But I’ll still test with the SGP40 TVOC sensor again and have an updated yaml file in the next few days that matches the Pro version more closely.
Two reasons
- There is/was a flaw in the software serial implementation in ESPHome that caused the device to reboot frequently when the logging output was very chatty, and the PMS5003 reporting every second was differently related to the reboots. By changing the update_interval to 2 minutes, the issue was mostly solved for me. There are other ways to force newer Software Serial versions, plus newer versions of ESPHome, but this worked consistently for me
- The ESPHome documentation specifically called out changing it to 120s or higher to extend sensor life, so it sounded like a good idea at the time: PMSX003 Particulate Matter Sensor — ESPHome
I only saw recently that Achim from AirGradient didn’t recommend changing the interval, but would like to see some tests side by side to confirm. I have 2 Pro kits, one I sourced parts from AliExpress and one direct from AG, and the one from AG does report higher PM2.5 counts in general, but both are using ESPHome with the same update interval, so I know both are getting readings, just not sure if they would get any more accurate if they were reading every second compared to every 120 seconds.
Early when we were just starting with AirGradient we sourced the PM5003 from AliExpress and got very different quality and some of them were showing considerably higher or lower readings.
Since we source them directly from Plantower, we see very very similar data across hundreds of PM sensors. So @MallocArray when you mention that one of the PM sensors you sourced was from AliExpress, this could be the explanation for it.
To verify you could probably swap the PM sensors to confirm if it’s a firmware or hardware issue,
Indoors, I’m typically getting 0 pm2.5 with my original Basic kit and my self sourced, and with my latest Pro direct from AG, I go from 0-10 pm2.5, when the outdoor levels are 10-25. So not wildly different, but measurable.
It does make me question the AliExpress sensors, but the typically shops are either Amazon or Ali, both with varying quality, or buying a whole kit with shipping from AG, and since they all “work” but with questionable reliability/accuracy, it is hard to know.
Thanks to @MallocArray for the code, I’ve been using your airgradient-pro.yaml with my self sourced sensors and it works great. I’ll try out the newest version this weekend.
Home Assistant was new to me when I first started using AirGradient and it was pretty confusing and overwhelming at first (and I come from a technical background). I had an older Raspberry Pi that I used to install HA on using the instructions on the HA site. No problems there.
But after that things got confusing. I found several other sites where I figured out I had to install ESPHome on HA but then spent a lot of time figuring out how to add the device. I ended up understanding I could temporarily plug the AirGradient in via usb into my Pi, go to ESPHome, “New Device”, then “Plug into the computer running ESPHome Dashboard”. BTW, this is just a one time step and after the installation any future configuration updates can be done with the “wirelessly” option.
After that appeared successful though I was stuck with @barman’s question of, where’s the data? Again, this was due to having no HA experience. After finally figuring that out and creating some dashboards I feel pretty good about the setup. My one question though, is it possible in HA’s dashboards to color change the state of the graphs depending on thresholds? For example if CO2 > 1000 change it to yellow, like how the AirGradient app is.
I think it would be great to have an integration docs section with screenshots and instructions that live on this site. The forum is great too but I had to search a lot and piece info together as I understood more. Hope that makes sense.
I have just received the new " Open Air Outdoor Monitor O-1PST CO2 Version" - will these integrations work with the additional sensor, or do I need to add something?
Primarily looking to switch to ESPHOME, with the additional upload to the Air Gradient API, so I can integrate in to Home Assistant.
Thanks.
I’m working on a config for ESPHome for that model right now, so if you can wait a few days I hope to have something ready soon.
Thanks for the update - as a newcomer to this community I can see your efforts are appreciated.
Does it include control of the blue light? That is already generating comments within the family and I haven’t even mounted it yet!
What blue light do you refer to?
Blue LED next to the USB port. Keeps coming on.
My initial release of an ESPHome config for the new AirGradient One with the v9 board is now available:
airgradient_esphome/airgradient-one.yaml at main · MallocArray/airgradient_esphome (github.com)
Supports all included sensors and the LED bar, based on CO2 values, as well as sending data to AirGradient’s dashboard in addition to your own HomeAssistant
We will most likely make the blue light only blink during the WiFi setup and if the monitor has some problem. Would that make your family happy 
?
That would make the most obvious use of the LED in my mind. My children are used to things with lights on around the house and outside, and if something is showing a light which shouldn’t do I usually get a report very quickly. Therefore it being used for error conditions only would probably make the most sense.
Although I will be switching over to the ESPHome config as soon as it is ready…
I’ve updated gohai’s HomeKit port to work with DIY_PRO_V4_2. If anyone runs into any bugs or issues feel free to let me know and I’ll do my best to help out if I can. I haven’t run into any problems yet but I also haven’t done any extensive tests.
Here is the link to my repo - https://github.com/brian-gee/arduino-homekit-enabled/tree/master/examples
@investigatorno56 Thanks for your great work on HomeKit integration for DIY PRO V4.2
I would like to know can I upload the same firmware to two Boards which is DIY PRO V4.2 with the same setup password and added to the same HomKit network ?
Are the 2 units detected under the same HomeKit then they can added on the same Apple Home network such as the same Home Name and same WIFI network?
I found that only one unit can be detected on the Add Accessory Screen, the 2nd unit must be power off. Simply speaking only ONE unit can be detected on the same Home network, even I try to changed the Setup password with difference number. Do you have any idea to fix that?
Thanks!
Alan