v0.5.0

[BJReplay]

What's Changed

• Additional air quality metrics by @autoSteve in Additional air quality metrics #26

This is a major new release that supports all of the pollutants recorded by the EPA.

It should upgrade from previous installations, but if you have any difficulties, given the way it supports new pollutants, it might be best to remove and then re-add the integration, so that it picks up the new pollutants that are available at many (but not all locations).

The integration sets up pollutants reported at the time a location is set up or discovered as the integration polls the EPA site. This allows for the scenario where pollutants are not reported at the time a location is set up because a sensor is out of action temporarily but is later restored - the pollutant is then enabled and becomes available automatically.

As for the last couple of releases, multiple locations are supported, as is fallback from hourly to 24-hour stats when the hourly stats are available.

The ability to choose whether to use PM2.5 or overall data for AQI is also supported but note that this may result in different AQI calculations than used by the EPA.

Feel free to discuss this release in the release discussion or raise an issue you run into a genuine issue.

Thanks again to @autoSteve for the work in this release, and to users for reporting issues and suggestions along the way.

Full Changelog: v0.4.9...v0.5.0

---

This discussion was created from the release v0.5.0.

[autoSteve]

Seamless upgrade for me on both 2025.11.2 and 2026.6.0 from 0.4.9 -> 0.5.0.

Downgrade to 0.4.7 okay on 2025.11.2, albeit with new entities unavailable (as expected). Subsequent upgrade 0.4.7->0.5.0 uneventful.

[BJReplay]

A bit of work for me, as I had the old entity names, and decided to take the hit and delete the original service to get a clean set up, but editing two dashboards in yaml mode was pretty straight forward to insert melbourne_cbd_ into each sensor