Hello Everyone,
I just bought the AirGradient One Kit and assembled it. My PM sensor show PM2.5 values between 5 and 15 ug/min3 most of the time. Its production date is 20250530. I don’t see the behaviour described here where the sensor mostly shows 0 ug/min3. Should I perform batch correction anyway for better results? I’m asking since I noticed there is a calibration formula in the admin panel for this batch., but i am not sure if I should perform the calibration with this formula.
Hi @DidoEng , welcome to our community!
It’s a good practice to apply a custom calibration formula where possible, alongside the EPA formula in most cases.
In your case, if you are using the AirGradient Dashboard only, please kindly pick 20250530.
However [you can ignore the message after this if you are only using AirGradient Dashboard with your monitor], in case you’re not only using the AirGradient Dashboard (e.g. you also use Home Assistant). Currently, I recommend you pick the Custom via PM count in the PM2.5 calibration section instead of picking 20250530 directly, then input the scaling factor and offset accordingly (scaling factor: 0.02411, offset: 0). Since we found that some of the batch-specific calibration formulas are not applied locally on the device (we are working on a fix and will roll out on the next firmware releases). These are the calibration formulas that have the issue the the configuration are not applied on the local device (but it does work normally if you’re relying on using only AirGradient Dashboard):
- Custom via PM2.5 Raw
- PMS5003T_20241222
- PMS5003T_20250208
- PMS5003_20250530
Hello Tai,
thank you for your answer!
So if I understood you correctly, if I am using the AirGradient Dashboard, I need to go to the admin panel, then edit the pm2.5 calibration and after that I should choose EPA formula click next and so on… and then redo this again with the PMS5003_20250530 formula, right?
Hi @DidoEng, you’re welcome! You can simply select the PMS5003_20250530 and check the ‘Apply EPA Formula’ box (this box will appear as soon as you select the PMS5003_20250530) as shown in the image below.
Hi @Tai_AirGradient,
i performed the PM2.5 sensor calibration like described by you, but now i have following issue.
The values from the iOS App/AG Dashboard differ from the values shown on the AG One Display. The AG Display always shows smaller PM2.5 values compared to the iOS App/Dashboard. For instance the device shows 14ug/min3 and the app shows 22.5ug/min3. I also noticed that this offset is not constant.
Which value is the right one? How can I make both devices to show the same right value?
The other values (CO2, T, Humidity, NOx, TVOC) are equal on the device and in the Dashboard.
Hi @DidoEng ,
Thank you for the update. As I mentioned, some batch-specific formulas don’t take effect properly (bug) on the device side, which means your AirGradient ONE OLED might not recognize the PMS5003_20250530 formula, so the OLED display doesn’t show the PM2.5 value that is corrected accordingly to PMS5003_20250530 formula. However, the AirGradient Dashboard and the mobile app should display the corrected PM2.5 value properly.
Briefly, the value you see on the AirGradient Dashboard and mobile app is the right one (the corrected value used PMS5003_20250530 formula).
However, please rest assured that we have acknowledged this issue and will provide the fix soon.
In the meantime, in case you want the conformity of all displays (dashboard, mobile app, device’s OLED display), you can try switching the calibration formula to ‘EPA Formula’. The PM2.5 value will be corrected using EPA formula only (without the batch-specific formula, which is currently problematic).
With this approach, the PM2.5 value shown on the device’s OLED display and the AirGradient Dashboard/mobile app should be closer (please note that the dashboard and mobile app data update interval is 60 seconds, while the OLED display on your AirGradient monitor is approximately 2-3 seconds).
@Tai_AirGradient thank you very much for the answer! I am then looking forward for the next firmware update 
