Deprecate YAML config for AirVisual (0.119 removal)

[bachya]

Breaking change

Per ADR-0010, this PR deprecates YAML configuration for AirVisual until 0.119. Users who already use the AirVisual integration do not need to take action, as their configuration has already been imported into the UI.

Proposed change

Per ADR-0010, this PR deprecates YAML configuration for AirVisual until 0.119.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: N/A
• This PR is related to issue: N/A
• Link to documentation pull request: TBD

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[frenck]

Thanks, @bachya 👍

[GeorgeSG]

That's pretty cool, but now there is no way to setup AirVisualGeographySensors because there's no support for them in Config Flow.
Edit: by AirVusalGeographySensor I mean a sensor set up from country/state/city.

Are they being deprecated (and the only option will be lat/lng going forward), or is this just missing in the UI and needs to be added?

[bachya]

@GeorgeSG The UI configuration allows for the setup of geography sensors via latitude/longitude – is there a use case where country/state/city is more effective than latitude/longitude?

[GeorgeSG]

@bachya I'm new to this integration, but I think there is a use case, yes.

Whatever I try, I cannot add a sensor for this location: https://www.iqair.com/bulgaria/sofia/sofia-mladost. Any lat/long I choose defaults to https://www.iqair.com/bulgaria/sofia.

There are multiple stations in Sofia, and I can only setup a sensor for what seems to be the default one:

I am hoping being able to specify country/state/city will solve this problem.

[bachya]

@GeorgeSG Got it. And you can confirm that with the previous country/state/city YAML configuration, you could get the station you want?

[GeorgeSG]

@bachya I haven't used the integration before, will yaml config work with this version?

[bachya]

@GeorgeSG No, that has been removed as part of this PR – sorry, from your previous comments, I had assumed you had previously used this integration.

[PhilRW]

@bachya I have the use case. I tried setting up my location via lat/lon but it did not report correctly - kept giving me NOx readings instead of PM2.5. Using the YAML I configured the location by country/city/state and it's worked appropriately ever since. Something with their API, I guess. Anyway, I would appreciate a way to configure it via location name before the YAML is deprecated.

[bachya]

Thanks, @PhilRW – appreciate the info. I'm on it.

[bachya]

@GeorgeSG @PhilRW FYI, #44116 has added this. Too late for 2021.2.0, I'm afraid, so it will land in the March release. A reminder that if you don't want to wait until then, you can always download that PR as a custom component.