iaqualink: add initial quality scale assessment

[flz]

Breaking change

Proposed change

Add initial quality scale assessment for iaqualink integration.

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)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

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

[Copilot]

Pull request overview

Adds an initial Integration Quality Scale (IQS) assessment for the iaqualink integration and updates hassfest so the new assessment file is recognized.

Changes:

• Remove iaqualink from hassfest’s “missing quality scale file” allowlist.
• Add homeassistant/components/iaqualink/quality_scale.yaml with an initial set of rule statuses (done/todo/exempt).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
script/hassfest/quality_scale.py	Stops treating iaqualink as an integration without a quality_scale.yaml.
homeassistant/components/iaqualink/quality_scale.yaml	Introduces the integration’s initial IQS self-assessment ruleset.

[justanotherariel]

A few remarks

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

[flz]

A few remarks

Thanks for the quick review!

Given there are only two todo's for Bronze, I'll leave this PR as Draft as someone suggested on Discord and submit two PRs to address the fixes. When merged, I'll update this one but bump the integration quality level to Bronze.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[joostlek]

Why not? Did you check mDNS or DHCP? what is the mac address and what is the hostname?

[flz]

No mDNS that I could see.

I didn't see discovery mechanism based on MAC (not sure how reliable it would be given there's a few different products by different manufacturers) or DHCP. Any good integration examples?

[flz]

Following up here: #168256

[joostlek]

turning on a light or climate also is an action

[flz]

I thought it was for integration-specific actions?

[flz]

Documentation says no exception but I'm not sure what should go in that part of the documentation?

[joostlek]

I think I should reword it better, but the built in actions that can raise also should be handled well

[flz]

Exceptions were already largely handled by I found some inconsistent handling, opened a PR here: #168268