From 9411cc0c49fb8fc37a59244544cc84bcb07f3a13 Mon Sep 17 00:00:00 2001 From: Maikel Punie Date: Tue, 23 Dec 2025 09:28:48 +0100 Subject: [PATCH 1/3] update Velbus documentation --- source/_integrations/velbus.markdown | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/source/_integrations/velbus.markdown b/source/_integrations/velbus.markdown index 101989f4be9b..3ab605e1f14b 100644 --- a/source/_integrations/velbus.markdown +++ b/source/_integrations/velbus.markdown @@ -102,6 +102,24 @@ This step is optional. In the next step of the configuration, you have the option to import a Velbus VLP configuration file. This is the configuration file that you can export from the VelbusLink software. This will eliminate the need for a scan of the bus and will create all devices and entities based on the configuration file. +{% configuration_basic %} +vlp: + description: "Path to the VLP file to import during re-configuration. If not provided, no VLP file will be imported and a bus scan will be performed." +{% configuration_basic %} + +If you don't have a VLP file or don't want to import it, you can skip this step, and the integration will perform a scan of the bus to discover the connected modules, but this is known to be less reliable than using a VLP file. + +## Re-configuring the integration + +You can re-configure the Velbus integration by following these steps: + +{% include integrations/option_flow.md %} + +{% configuration_basic %} +vlp: + description: "Path to the VLP file to import during re-configuration. If not provided, no VLP file will be imported and a bus scan will be performed." +{% endconfiguration_basic %} + ## Actions - `velbus.sync clock`: Synchronize Velbus time to local clock. - `velbus.scan`: Scan the bus for new devices. From a266696d3747b3618bbfb869fa0302a385058f15 Mon Sep 17 00:00:00 2001 From: Maikel Punie Date: Tue, 23 Dec 2025 09:46:52 +0100 Subject: [PATCH 2/3] update correct closing --- source/_integrations/velbus.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/velbus.markdown b/source/_integrations/velbus.markdown index 3ab605e1f14b..3b36a11ebb60 100644 --- a/source/_integrations/velbus.markdown +++ b/source/_integrations/velbus.markdown @@ -105,7 +105,7 @@ This will eliminate the need for a scan of the bus and will create all devices a {% configuration_basic %} vlp: description: "Path to the VLP file to import during re-configuration. If not provided, no VLP file will be imported and a bus scan will be performed." -{% configuration_basic %} +{% endconfiguration_basic %} If you don't have a VLP file or don't want to import it, you can skip this step, and the integration will perform a scan of the bus to discover the connected modules, but this is known to be less reliable than using a VLP file. From ffe6daa45788ecefae5906f4a2507cba8d06cdb7 Mon Sep 17 00:00:00 2001 From: Maikel Punie Date: Wed, 24 Dec 2025 09:08:17 +0100 Subject: [PATCH 3/3] copilot sugestion fix --- source/_integrations/velbus.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/velbus.markdown b/source/_integrations/velbus.markdown index 3b36a11ebb60..aa840bbc67d0 100644 --- a/source/_integrations/velbus.markdown +++ b/source/_integrations/velbus.markdown @@ -104,7 +104,7 @@ This will eliminate the need for a scan of the bus and will create all devices a {% configuration_basic %} vlp: - description: "Path to the VLP file to import during re-configuration. If not provided, no VLP file will be imported and a bus scan will be performed." + description: "Path to the VLP file to import. If not provided, no VLP file will be imported and a bus scan will be performed." {% endconfiguration_basic %} If you don't have a VLP file or don't want to import it, you can skip this step, and the integration will perform a scan of the bus to discover the connected modules, but this is known to be less reliable than using a VLP file.