ZHA: Move warning header into caution text block (#37645)

* Move warning header into caution text block to reduce redundant headers

* Move caution block into config requirements

* Use original phrasing for the specific scenario,  keep warning under hardware section

* Simplify Zigbee wording where reasonable
This commit is contained in:
kylehakala 2025-02-24 14:52:23 -06:00 committed by GitHub
parent e0097fa1a2
commit edb214f843
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -130,14 +130,16 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
- [ZiGate-Ethernet (Ethernet gateway board for PiZiGate)](https://zigate.fr/produit/zigate-ethernet/)
- [ZiGate + WiFi Pack](https://zigate.fr/produit/zigatev2-pack-wifi/)
#### Warning about using Zigbee Coordinator over Wi-Fi/WAN/VPN
{% caution %}
Be aware that using a Zigbee Coordinator via a Serial-Proxy-Server (also known as Serial-to-IP bridge or Ser2Net remote adapter) over a Wi-Fi, WAN, or VPN connection is not recommended.
Serial protocols used by the Zigbee Coordinator do not have enough robustness, resilience, or fault tolerance to handle packet loss and latency delays that can occur over unstable connections.
- It is **not recommended** to run a coordinator via **Serial-Proxy-Server** _(also called Serial-to-IP bridge or Ser2Net remote adapter)_ over:
- **Wi-Fi**,
- **WAN**, or
- **VPN**
A Zigbee Coordinator requires a stable local connection to its serial port interface with no drops in communication between it and the Zigbee gateway application running on the host computer.
- The coordinator requires a stable, local connection to its serial port interface without drops in communication with the Zigbee gateway application running on the host computer.
- Serial protocols used by the coordinator do not have enough robustness, resilience, or fault tolerance to handle packet loss and latency delays that can occur over unstable connections.
{% endcaution %}
## Configuration requirements