From b49835d6e3f393615b824554260200fda2df9dec Mon Sep 17 00:00:00 2001 From: Erik Hennig Date: Sun, 18 May 2025 09:29:25 +0200 Subject: [PATCH] Fix link in KNX documentation (#39077) --- source/_integrations/knx.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 94422587595..d08e5662c9f 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -2460,7 +2460,7 @@ entity_category: ## Known limitations -- The integration aims to be compatible with a wide variety of KNX devices from different manufacturers and eras. However, there are some devices that use non-standard DPT or use telegrams in a proprietary way. In these cases, you might not be able to configure {% term entities %} directly through this integration. However, you may still use [Template entities](integrations/template/) with the [KNX telegram trigger](#telegram-trigger) to work around this. +- The integration aims to be compatible with a wide variety of KNX devices from different manufacturers and eras. However, there are some devices that use non-standard DPT or use telegrams in a proprietary way. In these cases, you might not be able to configure {% term entities %} directly through this integration. However, you may still use [Template entities](/integrations/template/) with the [KNX telegram trigger](#telegram-trigger) to work around this. - USB bus interfaces are not directly supported by the underlying [`xknx` library](https://github.com/XKNX/xknx). However, you could try to run a software KNX router such as `Calimero` or `knxd` alongside Home Assistant to serve as a USB to IP bridge. For best reliability, using a certified KNX IP interface or router is recommended.