Mark AVM Fritz!Smarthome as Gold integration

[mib1185]

Proposed change

Marks the AVM Fritz!Smarthome integration as Gold on the integration quality scale.

Silver 🥈

• ✅ Satisfying all No score level requirements.
• ✅ Connection/configuration is handled via a component.
• ✅ Set an appropriate SCAN_INTERVAL (if a polling integration)
• ✅ Raise PlatformNotReady if unable to connect during platform setup (if appropriate)
• ✅ Handles expiration of auth credentials. Refresh if possible or print correct error and fail setup. If based on a config entry, should trigger a new config entry flow to re-authorize. (docs)
• ✅ Handles internet unavailable. Log a warning once when unavailable, log once when reconnected.
• ✅ Handles device/service unavailable. Log a warning once when unavailable, log once when reconnected.
• ✅ Operations like service calls and entity methods (e.g. Set HVAC Mode) have proper exception handling. Raise ValueError on invalid user input and raise HomeAssistantError for other failures such as a problem communicating with a device.
• ✅ Set available property to False if appropriate (docs)
• ✅ Entities have unique ID (if available) (docs)

Gold 🥇

• ✅ Satisfying all Silver level requirements.

• ✅ Configurable via config entries.

  • ✅ Don't allow configuring already configured device/service (example: no 2 entries for same hub)
  • ✅ Discoverable (if available)
  • ✅ Set unique ID in config flow (if available)
  • ✅ Raise ConfigEntryNotReady if unable to connect during entry setup (if appropriate)
    needs Pass through connection error also during login hthiery/python-fritzhome#84
    needs Raise ConfigEntryNotReady when unable to connect during setup of AVM Fritz!Smarthome #97985

• ✅ Entities have device info (if available) (docs)

• ✅ Tests

  • ✅ Full test coverage for the config flow
  • ✅ Above average test coverage for all integration modules
  • ✅ Tests for fetching data from the integration and controlling it (docs)

• ✅ Has a code owner (docs)

• ✅ Entities only subscribe to updates inside async_added_to_hass and unsubscribe inside async_will_remove_from_hass (docs)

• ✅ Entities have correct device classes where appropriate (docs)

• ✅ Supports entities being disabled and leverages Entity.entity_registry_enabled_default to disable less popular entities (docs)

• ✅ If the device/service API can remove entities, the integration should make sure to clean up the entity and device registry.

• ✅ When communicating with a device or service, the integration implements the diagnostics platform which redacts sensitive information.

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:

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
• I have followed the perfect PR recommendations
• 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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @flabbamann, mind taking a look at this pull request as it has been labeled with an integration (fritzbox) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of fritzbox can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign fritzbox Removes the current integration label and assignees on the pull request, add the integration domain after the command.