London Air
The london_air
integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] querieslocation
(local authority district or borough
Boroughs can have multiple monitoring sites at different geographical positions within the borough, and each of those sites can monitor up to six different kinds of pollutant. The pollutants are described herelatitude
and longitude
of each site is accessible through a data
attribute of the sensor, as are details about the pollutants monitored at that site. The sites
attribute of a sensor displays how many monitoring sites that sensor covers. The updated
attribute of a sensor states when the data was last published. Nominally data is published hourly, but in my experience this can vary. To limit the number of requests made by the sensor, a single API request is made every 30 minutes.
To add sensors to Home Assistant for all possible areas/boroughs add the following to your configuration.yaml
The configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file.
After changing the configuration.yaml
The configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file, restart Home Assistant to apply the changes. The integration is now shown on the integrations page under Settings > Devices & services. Its entities are listed on the integration card itself and on the Entities tab.
# Example configuration.yaml entry for a single sensor
sensor:
- platform: london_air
locations:
- Barking and Dagenham
- Bexley
- Brent
- Camden
- City of London
- Croydon
- Ealing
- Enfield
- Greenwich
- Hackney
- Haringey
- Harrow
- Havering
- Hillingdon
- Islington
- Kensington and Chelsea
- Kingston
- Lambeth
- Lewisham
- Merton
- Redbridge
- Richmond
- Southwark
- Sutton
- Tower Hamlets
- Wandsworth
- Westminster
To explore the data available within the data
attribute of a sensor use the dev-template
tool on the Home Assistant frontend. data
contains a list of monitored sites, where the number of monitored sites are given by the sites
attribute. If a sensor has four sites, access the fourth site by indexing the list of sites using data[3]. Each site is a dictionary with multiple fields, with entries for the latitude
and longitude
of that site, a pollution_status
, site_code
, site_name
and site_type
. The field number_of_pollutants
states how many pollutants are monitored (of the possible six) and the field pollutants
returns a list with data for each pollutant. To access the first pollutant in the list for site zero use attributes.data[0].pollutants[0]
. Each entry in pollutants
is a dictionary with fields for the pollutant code
, description
, index
, quality
and a summary
. Template sensors can then be added to display these attributes, for example:
# Example template sensors
template:
- sensor:
- name: "Updated"
state: "{{ state_attr('sensor.merton', 'updated') }}"
- name: "Merton PM10"
state: "{{ state_attr('sensor.merton', 'data')[0].pollutants[0].summary }}"
- name: "Westminster S02"
state: "{{ state_attr('sensor.westminster', 'data')[0].pollutants[3].summary }}"