Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZHA troubleshooting Zigbee OTA upgrades of device firmware #35884

Draft
wants to merge 3 commits into
base: current
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions source/_integrations/zha.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -583,6 +583,14 @@ Since all Zigbee Coordinator radio adapters are very sensitive/susceptible to al
- Place your Zigbee Coordinator away from any Wi-Fi access points and all other sources of WiFi.
- Wi-Fi frequency ranges can overlap with Zigbee, see the section above on defining Zigbee channel use.

### Problems upgrading Zigbee device firmware via OTA

Be aware that OTAU (Over-The-Air Upgrade) of Zigbee devices typically takes around 10 minutes. While a device is updating a lot of traffic is generated on the network, therefore it is recommended to not execute multiple updates at the same time. Always check that battery-powered devices have at least 70% of battery-life left before starting a firmware upgrade (a general tip is therefore to simply put new fresh batteries in before upgrading any OTA firmware upgrade), OTA updating of firmware is very power-consuming and while some devices do check for a minimum battery-level before starting the upgrade and might refuse to update unless have enough battery-life left, not all do so.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

therefore it is recommended to not execute multiple updates at the same time.

This is not something we should burden our users with. If this is an issue it should be fixed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Always check that battery-powered devices have at least 70% of battery-life left before starting a firmware upgrade

Same.


If Zigbee firmware upgrades do not start on a battery-powered product, then be aware that you usually need to "wake up the device" so that it will be able to receive commands (because battery-powered products are sleepy devices, so they normally only receive commands when the state of the device is changed). If the upgrade still does not start, then try restarting the device by disconnecting the power/battery for a few seconds and try again; make sure to activate the device by pressing a button on it right before sending the update request. Try to push a button on the device (if it has one) shortly before you start the firmware update to wake it up. Sometimes, it also helps to try keeping the device awake by repeatedly pushing a button until you see the first "Updating... " message in the user interface.

Another common reason for Zigbee firmware upgrades not starting or failing is poor reception or not having a stable Zigbee network mesh. Take action to try to optimize your Zigbee network by avoiding radio frequency interference and adding many Zigbee Router devices (repeaters/extenders) to extend range and coverage. Try to follow all the best practice tips above in the [Zigbee interference avoidance and network range/coverage optimization)](#zigbee-interference-avoidance-and-network-rangecoverage-optimization) section under troubleshooting.

### Zigbee network visualization in ZHA UI

The ZHA configuration UI has a tab to visualize device links in your Zigbee network topology.
Expand Down
Loading