Add support for AirVisual Node/Pro units

[bachya]

Proposed change

This PR adds support for AirVisual Node/Pro units to the airvisual integration. The integration talks to the device locally via Samba.

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
airvisual:
  ip_address: 192.168.1.101
  password: 12345

Additional information

• This PR fixes or closes issue: N/A
• This PR is related to issue: N/A
• Link to documentation pull request: Add AirVisual Node/Pro docs home-assistant.io#12382

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

[bachya]

Marking this as WIP because just as I finished it, I learned that I may be able to access the data locally... 😱 Although the PR will be very similar, there is enough of a change that I'm going to close this one and will re-approach.

[bachya]

Re-opening, as the work wasn't as bad as I'd anticipated.

[MartinHjelmare]

Please rebase to solve the merge conflicts.

[bachya]

@MartinHjelmare It's on my to-do list. 👍

[balloob]

Rebasing still on to-do list?

[bachya]

@balloob I've rebased it twice thus far; since it's been hanging out, there have been ongoing changes in dev. Will push it again today.

EDIT: ended up being pretty simple. 👍

[bachya]

I know ADR-0010 has been approved since I originally created this; do I need to rip out configuration.yaml support here? Or subsequent PR?

[MartinHjelmare]

We don't want to add more things to the config yaml. We also don't want to remove the config yaml without a deprecation period.

Just add the new options to the config flow and leave the config yaml schema untouched, I think.

[bachya]

Thanks, @MartinHjelmare. Going to move this to a draft in the meantime; no reason to review until it's fully ready.

[bachya]

It ended up being pretty easy to remove configuration.yaml support for this new functionality (pushed via 795190b). Good for review.

[MartinHjelmare]

Looks good! Just a small comment.

[MartinHjelmare]

Nice!