AirGradient Forum

FW 3.7.0 Official Release - AirGradient ONE & Open Air

updates
#1

Hey folks,

I would like to inform you that we are starting to roll out the new firmware version 3.7.0 for the AirGradient ONE (I-9PSL-DE) and the Open Air (O-1PST).

This update includes changes introduced between versions 3.6.2 and 3.7.0. Here are some highlights that you will get from this 3.7.0 update:

  • Added support for the Sensirion SPS30 PM sensor (for both ONE and Open Air)
  • Added GO IAQS Score Mode for AirGradient ONE’s LED bar & OLED display
  • Improved Wi-Fi portal start-up speed
  • Enabled secure OTA firmware update over HTTPS
  • Added CoAP communication for cellular models
  • Fixed PM2.5 correction algorithm issues
  • Added multi-A-record DNS failover for Wi-Fi HTTPS connections

There are also a lot of improvements in the background, you can check them out here: Releases · Open-Air-Foundation/arduino · GitHub .

Please note that it may take time to get the new firmware. Some users may receive the update this weekend, while other users may receive it a bit later.

Also, it’s worth mentioning that we recently set up the Open Air Foundation in Switzerland to strengthen our non-profit activities. Our firmware repositories have now been transferred to the foundation’s GitHub, which will host all our open-source projects.

As always, if you find any issues or have feedback on the new firmware, please feel free to leave your comment here. Looking forward to hearing from you all!

Cheers!
Tai

IMG_7855 (Custom)
IMG_7855 (Custom)1920×1279 253 KB

4 Likes
#2

Two of my indoor units received an update today to 3.7.0 and I have noticed the following:

With LED mode set to GO IAQS, both units will fail to connect to Home Assistant with the following message “Failed setup, will retry: Field “led_bar_mode” of type LedBarMode in Config has invalid value “iaqs”.” After changing back to PM2.5 LED mode, the units will re-connect to Home Assistant just fine.

Furthermore - GO IAQS is not selectable within the mobile app, it seems it’s only accessible through the web dashboard.

Anyway - keep up the good work!.

2 Likes
#3

Could you help to share why the change to support Sensirion SPS30 PM sensor?

1 Like
#4

We’ve been testing the Sensirion SPS30 more extensively and have become more familiar with it, especially since it is also used in the AirGradient Go.

Adding support in the ONE and Open Air firmware gives us more flexibility and lets us support it as an option alongside the Plantower sensors.

2 Likes
#5

Hi @underwater - this may be a bug. I will tag @Tai_AirGradient who can raise this with @Samuel_AirGradient and also log this for implementation for the mobile app.

2 Likes
#6

I appreciate the emails that are sent to me when one of my air gradient units goes offline. What usually happens is that whatever transient issue was causing the problem resolves itself without my intervention. So I tend to ignore these emails.

Unfortunately, when it’s a real issue that doesn’t resolve itself, I don’t take action for several days, because most of the time I don’t have to do anything.

What I would like is for a second email to be sent when the unit comes back online, that way I would notice much sooner that the unit is still offline and that I actually need to intervene.

1 Like
#7

Thank you, everyone, for reporting issues and giving us your feedback.

@underwater, this is an excellent finding! This one needs to be addressed on the HA integration side. Our team is working on it. The issue should be fixed in a future HA release.

@complexworld, thank you for your feedback on the notification! Let me log this to our feature request list.

1 Like
#8

Hey,

I also got the new update and have a question in this regard. I use one batch correction formula for the pm sensor and the values I am getting in the app/dashboard are sometimes significantly higher than on the AG One display (e.g. 28 vs 15 ug/m3). If I remember correctly it was planned that the next update should solve this issue so that the oled display shows same values like in the app/dashboard. With the new update I still have same issue. Is a bug fix planned for one of the next updates?

#9

Hi @DidoEng, thank you for following up on this issue. Could you please let me know which batch calibration do you use?

#10

Hi @Tai_AirGradient, I am currently applying EPA Formula + PMS5003_ 20250530.

#11

@DidoEng, thanks for your quick response.

Could you please try changing your PM2.5 Calibration Formula to ‘Custom via PM Count’, then input 0.02411 as a Scaling Factor, and 0 as an offset. This should give you an identical result to the preset calibration of PMS5003_ 20250530 with the EPA Formula. Please see: PM Sensor Batch Correction Factors | AirGradient Knowledge Base

Please observe and let me know if it works.

image
image1698×681 139 KB

1 Like
#13

Hey @Tai_AirGradient I just checked the difference between both corrections and got pretty big deviation (see below). What is more accurate?

EPA + PMS5003_20250530: Measurement: 15 ug/m3
EPA + Custom via PM Count (SF 0,02411, Offset 0): Measurement: 25 ug/m3

#14

@DidoEng The EPA + Custom via PM Count (SF 0,02411, Offset 0) should be the right one. Please check if the app/dashboard shows more consistent readings with the physical OLED display after you switch to the EPA + Custom via PM Count (SF 0,02411, Offset 0).

