AirGradient Forum

Can't add a DIY-PRO v 4.2 to Home Assistant anymore

I’ve been using a DIY-PRO v 4.2 with the “beta” firmware from here on Home Assistant for awhile with no issue. I’m currently running 2025.11.1, which is the “stable” version of the Docker container.

I’m retiring the old Home Assistant instance to repurpose some hardware (slash, I did it wrong the first time around and want to start with a clean slate) and creating a new one running Home Assistant Operating System (2026.9.3) on an old SBC I had sitting around. So far, so good, but when I try to add the DIY-PRO v 4.2, I get the error message “This firmware version is unsupported. Please upgrade the firmware of the device to at least version 3.1.1.” The DIY-PRO reports firmware version “snapshot.”

It seems like the version check was added here: https://github.com/home-assistant/core/pull/118744. The sensor works fine in 2025.11.1, it just seems to be failing the version check.

New sensor firmware to report a sensible firmware version? Fix the Home Assistant integration? Something else?

Hi @akc7819, welcome to our community and thank you for reporting this issue. I will discuss this with our firmware engineer and will get back to you as soon as there’s an update.

Thank you!

My solution for now was to build 3.7.0 from source.

The code is here: github [dot] com/Open-Air-Foundation/firmware-one-openair/tree/master/examples/DiyProIndoorV4_2

Instructions are here: github [dot] com/Open-Air-Foundation/firmware-one-openair/blob/master/docs/howto-compile.md#steps-for-esp8266-based-board-diy-model

(Links intentionally broken because the forum software is rejecting this post if I don’t.)

Running that firmware, the sensor reports 3.7.0-snap, which passes the version check and I can successfully add it to Home Assistant The sensor seems to be reporting reasonable values to both Home Assistant and the cloud, but I can’t say I’ve done much to verify correct operation with this firmware. On the Home Assistant side of things, it wants to upgrade the firmware from “3.7.0.-snap” to “3.7.0”, although it is incapable of doing so.

1 Like

@akc7819 Thank you a lot for your update and for providing the detailed guide.

We will update our knowledge base articles for the legacy models.

I would appreciate it a lot if you could provide an update after a while to see if it runs reliably over time. Thank you!

Same problem here.
Also the flashing over the website is also broken, because that is also not able to read out the firmware version anymore.
I manipulated some weblinks and got my hands on the DIY-PRO v3.7 firmware image from the website. And I get the same problem in home assistant and on the website.
So I guess the version number is broken in the “beta” firmware completely.

Hi @bdvd, welcome to our community.

Could you please confirm that the “beta” firmware you referred to is the one provided on this page: The AirGradient DIY Air Quality Sensor (Pro Presoldered-Version, PCB Version 3.7) | AirGradient Knowledge Base ?

And from my understanding, Home Assistant rejects your DIY Pro because the version number is not properly reported. Is that correct? (I’m sorry that I don’t have the v3.7 hardware so I cannot verify it myself). I will discuss this with my team. Thanks.

Hi @Tai_AirGradient,
Yes. I tried the versions 3.7 (that you linked) and the version 4.2.
Both of them suffered the same problem.

At the end I ended up tricking my home assistant to believe everything is fine by overriding this function to return only True no matter what:
homeassistant/components/airgradient/config_flow.py#L47

1 Like

Hi @bdvd, thank you for your reply.

I checked with our team and can confirm that the Home Assistant integration has a mechanism to check the firmware version tag of the air monitor.

In the meantime, for DIYers, you may follow @akc7819’s path to fix. However, please allow me to discuss this again with the team for a more sustainable fix. Thank you for your understanding.

I don’t think anyone was ever claiming it didn’t. Rather, the “beta” firmware you (as in AirGradient) suggest for Home Assistant support on this hardware reports firmware version “snapshot” on both the OLED display on startup and when queried programmatically. The problem, then, is that this fails a version check in the Home Assistant integration when we try to add the sensor to Home Assistant. If this check is bypassed, the sensor works without major issues. (Minor issue: It complains about how the firmware should be updated—but it also does that in builds of 3.7.0 from source, so that seems like a problem with the integration.)

The version check on adding a device in the Home Assistant integration is not apparently doing anything valuable because devices that fail the check work. The version check on device add should probably be removed. Also, whatever version of the firmware you recommend for Home Assistant should report a firmware version that Home Assistant will accept.

The version “number” is reported, it’s just the string “snapshot” which the Home Assistant integration rejects as an unsupported version when you try to add a device.

1 Like

Hi @akc7819, thank you very much for your clarification.

I am going to get my hands on the legacy DIY monitors soon. I will try testing them to experience all the issues myself and will discuss them with our team again, especially the point you mentioned about the version check in the Home Assistant integration failing to work.

I will update here when I have an update. Thank you again for all the useful, detailed explanations.