From 1a98131f76647b23d4e0c850602930c816599f94 Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Mon, 10 Mar 2025 15:52:25 +0100
Subject: [PATCH] Thread: remove mention of multiprotocol as it's been
discontinued (#37901)
* Thread: remove mention of multiprotocol as it's been discontinued
* Update source/_integrations/thread.markdown
---
source/_integrations/thread.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/thread.markdown b/source/_integrations/thread.markdown
index 5c8250b2da5..55d29437b8b 100644
--- a/source/_integrations/thread.markdown
+++ b/source/_integrations/thread.markdown
@@ -83,7 +83,7 @@ Unlike other protocols, Thread can use multiple border routers in a single netwo
OpenThread is an open source implementation of Thread, originally released by Google. Almost all commercially available Thread border routers are based on the open source implementation. However, the configuration of TBRs is not part of the Thread standard. This means that Google and Apple TBRs implementation setup and configured by their respective ecosystems.
-While Home Assistant can *use* any border router, it can *configure* and *control* only OpenThread border routers built with the REST API available in the open source implementation. The OpenThread Border Router add-on (as well as the OpenThread Border Router bundled in the experimental Silicon Labs Multiprotocol add-on) are built from this open source OpenThread code and have the REST API enabled.
+While Home Assistant can *use* any border router, it can *configure* and *control* only OpenThread border routers built with the REST API available in the open source implementation. The OpenThread Border Router add-on is built from this open source OpenThread code and has the REST API enabled.
### List of Thread border router devices