Use zeroconf attributes (A-D)

[epenet]

Proposed change

Use zeroconf attributes (A-D)
Follow-up to #58671

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

Additional information

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

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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• 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.

[Kane610]

This PR is incomplete. Please perform the same changes to the tests. For axis integration do the same changes to the tests to get an approval

[epenet]

This PR is incomplete. Please perform the same changes to the tests. For axis integration do the same changes to the tests to get an approval

I thought it was better / easier to review if the changes to test were kept separate from the changes to component code.
If the same mistake is made in both the component and the code, then it might not get picked up.

[Kane610]

This PR is incomplete. Please perform the same changes to the tests. For axis integration do the same changes to the tests to get an approval

I thought it was better / easier to review if the changes to test were kept separate from the changes to component code. If the same mistake is made in both the component and the code, then it might not get picked up.

If you're next PR fixes the related tests that's fine by me

[epenet]

If you're next PR fixes the related tests that's fine by me

Sure, it will be my next PR...

[Kane610]

Changes to axis integration looks good

[epenet]

@Kane610 draft PR prepared: #58836

[bdraco]

In the future, it would be good to do less integrations and update the tests at the same time.

[epenet]

Thanks @bdraco
I felt it was safer to update separately the code and the tests, but I will follow those instructions going forward.
Hard to find the balance sometimes.

[bdraco]

Thanks @bdraco I felt it was safer to update separately the code and the tests, but I will follow those instructions going forward. Hard to find the balance sometimes.

Should be safe if you:

• Update the code
• Run the test
• Update the tests