Google Air Quality: support languageCode / localization based on hass.config.language

[eXPerience83]

Integration name

Google Air Quality

Link to integration documentation on our website

https://rc.home-assistant.io/integrations/google_air_quality

Describe the enhancement

The Google Air Quality integration currently doesn’t expose any way to control the languageCode used by the underlying API. As a result, human-readable fields such as categories, health recommendations, and pollutant descriptions are always returned in the default language instead of matching the user’s Home Assistant UI language.

It would be great if the integration could pass a configurable languageCode to the Google Air Quality API, ideally defaulting to hass.config.language, so that textual data is localized in the same language as the user’s Home Assistant interface. An optional override in the options flow would cover advanced use cases (for example, people who run HA in English but want air quality text in their local language).

This should be a purely additive change and backward-compatible: if languageCode is not set, the behavior would remain as it is today.

Use cases

• Consistent localization: Health recommendations, AQI categories, and pollutant descriptions appear in the same language as the rest of the Home Assistant UI, making the integration more user-friendly for non-English speakers.
• More readable notifications: Automations that send notifications (mobile, TTS, etc.) can include the raw API text directly without having to re-translate or maintain separate translation templates in YAML.
• Better dashboards for families: Lovelace dashboards that are meant for household members (children, elderly relatives, etc.) can show air quality messages in their preferred language, without extra template sensors or manual mapping.
• Parity with other integrations: Other services that support localization often respect hass.config.language; doing the same here would make Google Air Quality feel more integrated into the overall HA experience.

Anything else?

The Google Air Quality API supports languageCode directly in the request body. For example, a call to the currentConditions:lookup endpoint can include:

curl -X POST -d '{
  "universalAqi": true,
  "location": {
    "latitude": 37.419734,
    "longitude": -122.0827784
  },
  "extraComputations": [
    "HEALTH_RECOMMENDATIONS",
    "DOMINANT_POLLUTANT_CONCENTRATION",
    "POLLUTANT_CONCENTRATION",
    "LOCAL_AQI",
    "POLLUTANT_ADDITIONAL_INFO"
  ],
  "languageCode": "en"
}' \
-H 'Content-Type: application/json' \
'https://airquality.googleapis.com/v1/currentConditions:lookup?key=YOUR_API_KEY'

[github-actions[bot]]

🏷️ I've automatically added the integration: google_air_quality label to help categorize this feature request.

[Thomas55555]

Hi,
my approach was to make it all in English. This allows to make enum sensors, which shows all possible values. The states will get translated by the localize project, and if you change the language in the frontend the state will be shown in your language, as soon as the translation is available.
So even each member of a household could choose his favorite language.

This was a lot more work, than just use the language code, but I think this is the better solution.