Mark Vogel's MotionMount integration as Bronze on the quality scale

[RJPoelstra]

Proposed change

This PR marks the integration has having reached Bronze

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

Bronze

• action-setup - Service actions are registered in async_setup - Integration doesn't have actions
• appropriate-polling - If it's a polling integration, set an appropriate polling interval - https://github.com/home-assistant/core/blob/84ae476b678fa0e593e83a01db16359ca021189b/homeassistant/components/motionmount/select.py#L19C1-L19C38
• brands - Has branding assets available for the integration
• common-modules - Place common patterns in common modules - https://github.com/home-assistant/core/blob/dev/homeassistant/components/motionmount/entity.py
• config-flow-test-coverage - Full test coverage for the config flow
• config-flow - Integration needs to be able to be set up via the UI
  • Uses data_description to give context to fields -

    core/homeassistant/components/motionmount/strings.json

    Line 15 in df166d1

    "data_description": {

  • Uses ConfigEntry.data and ConfigEntry.options correctly
• dependency-transparency - Dependency transparency - https://github.com/vogelsproducts/python-MotionMount
• docs-actions - The documentation describes the provided service actions that can be used - The integration doesn't have actions
• docs-high-level-description - The documentation includes a high-level description of the integration brand, product, or service - https://www.home-assistant.io/integrations/motionmount/
• docs-installation-instructions - The documentation provides step-by-step installation instructions for the integration, including, if needed, prerequisites - https://www.home-assistant.io/integrations/motionmount/#configuration
• docs-removal-instructions - The documentation provides removal instructions - https://www.home-assistant.io/integrations/motionmount/#removing-the-integration
• entity-event-setup - Entities event setup - The integration doesn't register events
• entity-unique-id - Entities have a unique ID -

  core/homeassistant/components/motionmount/number.py

  Line 47 in 84ae476

  self._attr_unique_id = f"{self._base_unique_id}-extension"

• has-entity-name - Entities use has_entity_name = True -

  core/homeassistant/components/motionmount/entity.py

  Line 23 in 84ae476

  _attr_has_entity_name = True

• runtime-data - Use ConfigEntry.runtime_data to store runtime data -

  core/homeassistant/components/motionmount/__init__.py

  Line 70 in 84ae476

  entry.runtime_data = mm

• test-before-configure - Test a connection in the config flow -

  core/homeassistant/components/motionmount/config_flow.py

  Line 54 in 84ae476

  info = await self._validate_input_connect(self.connection_data)

• test-before-setup - Check during integration initialization if we are able to set it up correctly -

  core/homeassistant/components/motionmount/__init__.py

  Line 36 in 84ae476

  try:

• unique-config-entry - Don't allow the same device or service to be able to be set up twice -

  core/homeassistant/components/motionmount/config_flow.py

  Line 72 in 84ae476

  self._abort_if_unique_id_configured(

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][dev-checklist]
• I have followed the [perfect PR recommendations][perfect-pr]
• The code has been formatted using Ruff (ruff format 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][docs-repository]

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

• The [manifest file][manifest-docs] 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.

To help with the load of incoming pull requests:

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

[zweckj]

please also add the rest of the quality scale

[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.

[zweckj]

and the rest too please

[RJPoelstra]

Are all your concerns handled? Shall I open it for review again?