GIOŚ

The GIOŚ integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] uses the GIOŚ web service of the Polish Chief Inspectorate of Environmental Protection (Główny Inspektorat Ochrony Środowiska) as a source for air quality data for your location. The integration provides the current pollutant concentrations and air quality indices measured by a selected measuring station in Poland.

Use cases

• Monitor the outdoor air quality near your home.
• Get a notification to close the windows when the air quality is poor.
• Control your ventilation system or air purifier based on the air quality.
• Show the current outdoor air quality on your dashboard.

Configuration

To add the GIOŚ service to your Home Assistant instance, use this My button:

Supported functionality

The GIOŚ integration provides the following entities. Which entities are created depends on the pollutants measured by the selected measuring station.

Sensors

• Air quality index
  • Description: Shows the overall air quality index for the measuring station. The possible values are Very good, Good, Moderate, Sufficient, Bad, and Very bad.
• Benzene
  • Description: Shows the benzene (C6H6) concentration in micrograms per cubic meter.
• Carbon monoxide
  • Description: Shows the carbon monoxide (CO) concentration in micrograms per cubic meter.
• Nitrogen dioxide
  • Description: Shows the nitrogen dioxide (NO2) concentration in micrograms per cubic meter.
• Nitrogen dioxide index
  • Description: Shows the air quality index for nitrogen dioxide. The possible values are the same as for the Air quality index sensor.
• Nitrogen monoxide
  • Description: Shows the nitrogen monoxide (NO) concentration in micrograms per cubic meter.
• Nitrogen oxides
  • Description: Shows the nitrogen oxides (NOx) concentration in micrograms per cubic meter.
• Ozone
  • Description: Shows the ozone (O3) concentration in micrograms per cubic meter.
• Ozone index
  • Description: Shows the air quality index for ozone. The possible values are the same as for the Air quality index sensor.
• PM10
  • Description: Shows the concentration of particulate matter smaller than 10 micrometers in micrograms per cubic meter.
• PM10 index
  • Description: Shows the air quality index for PM10. The possible values are the same as for the Air quality index sensor.
• PM2.5
  • Description: Shows the concentration of particulate matter smaller than 2.5 micrometers in micrograms per cubic meter.
• PM2.5 index
  • Description: Shows the air quality index for PM2.5. The possible values are the same as for the Air quality index sensor.
• Sulphur dioxide
  • Description: Shows the sulphur dioxide (SO2) concentration in micrograms per cubic meter.
• Sulphur dioxide index
  • Description: Shows the air quality index for sulphur dioxide. The possible values are the same as for the Air quality index sensor.

The index sensors become unavailable when GIOŚ does not publish an index for the related pollutant.

GIOŚ automation examples

The following example shows how to use the integration in Home Assistant automations. It is just a starting point, and you can use it as inspiration to create your own automations.

Automation: Notify when the PM10 level is too high

This automation sends a notification to your mobile device when the PM10 level exceeds 100 µg/m³. Replace the entity ID in the example with the entity ID of your station’s PM10 sensor.

• Trigger: Numeric state crossed threshold
  • Entity: PM10 (sensor.czerniawa_pm10)
  • Above: 100
• Action: Send a notification message
  • Target: My Device (notify.my_device)
  • Title: High PM10 level alert
  • Message: The current PM10 level and a reminder to stay inside

alias: "Notify when the PM10 level is too high"
triggers:
  - trigger: numeric_state
    entity_id: sensor.czerniawa_pm10
    above: 100
actions:
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      title: "High PM10 level alert"
      message: >
        The PM10 level is too high at
        {{ states('sensor.czerniawa_pm10') }} µg/m³.
        Avoid going outside.

Data updates

The GIOŚ integration pollsData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more] data from the GIOŚ web service every 30 minutes. The GIOŚ terms of service allow downloading data no more than twice an hour, so this interval cannot be changed.

Known limitations

• The availability of sensors depends on the selected measuring station. Not all stations provide data for all pollutants or indices.
• GIOŚ may publish new measurements less frequently than every 30 minutes, so consecutive pollsData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more] can return unchanged data.

Troubleshooting

Removing the integration

This integration follows standard integration removal. No extra steps are required.

To remove an integration instance from Home Assistant

1. Go to Settings > Devices & services and select the integration card.
2. Next to the entry you want to remove, select the three dots menu. Then, select Delete.
   • Depending on the integration, the entries are listed under one of the following headings:
     • Devices
     • Hubs
     • Services
     • Integration entries
3. To confirm, select Delete.
   • Home Assistant also deletes the devices and entities of the entry.
4. If Home Assistant asks you to restart, restart Home Assistant.
5. If Home Assistant asks whether to also delete the application credentials, select Remove or Keep.
   • If you keep them, Home Assistant uses them automatically when you add the integration again.
   • To delete them later, refer to Deleting application credentials.