From 1b9de1c2bf1ae76d68e13088797cb92ce460276f Mon Sep 17 00:00:00 2001 From: kylehakala Date: Sat, 15 Mar 2025 23:22:44 +0000 Subject: [PATCH 1/3] Move zigbee 3.0 note to troubleshooting section --- source/_integrations/zha.markdown | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index f52612bc9a9..15bdd47c525 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -94,14 +94,6 @@ ZHA uses an open-source Python library called [zigpy](https://github.com/zigpy/z The hardware-independent design of this integration provides support for many Zigbee coordinators available from different manufacturers, as long as the coordinator is compatible with the [zigpy](https://github.com/zigpy/zigpy) library. -### Zigbee 3.0 support - -Some coordinators may not support firmware capable of Zigbee 3.0, but they can still be fully functional and feature-complete for your needs. Support for Zigbee 3.0 depends primarily on your coordinator hardware and firmware. - -{% note %} -Newer coordinators generally support Zigbee 3.0 firmware, but it is up to the manufacturer to make such firmware available to them. If your coordinator was shipped with an older firmware version, you may want to manually upgrade the firmware. -{% endnote %} - ### Recommended Zigbee radio adapters and modules - Silicon Labs EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy) @@ -908,3 +900,11 @@ services: When you see `NCP entered failed state. Requesting APP controller restart` in logs during normal operation, it indicates a drop in communication between ZHA and the serial interface of the Silabs EmberZNet Zigbee Coordinator. The EZSP (EmberZNet Serial Protocol) interface used by Silicon Labs EmberZNet Zigbee Coordinator adapters requires a stable connection to the serial port; therefore, it is not recommended to use a connection over Wi-Fi, WAN, VPN, etc. + +### Zigbee 3.0 support + +Some coordinators may not support firmware capable of Zigbee 3.0, but they can still be fully functional and feature-complete for your needs. + +{% note %} +It is up to hardware manufacturers to make such firmware available to them. If your coordinator was shipped with an older firmware version, you be able to manually upgrade the firmware. +{% endnote %} From d2a50399a79f830859cbb5ac6e45dcd4adb43775 Mon Sep 17 00:00:00 2001 From: kylehakala Date: Sun, 16 Mar 2025 00:03:09 +0000 Subject: [PATCH 2/3] format OTA section and collapse migrations --- source/_integrations/zha.markdown | 40 ++++++++++++++++--------------- 1 file changed, 21 insertions(+), 19 deletions(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index 15bdd47c525..e65166c0aa7 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -297,11 +297,11 @@ Additional devices in the [Compatible hardware](#compatible-hardware) section ma ### OTA updates of Zigbee device firmware -The ZHA integration has the ability to perform OTA (over-the-air) firmware updates of Zigbee devices. This feature is enabled by default. As it uses standard [Update](/integrations/update/) entities in Home Assistant, users will get a UI notification if and when an OTA firmware update is available for a specific device, with an option to initiate the update or ignore that specific update for the device. +The ZHA integration can perform over-the-air (OTA) firmware updates of Zigbee devices. -To see OTA updates for a device, it must support OTA updates and firmware images for the device must be publicly provided by the manufacturer. ZHA currently only includes OTA providers for a few manufacturers that provide these updates publicly. +A UI notification will be created if an OTA update is available for a device with an option to initiate or ignore the specific update for a device. -**Included manufacturers:** +To see OTA updates for a device, it must support OTA updates and the device's firmware must be publicly provided by the manufacturer. ZHA currently only includes OTA providers the following manufacturers that provide updates publicly: - IKEA - Inovelli @@ -561,19 +561,25 @@ Manual backups can also be created from the configuration page under **Network S ZHA supports migrating the Zigbee network between different Zigbee Coordinators based on chips from Silicon Labs, Texas Instruments, or ConBee/RaspBee if the backup was made from inside ZHA. -#### Prerequisites - -To migrate your Zigbee network from one Zigbee Coordinator to another, confirm you meet the following requirements before proceeding with the migration process: - -- The previous Zigbee Coordinator is used in the ZHA {% term integration %} and _not_ in deCONZ or MQTT. -- The radio type is one of the following: - - ezsp (Silicon Labs EmberZnet) - - znp (Texas Instruments Z-Stack ZNP) - - deCONZ (ConBee/RaspBee from dresden elektronik) - - For deCONZ (ConBee/RaspBee) radio adapters, make sure it is running [firmware 0x26700700 (from 2021-08-18)](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Firmware-Changelog) or later. - #### To migrate to a new Zigbee coordinator radio inside ZHA +Confirm you meet the following requirements before migrating: + +- The previous coordinator is used in the ZHA {% term integration %} and _not_ in deCONZ or MQTT. +- The radio type is one of the following: + - ezsp _(Silicon Labs EmberZnet)_ + - znp _(Texas Instruments Z-Stack ZNP)_ + - deCONZ _(ConBee/RaspBee from dresden elektronik)_ + - Be sure it is running [firmware 0x26700700 (from 2021-08-18)](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Firmware-Changelog) or later. + +{% details "To migrate to a new Zigbee coordinator radio inside ZHA:" %} + +{% important %} +You will not be able to control your existing Zigbee devices until the new coordinator fully joins the network after the migration. **This can take a few minutes.** + +If some existing devices do not resume normal functions after some time, try power-cycling them to attempt rejoining to the network. +{% endimportant %} + 1. Go to **{% my integrations title="Settings > Devices & services" %}** and select the ZHA {% term integration %}. Then select **Configure**. 2. Under **Network settings**, select **Migrate radio**. 3. Reconfiguration of ZHA will start. Select **Submit**. @@ -604,11 +610,7 @@ To migrate your Zigbee network from one Zigbee Coordinator to another, confirm y 11. Finally, a **Success!** message should pop up with information that all options were successfully saved. - Select **Finish** to confirm. -{% important %} -You will not be able to control your existing Zigbee devices until the new coordinator fully joins the network after the migration. **This can take a few minutes.** - -If some existing devices do not resume normal functions after some time, try power-cycling them to attempt rejoining to the network. -{% endimportant %} +{% enddetails %} ## Troubleshooting From 9d3ac3ef1080995ac5527067e5cddcbb2a652d1f Mon Sep 17 00:00:00 2001 From: kylehakala Date: Mon, 17 Mar 2025 10:49:27 -0500 Subject: [PATCH 3/3] Update source/_integrations/zha.markdown Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/zha.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index e65166c0aa7..fb5f9f01c30 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -561,7 +561,7 @@ Manual backups can also be created from the configuration page under **Network S ZHA supports migrating the Zigbee network between different Zigbee Coordinators based on chips from Silicon Labs, Texas Instruments, or ConBee/RaspBee if the backup was made from inside ZHA. -#### To migrate to a new Zigbee coordinator radio inside ZHA +#### Prerequisites Confirm you meet the following requirements before migrating: