Oh this is nice — so using this, you could have the device both pushing data to AirGradient’s cloud, and to your local HA instance, correct?
Ah, took a glance, it looks like it works by diverting the URL to point at your local Home Assistant install. It would be really cool if there were a way to get ESPHome + AirGradient support (without customizing things so much) so I could use both at the same time.
That is completely possible with this:
MallocArray/airgradient_esphome: ESPHome definition for an AirGradient DIY device to send data to HomeAssistant and AirGradient servers (github.com)
Currently the “Upload to AirGradient Dashboard” is disabled by default, but just a flip of a switch in HomeAssistant to enable it (Assuming you have your ID registered in the AirGradient Dashboard)
I’ve been running HA for several years, and recently setup two AirGradients which are working fine to the AirGradient cloud. I’d really like to get them logging locally, but I don’t really understand all the references to ESPhome, does this mean I’m no longer running AirGradient code and instead a custom firmware? And I also need to install ESPhome somewhere as a go-between to HA?
This new integration seems like a much nicer option to “remain stock”, but now I’m unclear if I can send to both without replacing all my firmware anyway?
Yes, you would convert the units to ESPHome firmware (which is ‘custom’ compared to the stock firmware). There is no need to install anything between ESPHome and HA, as HA can connect directly to ESPHome (ESPHome is intended for usage with HA and provides a native API connection).
It is a significant change, and is not for everyone (mostly it’s useful for those of us who are already using ESPHome on other devices).
Thanks for the explanation. I’m in the same boat as jfitzell. Suppose I go the ESPhome route, I do need to install the ESPHome Add-on in HASS, correct? Which in my case would mean a seperate ESPhome Docker, as I’m running HASS in Docker, which does not have the Add-On store.
Personally I’m looking at the MQTT route, as I already have a MQTT broker setup. Hopefully it comes available soon for the Gen 9.
Correct. I run HA in Docker and have another container running ESPHome. I explained it a bit more in this thread:
If you aren’t looking to reconfigure much, you can use the .bin files from the ESPHome integration repo and just install it using the web flasher so you don’t need to install ESPHome right now, you just can’t configure the name of the device, but if this is a first device and an intro to it, then it is a low friction route.
I ended up finding a lot of uses for ESPHome so I have devices acting as IR blasters, controllers for dumb ceiling fan remotes, temperature monitors for air coming in and out of my HVAC, and more. So once you start down the rabbit hole, you may find a lot of things you can do with it.
Thanks for your reply, I appreciate it. I’m still a bit confused, pardon for asking but do I still need to run an ESPHome Docker container if I go the .bin file route? Or is it sufficient to just flash the .bin file via web.esphome.io without running the ESPhome Docker container?
Thanks
Not initially. It won’t know about your Wifi network, so after using the .bin file you’ll have to find the hotspot that it creates so you can enter your wifi info and then it will be on your network. Hopefully it is autodetected by HomeAssistant, or you may have to find the IP address to add it to HA if it doesn’t.
Then you should be good to get started, all without ESPHome Docker.
Also it is not necessary to use Docker to use ESPHome to build new/modified firmware images and upload them to devices; while that is a convenient option for many HA users, it’s not the only mehod. The ESPHome software can be directly installed on pretty much any computer you wish and used to manage firmware configurations and files. You won’t have the ‘ESPHome Dashboard’ in your HA console, but that’s not necessary either.
Sorry for asking, but is there also a possibility to go back to the stock firmware after flashing the ESPHome firmware? Is it just a matter of following these steps: Factory Flashing ?
Thank you
Yes, you can go back to the stock firmware without issue. Not sure how you got to that page in particular, but I would use the specific model pages and use whatever firmware they have listed there, such as:
The AirGradient ONE Air Quality Sensor (Presoldered-Version, PCB Version 9)
temperature monitors for air coming in and out of my HVAC
What hardware are you using for this?
I’m using 2 DS18b20 sensors I got off Amazon for cheap, integrated to ESPHome with this:
Dallas Temperature Sensor — ESPHome
Thanks @MallocArray , I’m not ignoring you I’ve just been out of control busy lately 
Tbh one thing I’ve really struggled with is which model of AirGradient’s I even have (looking at the instructions hasn’t completely helped and I don’t really want to dismantle them just to read a number on the PCB). This uncertainty makes me very uncomfortable to flash them with anything, official or not. Is there a way I can check definitively what models I have? (I’d thought they would show in the cloud app but it doesn’t seem to know, and after I set one model incorrectly I don’t even seem able to change it back to blank)
There are really only 4 primary models out there (6 if you want to get into the weeds)
Is yours an Indoor or Outdoor model?
If Indoor, did it come in the big white case?
If in the white case, does it have LEDs across the top?
Ultimately, I haven’t heard any reports of a board being bricked by doing any firmware, as there is a way to re-flash it even if it didn’t work as expected. So you can go between ESPHome or AirGradient firmware as you please.
Hi @MallocArray sorry for the recent spam, life has been way too busy and I could never work out how to switch my AirGradients to ESPhome. After using the AirGradients for about 8 months now they’ve ticked the box in terms of air quality monitoring but ticked none of the boxes they promised in terms of local logging, MQTT or openness etc.
I was seriously considering binning them, and then Home Assistant announced support in 2024.6 and I’m investigating further (hence the flurry of spam). So… clearly my pre-soldered versions were a dud purchase. I have now tried several things and not sure of the results.
I used the link you shared above to install basic ESPhome and can go to the device webpage that then didn’t allow me to install the BIN file because there wasn’t enough space.
I then used the link above to install the Pro BIN from your github, which appears to have worked successfully, and I can see in the UART logs (and the screen) that it’s working… but I can’t get to the device webpage, nor is it showing in the AirGradient app anymore. (the LCD is also using American measurements instead of Australian which I’m not sure how to change)
As far as I can tell the device is now working with ESPhome, but it’s no longer connecting to the Wifi I configured and it’s no longer able to re-configure it. I can connect to it in web.esphome.io and see logs etc, but clicking Configure Wifi gives the error below. le sigh.
I reflashed the device, with no improvement… then found a fix here: New device: An error occurred. Improv Wi-Fi Serial not detected - ESPHome - Home Assistant Community (home-assistant.io)
However since re-flashing I am no longer getting any CO2 reading on the screen (just shows NaN) and shows CO2 unknown in Home Assistant. Just did a calibration and it’s reappeared… not sure the PM readings are accurate (they’re quite bad despite this being inside and readings being ok before I flashed) but right now it’s time for bed.
So you got it to connect to HomeAssistant in the end? After flashing ESPHome the first time, if you didn’t provide the Wifi SSID and password in a YAML file, then it should default to creating its own Access Point that you could connect to with your laptop/phone and then select your home wifi for it to connect to long term. But I think you got that working.
I have seen after flashing, sometimes the sensors don’t always read fully until you unplug the power and connect it again so it gets a full reboot, so hopefully that will get you going if you are still seeing NaN for any readings.
I have several devices running ESPHome and the stock firmware and both give me the same numbers, so maybe PM is just high at the time you were writing this