Add quality_scale.yaml for KNX

[farmio]

Bronze

• config-flow - Integration needs to be able to be set up via the UI
  https://github.com/home-assistant/core/blob/dev/homeassistant/components/knx/config_flow.py
  • Uses data_description to give context to fields
    https://github.com/home-assistant/core/blob/dev/homeassistant/components/knx/strings.json
  • Uses ConfigEntry.data and ConfigEntry.options correctly
• test-before-configure - Test a connection in the config flow
• unique-config-entry - Don't allow the same device or service to be able to be set up twice
• config-flow-test-coverage - Full test coverage for the config flow
  https://github.com/home-assistant/core/blob/dev/tests/components/knx/test_config_flow.py
• runtime-data - Use ConfigEntry.runtime_data to store runtime data
• test-before-setup - Check during integration initialization if we are able to set it up correctly
  

  core/homeassistant/components/knx/__init__.py

  Lines 158 to 160 in bd0edd4

  	await knx_module.start()
  	except XKNXException as ex:
  	raise ConfigEntryNotReady from ex

• appropriate-polling - If it's a polling integration, set an appropriate polling interval
• entity-unique-id - Entities have a unique ID
  

  core/homeassistant/components/knx/entity.py

  Line 110 in 253098d

  self._attr_unique_id = unique_id

  
  YAML entities do it in their platform modules
• has-entity-name - Entities use has_entity_name = True
  

  core/homeassistant/components/knx/entity.py

  Line 103 in 253098d

  _attr_has_entity_name = True

  
  YAML entities don't use this as they don't support devices
• entity-event-setup - Entities event setup
  

  core/homeassistant/components/knx/entity.py

  Line 78 in 253098d

  self._device.register_device_updated_cb(self.after_update_callback)

• dependency-transparency - Dependency transparency
  https://github.com/XKNX
• action-setup - Service actions are registered in async_setup
  

  core/homeassistant/components/knx/__init__.py

  Line 140 in 253098d

  register_knx_services(hass)

• common-modules - Place common patterns in common modules
  https://github.com/home-assistant/core/blob/dev/homeassistant/components/knx/entity.py
• docs-high-level-description - The documentation includes a high-level description of the integration brand, product, or service
  https://www.home-assistant.io/integrations/knx/
• docs-installation-instructions - The documentation provides step-by-step installation instructions for the integration, including, if needed, prerequisites
  https://www.home-assistant.io/integrations/knx/#configuration
• docs-removal-instructions - The documentation provides removal instructions
• docs-actions - The documentation describes the provided service actions that can be used
  https://www.home-assistant.io/integrations/knx/#actions
• brands - Has branding assets available for the integration
  https://github.com/home-assistant/brands/tree/master/core_integrations/knx

Silver

• config-entry-unloading - Support config entry unloading
  

  core/homeassistant/components/knx/__init__.py

  Line 186 in bd0edd4

  async def async_unload_entry(hass: HomeAssistant, entry: ConfigEntry) -> bool:

• log-when-unavailable - If internet/device/service is unavailable, log once when unavailable and once when back connected
• entity-unavailable - Mark entity unavailable if appropriate
  

  core/homeassistant/components/knx/entity.py

  Lines 64 to 66 in 8f6e4cd

  	def available(self) -> bool:
  	"""Return True if entity is available."""
  	return self._knx_module.connected

• action-exceptions - Service actions raise exceptions when encountering failures
• reauthentication-flow - Reauthentication flow
• parallel-updates - Set Parallel updates
• test-coverage - Above 95% test coverage for all integration modules
• integration-owner - Has an integration owner
  https://github.com/home-assistant/core/blob/dev/homeassistant/components/knx/manifest.json
• docs-installation-parameters - The documentation describes all integration installation parameters
• docs-configuration-parameters - The documentation describes all integration configuration options

Gold

• entity-translations - Entities have translated names
• entity-device-class - Entities use device classes where possible
• devices - The integration creates devices
• entity-category - Entities are assigned an appropriate EntityCategory
• entity-disabled-by-default - Integration disables less popular (or noisy) entities
• discovery - Can be discovered
• stale-devices - Clean up stale devices
• diagnostics - Implements diagnostics
  https://github.com/home-assistant/core/blob/dev/homeassistant/components/knx/diagnostics.py
• exception-translations - Exception messages are translatable
• icon-translations - Icon translations
• reconfiguration-flow - Integrations should have a reconfigure flow
• dynamic-devices - Devices added after integration setup
• discovery-update-info - Integration uses discovery info to update network information
• repair-issues - Repair issues and repair flows are used when user intervention is needed
• docs-use-cases - The documentation describes use cases to illustrate how this integration can be used
• docs-supported-devices - The documentation describes known supported / unsupported devices
• docs-supported-functions - The documentation describes the supported functionality, including entities, and platforms
• docs-data-update - The documentation describes how data is updated
• docs-known-limitations - The documentation describes known limitations of the integration (not to be confused with bugs)
• docs-troubleshooting - The documentation provides troubleshooting information
• docs-examples - The documentation provides automation examples the user can use.

Platinum

• async-dependency - Dependency is async
• inject-websession - The integration dependency supports passing in a websession
• strict-typing - Strict typing

[home-assistant]

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

Code owner commands

Code owners of knx 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 knx Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[gjohansson-ST]

CI is failing (all seems related to missing translations)

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

[farmio]

Should be fixed by #134078