AirVisual


The airvisual sensor platform queries the AirVisual cloud API for air quality data. Data can be collected via latitude/longitude, by city/state/country, or from an AirVisual Node/Pro unit.

Using the AirVisual Cloud API

AirVisual API keys can be obtained here. Note that the platform was designed using the “Community” package; the “Startup” and “Enterprise” package keys should continue to function, but actual results may vary (or not work at all).

The Community API key is valid for 12 months after which it will expire. You must then go back to the AirVisual website, delete your old key, create a new one following the same steps and update your configuration with the new key.

The “Community” API key is limited to 10,000 calls per month. In order to accommodate using the same API key for multiple geographies, the airvisual integration will automatically “re-level” the time between API calls so as to not overrun the call limit.

For example:

  • One instance of the integration: API calls every 5 minutes
  • Two instances of the integration: API calls every 10 minutes
  • etc.

Using an AirVisual Node/Pro Unit

The integration can communicate to Node/Pro units over the local network. You will need the IP address/hostname of the unit and its Samba password (which can be found on the unit; instructions here: https://support.iqair.com/en/articles/3029331-download-the-airvisual-node-pro-s-data-using-samba).

Configuration

Home Assistant offers AirVisual Node/Pro Unit integration through Configuration -> Integrations -> AirVisual. Choose “Integration Type: AirVisual Node/Pro” and follow the instructions to get it set up.

The Cloud API integration can be done via the Integrations UI at Configuration -> Integrations -> AirVisual (Choose “Integration Type: Geographical Location”) or via YAML. To enable the integration and gather data via latitude/longitude using YAML, add the following lines to your configuration.yaml file:

airvisual:
    api_key: YOUR_AIRVISUAL_API_KEY

Note that an API key-based entry can be mixed with one or more Node/Pro-based entries (examples below).

Configuration Variables

api_key string (Optional)

Your AirVisual API key.

geographies list | map (Optional)

A list of geographical locations to monitor

latitude float (Inclusive)

The latitude of the location to monitor.

longitude float (Inclusive)

The longitude of the location to monitor.

city string (Inclusive)

The city to monitor.

state string (Inclusive)

The state the city belongs to.

country string (Inclusive)

The country the state belongs to.

Example Configurations

No explicit configuration (using the cloud API and the latitude and longitude defined within configuration.yaml):

airvisual:
    api_key: YOUR_AIRVISUAL_API_KEY

Configuration using the cloud API and a single custom latitude and longitude:

airvisual:
    api_key: YOUR_AIRVISUAL_API_KEY
    geographies:
        latitude: 42.81212
        longitude: 108.12422

Configuration using the cloud API and multiple custom latitude and longitude pairs:

airvisual:
    api_key: YOUR_AIRVISUAL_API_KEY
    geographies:
        - latitude: 42.81212
          longitude: 108.12422
        - latitude: 32.87336
          longitude: -117.22743

Configuration using the cloud API and a single city, state, and country:

airvisual:
    api_key: YOUR_AIRVISUAL_API_KEY
    geographies:
        city: Los Angeles
        state: California
        country: USA

Determining the City/State/Country

To easily determine the proper values for a particular location, use the AirVisual region directory. Once you browse to the particular city you want, take note of the breadcrumb title, which is of the form country > state/region > city. Use this information to fill out configuration.yaml.

For example, Sao Paulo, Brazil shows a breadcrumb title of Brazil > Sao Paulo > Sao Paulo. Thus, the proper configuration would look like this:

airvisual:
    api_key: YOUR_AIRVISUAL_API_KEY
    geographies:
        city: sao-paulo
        state: sao-paulo
        country: brazil

Sensor Types

When configured, the platform will create three sensors for each air quality standard:

Air Quality Index

  • Description: This sensor displays a numeric air quality index (AQI), a metric for the overall “health” of the air.
  • Example Sensor Name: sensor.chinese_air_quality_index
  • Example Sensor Value: 32
  • Explanation:
AQI Status Description
0 - 50 Good Air quality is considered satisfactory, and air pollution poses little or no risk
51 - 100 Moderate Air quality is acceptable; however, for some pollutants there may be a moderate health concern for a very small number of people who are unusually sensitive to air pollution
101 - 150 Unhealthy for Sensitive Groups Members of sensitive groups may experience health effects. The general public is not likely to be affected
151 - 200 Unhealthy Everyone may begin to experience health effects; members of sensitive groups may experience more serious health effects
201 - 300 Very unhealthy Health warnings of emergency conditions. The entire population is more likely to be affected
301+ Hazardous Health alert: everyone may experience more serious health effects

Air Pollution Level

  • Description: This sensor displays the associated Status (from the above table) for the current AQI.
  • Sample Sensor Name: sensor.us_air_pollution_level
  • Example Sensor Value: Moderate

Main Pollutant

  • Description: This sensor displays the pollutant whose value is currently highest.
  • Sample Sensor Name: sensor.us_main_pollutant
  • Example Sensor Value: PM2.5
  • Explanation:
Pollutant Symbol More Info
Particulate (<= 2.5 μm) PM2.5 EPA: Particulate Matter (PM) Pollution
Particulate (<= 10 μm) PM10 EPA: Particulate Matter (PM) Pollution
Ozone O EPA: Ozone Pollution
Sulpher Dioxide SO2 EPA: Sulfur Dioxide (SO2) Pollution
Carbon Monoxide CO EPA: Carbon Monoxide (CO) Pollution in Outdoor Air