Airgradient Go Arrived

[Cossym]

I posted this to reddit last night but their over zealous filters removed it. Tai suggested posting here

Arrived safely this afternoon ​Few things so far:

Love the form factor.

Pm2.5 was higher than my co-located ONE. 2-5ug/m3 vs zero… Which got me digging into why the ONE was flatlining (previously assumed my air was super clean ). Turned out I’d missed the calibration needed for the sensor… And been under reading for quite some time! Oh well. N​ow they’re much more comparable.

co2 is super close after calibration.

Temperatu​re is about 2 degrees C higher on the Go. Humidity is about 7 percent lower on the Go. I had calibration applied to the ONE which appears to have been unnecessary (Required for Outdoor only I believe​). After removing the calibration I’m not seeing any difference though, so there’s still a bit of a discrepancy.

Can’t stream data to Airgradient server (says it needs to be linked to a cloud location first, which I can’t immediately see a way of doing… I believe this is work in progress?).

Can’t comment on battery or GPS but will be using it properly in coming weeks

Charging is a bit of an issue. The cable provided (and others in my house) will not charge when properly inserted. Instead I need to put slight pressure on the connector to have it charge. Has anyone else encountered this? The handy blue led on the provided cable helped me discover this easily.

[Tai_AirGradient]

Hi @Cossym, welcome to our community! Thank you for posting here and for your detailed feedback on the AirGradient Go.

The temperature and humidity readings need a correction algorithm, as there is heat generated from components inside the enclosure. We are developing the correction algorithm specifically for the AirGradient Go and will push the update to all AirGradient Go out there as soon as it is ready.

For “Stream current data to AirGradient Server”, you need to register your AirGradient Go on your AirGradient Dashboard after you have your AirGradient Go connected to your AirGradient Map app on your phone. We are working on this, so the AirGradient Go is not yet on the ‘Connect a Monitor’ page on the AirGradient Dashboard.