The AirGradient Dashboard currently has an issue applying the PMS5003_20250530 directly. Our developer team is working on it, so I would suggest that using the Custom via PM Count is the way to go (as it achieves the same result as what the functional PMS5003_20250530 is supposed to do.

Please let me know if you have any questions. I’m happy to help!

1 Like
#15

Hi,

I have a couple of AirGradient ONE devices with the latest firmware, eg.:

Detected ONE_INDOOR                                                                              
Serial nr: 3cdc75bd0xxx                                                                          
[OledDisplay] Info: begin                                                                        
Firmware Version: 3.7.0

The AirGradient Dashboard lists them, with proper Commissioning date, Last seen timestamp lists initial time. However, their status is offline.
The device’s console lists the reason - certificate error:

---- PAYLOAD
 {"pm01":0,"pm02":0,"pm10":0,"pm01Standard":0,"pm02Standard":0,"pm10Standard":0,"pm003Count":32.67,"pm005Count":27.33,"pm01Count":4.67,"pm02Count":0.5,"pm50Count":0,"pm10Count":0,"pm02Compensated":0,"firmware":"PMS5003x-151","atmp":25.11,"rhum":43.98,"rco2":496.67,"tvocIndex":89.58,"tvocRaw":33654.08,"noxIndex":1,"noxRaw":19546.17,"boot":2,"bootCount":2,"wifi":-36,"resetReason":1,"freeHeap":147200}
-----
[AgWifiClient] Info: Post measures to https://hw.airgradient.com/sensors/airgradient:3cdc75bd0xxx/measures
[AgWifiClient] Info: Payload: {"pm01":0,"pm02":0,"pm10":0,"pm01Standard":0,"pm02Standard":0,"pm10Standard":0,"pm003Count":32.67,"pm005Count":27.33,"pm01Count":4.67,"pm02Count":0.5,"pm50Count":0,"pm10Count":0,"pm02Compensated":0,"firmware":"PMS5003x-151","atmp":25.11,"rhum":43.98,"rco2":496.67,"tvocIndex":89.58,"tvocRaw":33654.08,"noxIndex":1,"noxRaw":19546.17,"boot":2,"bootCount":2,"wifi":-36,"resetReason":1,"freeHeap":147200}
[155220][E][ssl_client.cpp:37] _handle_error(): [start_ssl_client():273]: (-9984) X509 - Certificate verification failed, e.g. CRL, CA or signature check failed
[155389][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -9984
[AgWifiClient] Warning: TLS connect to 91.98.9.143 failed in 302ms (ret=0)
[AgEpSel] Warning: Advance 91.98.9.143 -> 46.225.42.92 (idx 0 -> 1)
[155508][E][ssl_client.cpp:37] _handle_error(): [start_ssl_client():273]: (-9984) X509 - Certificate verification failed, e.g. CRL, CA or signature check failed
[155678][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -9984
[AgWifiClient] Warning: TLS connect to 46.225.42.92 failed in 287ms (ret=0)
[AgEpSel] Warning: Advance 46.225.42.92 -> 91.98.9.143 (idx 1 -> 0)
[AgWifiClient] Warning: All 2 IP(s) failed; falling back to hostname resolution
[155801][E][ssl_client.cpp:37] _handle_error(): [start_ssl_client():273]: (-9984) X509 - Certificate verification failed, e.g. CRL, CA or signature check failed
[155972][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -9984
[AgWifiClient] Warning: TLS connect to hw.airgradient.com failed in 294ms (ret=0)
[AgWifiClient] Error: Both IP and hostname paths failed

Online mode and isPostToAirGradient = true

Free heap: 149012
[AgWifiClient] Info: Fetch configuration from https://hw.airgradient.com/sensors/airgradient:3cdc75bd0xxx/one/config
[156093][E][ssl_client.cpp:37] _handle_error(): [start_ssl_client():273]: (-9984) X509 - Certificate verification failed, e.g. CRL, CA or signature check failed
[156262][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -9984
[AgWifiClient] Warning: TLS connect to 91.98.9.143 failed in 288ms (ret=0)
[AgEpSel] Warning: Advance 91.98.9.143 -> 46.225.42.92 (idx 0 -> 1)
[156387][E][ssl_client.cpp:37] _handle_error(): [start_ssl_client():273]: (-9984) X509 - Certificate verification failed, e.g. CRL, CA or signature check failed
[156559][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -9984
[AgWifiClient] Warning: TLS connect to 46.225.42.92 failed in 296ms (ret=0)
[AgEpSel] Warning: Advance 46.225.42.92 -> 91.98.9.143 (idx 1 -> 0)
[AgWifiClient] Warning: All 2 IP(s) failed; falling back to hostname resolution
[156687][E][ssl_client.cpp:37] _handle_error(): [start_ssl_client():273]: (-9984) X509 - Certificate verification failed, e.g. CRL, CA or signature check failed
[156859][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -9984
[AgWifiClient] Warning: TLS connect to hw.airgradient.com failed in 299ms (ret=0)
[AgWifiClient] Error: Both IP and hostname paths failed

Thanks & best wishes, Ivan.

#16

Hi @Ivan_Z! I believe you need to add exceptions in the router settings for the IPs/domains listed here: Troubleshooting WiFi Connectivity Issues | AirGradient Knowledge Base