From a226761cc6f08fe5df35d501d5d772412c19d52b Mon Sep 17 00:00:00 2001 From: Jens Timmerman <281523+JensTimmerman@users.noreply.github.com> Date: Sun, 5 Apr 2026 15:32:13 +0200 Subject: [PATCH 1/3] Add links to discovery methods in documentation Updated discovery methods with links to integration manifest documentation. --- .../rules/discovery.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/docs/core/integration-quality-scale/rules/discovery.md b/docs/core/integration-quality-scale/rules/discovery.md index fae698fa5b0..ce603009b4a 100644 --- a/docs/core/integration-quality-scale/rules/discovery.md +++ b/docs/core/integration-quality-scale/rules/discovery.md @@ -13,13 +13,13 @@ import RelatedRules from './_includes/related_rules.jsx' A lot of devices have the ability to be discovered. This can happen using one of the following methods: - App (formerly known as add-ons) -- Bluetooth -- DHCP -- HomeKit -- mDNS -- MQTT -- SSDP -- USB +- [Bluetooth](docs/creating_integration_manifest#bluetooth) +- [DHCP](docs/creating_integration_manifest#DHCP) +- [HomeKit](docs/creating_integration_manifest#HomeKit) +- [mDNS](docs/creating_integration_manifest#Zeroconf) +- [MQTT](docs/creating_integration_manifest#MQTT) +- [SSDP](docs/creating_integration_manifest#SSDP) +- [USB](docs/creating_integration_manifest#USB) This is a great way to make it easier for users to find and set up devices, since they don't have to manually look up which integration to use and then enter the host. This greatly reduces the effort required to set up a device and thus improves the user experience. @@ -115,6 +115,7 @@ class MyConfigFlow(ConfigFlow, domain=DOMAIN): To learn more information about config flows, checkout the [config flow documentation](/docs/config_entries_config_flow_handler). To learn more about discovery on network protocols, checkout the [Networking and discovery documentation](/docs/network_discovery). To learn more about discovery for bluetooth devices, checkout the [Bluetooth documentation](/docs/bluetooth). +To learn more about specifying different discovery methods in your manifest checkout the [Integration Manifest Documentation](docs/creating_integration_manifest). ## Exceptions @@ -123,4 +124,4 @@ Integrations where the devices can't be discovered are exempt from this rule. ## Related rules - \ No newline at end of file + From d716fa0839f2b8d6125ef3cc53a80ec96cc92dad Mon Sep 17 00:00:00 2001 From: Jens Timmerman <281523+JensTimmerman@users.noreply.github.com> Date: Sun, 5 Apr 2026 16:54:56 +0200 Subject: [PATCH 2/3] Fix links in discovery documentation --- .../integration-quality-scale/rules/discovery.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/core/integration-quality-scale/rules/discovery.md b/docs/core/integration-quality-scale/rules/discovery.md index ce603009b4a..c334cf9c93f 100644 --- a/docs/core/integration-quality-scale/rules/discovery.md +++ b/docs/core/integration-quality-scale/rules/discovery.md @@ -13,13 +13,13 @@ import RelatedRules from './_includes/related_rules.jsx' A lot of devices have the ability to be discovered. This can happen using one of the following methods: - App (formerly known as add-ons) -- [Bluetooth](docs/creating_integration_manifest#bluetooth) -- [DHCP](docs/creating_integration_manifest#DHCP) -- [HomeKit](docs/creating_integration_manifest#HomeKit) -- [mDNS](docs/creating_integration_manifest#Zeroconf) -- [MQTT](docs/creating_integration_manifest#MQTT) -- [SSDP](docs/creating_integration_manifest#SSDP) -- [USB](docs/creating_integration_manifest#USB) +- [Bluetooth](/docs/creating_integration_manifest#bluetooth) +- [DHCP](/docs/creating_integration_manifest#DHCP) +- [HomeKit](/docs/creating_integration_manifest#HomeKit) +- [mDNS](/docs/creating_integration_manifest#Zeroconf) +- [MQTT](/docs/creating_integration_manifest#MQTT) +- [SSDP](/docs/creating_integration_manifest#SSDP) +- [USB](/docs/creating_integration_manifest#USB) This is a great way to make it easier for users to find and set up devices, since they don't have to manually look up which integration to use and then enter the host. This greatly reduces the effort required to set up a device and thus improves the user experience. @@ -115,7 +115,7 @@ class MyConfigFlow(ConfigFlow, domain=DOMAIN): To learn more information about config flows, checkout the [config flow documentation](/docs/config_entries_config_flow_handler). To learn more about discovery on network protocols, checkout the [Networking and discovery documentation](/docs/network_discovery). To learn more about discovery for bluetooth devices, checkout the [Bluetooth documentation](/docs/bluetooth). -To learn more about specifying different discovery methods in your manifest checkout the [Integration Manifest Documentation](docs/creating_integration_manifest). +To learn more about specifying different discovery methods in your manifest checkout the [Integration Manifest Documentation](/docs/creating_integration_manifest). ## Exceptions From f01788864c90147ec0d74e9ec6fbb4e1a75ae28b Mon Sep 17 00:00:00 2001 From: Jens Timmerman <281523+JensTimmerman@users.noreply.github.com> Date: Tue, 7 Apr 2026 10:44:48 +0200 Subject: [PATCH 3/3] Fix link casing in discovery.md for consistency --- .../integration-quality-scale/rules/discovery.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/core/integration-quality-scale/rules/discovery.md b/docs/core/integration-quality-scale/rules/discovery.md index c334cf9c93f..b0d03a3fc3e 100644 --- a/docs/core/integration-quality-scale/rules/discovery.md +++ b/docs/core/integration-quality-scale/rules/discovery.md @@ -14,12 +14,12 @@ A lot of devices have the ability to be discovered. This can happen using one of the following methods: - App (formerly known as add-ons) - [Bluetooth](/docs/creating_integration_manifest#bluetooth) -- [DHCP](/docs/creating_integration_manifest#DHCP) -- [HomeKit](/docs/creating_integration_manifest#HomeKit) -- [mDNS](/docs/creating_integration_manifest#Zeroconf) -- [MQTT](/docs/creating_integration_manifest#MQTT) -- [SSDP](/docs/creating_integration_manifest#SSDP) -- [USB](/docs/creating_integration_manifest#USB) +- [DHCP](/docs/creating_integration_manifest#dhcp) +- [HomeKit](/docs/creating_integration_manifest#homekit) +- [mDNS](/docs/creating_integration_manifest#zeroconf) +- [MQTT](/docs/creating_integration_manifest#mqtt) +- [SSDP](/docs/creating_integration_manifest#ssdp) +- [USB](/docs/creating_integration_manifest#usb) This is a great way to make it easier for users to find and set up devices, since they don't have to manually look up which integration to use and then enter the host. This greatly reduces the effort required to set up a device and thus improves the user experience.