However, you can follow the steps below to get it working (we are working on this to ensure that we provide the best experience for all AirGradient Go users. We are in the process of simplifying these, and we intend to make it complete when the Home Assistant integration is ready for the AirGradient Go.:

Go to your AirGradient Dashboard → Select ‘Connect a Monitor’ on the side menu → Tap ‘Next’ → Tap ‘AirGradient ONE / BASIC / DIY PRO’ → Select ‘AirGradient ONE (I-9PSL-DE) Indoor Monitor’ → Input your AirGradient Go’s serial number in the ‘Serial Number’ field, and input your preferred ‘Location Name’ (this can be anything, e.g. ‘AirGradient Go’ or ‘Living Room’) → Tap ‘Add’ → Ignore the ‘Connect to Wifi’ step for now → Tap ‘Next step’ → Tap 'To Dashboard’

After that, please go to your AirGradient Map app on your mobile phone. Navigate to the AirGradient Go that your phone is connected to. Go to ‘Configure monitor’ → Toggle ‘Stream current data to AirGradient Server’ on

A few minutes later, you should see the AirGradient Go appear on your AirGradient Dashboard

You can also switch the AirGradient Go to the Stationary Mode, so the Go will be able to work directly via your home Wi-Fi (without relying on your phone’s Bluetooth connection). Simply put, to use it as a normal stationary air monitor. You can follow this article to connect your AirGradient Go to Wi-Fi in Stationary Mode: Connect AirGradient Go to WiFi | AirGradient Knowledge Base

---

Regarding the charging USB port, could you please provide us with more information with photos and videos via Contact Us ? We are happy to look into it.

Thank you again for your feedback. We are looking forward to hearing more feedback from you and every Go user. Please feel free to let us know.

[Cossym]

Thanks for the detailed response!

Re: temperature and humidity, that makes sense. Will wait for the calibration to be applied in future.

I followed your instructions and can see the Go in my dashboard now pm2.5 had a default “factory calibration” applied which a scaling factor of over 2x. I hope this is incorrect as it was showing far higher than my ONE for now I’ve switched to raw which obviously matches the e-ink display. Can you comment on whether I should be applying any pm2.5 calibration for the Go?

I’ll send more details about the charging cable later today

[Tai_AirGradient]

@Cossym, my pleasure!

Please let me take some time to consult with our team about the calibration for an accurate answer, and I will come back to let you know.

Could you please confirm if I understand you correctly that:

• The calibrated PM2.5 reading of the Go on the Dashboard shows a higher value than the calibrated PM2.5 reading of the ONE on the Dashboard.
• The raw PM2.5 reading of the Go on the Dashboard (which matches its physical e-ink display) shows a comparable reading to the corrected PM2.5 reading of the ONE on the Dashboard.

Thank you!

[Cossym]

Thanks!

Yes that’s correct. The Go calibration was “factory” and the ONE calibration is PMS5003_20231218 with EPA formula.

Now that Go is set to “raw” its very close to the ONE with the calibration above.

[Tai_AirGradient]

@Cossym, thank you for your confirmation. Please give us some time to check this out.

Regarding the Go’s e-ink reading VS Go’s Dashboard reading: the reason why the reading shown on the e-ink display and the reading shown on the AirGradient Dashboard of the AirGradient Go are different. It is likely because the current firmware versions (1.0.0 and 1.0.1) do not support parsing cloud configuration (e.g., the correction algorithm you made changes to via the Dashboard) on the local side of the device (the Go receives that configuration, even if in Stationary Mode (Wi-Fi connected), it doesn’t take action in the current firmware, so the new configuraion doesn’t take effect on the e-ink display). I have confirmed with our engineer that we will implement this in the next firmware (v1.1.0). Please stay tuned.

Please feel free to keep your feedback coming. We are happy to hear all of the feedback to improve the product. Thanks!

[Cossym]

Understood I’m using raw for now and will wait for confirmation on whether any calibration should be applied.

I’ve raised a ticket for the charging port now.

Other feedback so far: I recorded my first route and found the GPS didn’t kick in until partway through. I’ll be sure to get a proper lock before starting next time (I know GPS struggles to get a lock while moving). So not really something for you to worry about at this point

[Tai_AirGradient]

Thanks for your update @Cossym! Please let us check, and we will get back to you.

[Cossym]

Some additional findings:

After a “critical battery” message, the pm sensor was not providing any readings. A diagnostic test showed the pm sensor in a failed state. A reboot of the device rectified that.

Regarding battery life. I’m finding it lasts only a few days in “stationary” mode with GPS effectively off (on for tracking) and a sampling rate of 5 mins. This is substantially lower than the battery simulator showed in similar conditions (around 6.5 days)

I’m going to charge fully and get an accurate measurement for this soon.

[Tai_AirGradient]

@Cossym thank you for the update!

Just to confirm that I understand the Go’s behavior you described correctly. After the critical battery message appears → the PM shuts down → and it does not resume when you plug it into a USB power source; the only way to make it work is to force-reboot it. Is that correct?

And thank you for reporting on the battery life. Please let me check this with the team. There is a lot to improve, and we are quite close to releasing a new firmware that supports, e,g, local API, configurable measurement correction, and more other features. Please stay tuned, and feel free to keep your feedback coming.

[Cossym]

Yes that’s exactly what I experienced

Interestingly, after the battery critical this time, the co2 is not reading at all. A hardware test showed pm fail, co2 pass.

After a reboot, both pm and co2 are showing fail. Pm is updating but co2 is 0 or -.

I’d charged it from dead for around 5 hours and it maxed at 94 percent. Then died again after 18 hours this time. Same settings as before.

[Tai_AirGradient]

Hey @Cossym, thank you a lot for getting back! I discussed this with our hardware engineer, and he suggested that it is likely caused by not enough voltage for those modules. He suggested that we adjust some firmware logic to improve the user experience. Let me hand this over to our firmware engineer. Thank you so much for reporting the issue. Please don’t hesitate to let us know if you find any other issues or have any suggestions.

[Cossym]

Thanks! Will keep an eye out for firmware updates as they come available

[Tai_AirGradient]

Sure! We will let you know when it is available.

[Cossym]

Latest is that after multiple recharge cycles and manual reboots, the co2 sensor has not been registering a signal. I’ve tried rebooting on a full battery and when plugged in.

Wonder if this will/can be addressed with firmware and voltage tweaks? Any other suggestions in the meantime?

Co2 has been offline for maybe 4-5 days now.

[Tai_AirGradient]

Hi @Cossym, thank you for reporting, and sorry for the inconvenience you faced.

Could you try performing a hard reset by following the steps in this article?: AirGradient Go: Performing a Hard Reset | AirGradient Knowledge Base

The CO2 should return online after the hard reset. Feel free to let me know if that doesn’t help.

Thanks!

[Cossym]

Thanks for the instructions. I’ve tried that a few times now without any change in co2. It’s stuck at “0”. I also tried recalibrating in case it was stuck at an out of range value. No change.

Interestingly, a hardware test showed co2 getting a “pass”.

[Tai_AirGradient]

@Cossym, thanks for your response! Let me consult our engineers about this, and I will get back to you.

[chris_bernhardt]

I haven’t been paying much attention to all the posts on calibration. I just received my GO. The numbers, especially for Pm2.5, are quite different from my ONE. (Reading of 4.9 ug/m3 on GO vs 19 on ONE).

Which needs to be recalibrated? How do i go about this?

[chris_bernhardt]

I have been playing around. I connected GO to the cloud following the instructions above. The dashboard readings for GO are fairly close to readings for ONE. The reading on the physical GO doesn’t agree with the uploaded dashboard reading.

On my phone app I see the cloud readings on the initial page. There is a tab saying a GO is nearby. If i click on that i can connect by Bluetooth to the GO and it shows the reading displayed on the GO.

I am hoping it can all be sorted out with a firmware update.