-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Socket connection and MQTT need to be stoped while Zigbee flash #70
Comments
But serial already didn't work while Zigbee flashing. And MQTT doesn't interfere at all. |
I tried these steps:
So i think may a ZHA or Socket Connection stop mechanism should work properly. Thanks very much for your support! |
Thanks for your feedback |
Yes a handy hint would be to tell people they might want to shutdown their instance of Zigbee2MQTT or ZHA down whilst updating Zigbee. I was only able to update OTA by stopping Zigbee2MQTT |
It seems to me that if you are going to update the firmware of a device, it would be logical to stop using it while the firmware is being updated. |
Indeed - I was putting this message up and suggesting a warning so future me remembers to stop Zigbee2MQTT first (or otherwise it freezes during the flash at x%). 💯 |
Because of the Zigbee FW Bug koenkk ZG FW Bug on P7 Coordinators #496 Would be great, if you could post a warning note or disable ZHA and MQTT before update starts. Thanks a lot for this support here! |
Guys, thanks a lot for your feedback. I'll keep it in mind. |
@LeonArmston @jdm09 |
I updated to new XZG: So it's not a 100% solution, but it's on a good way :) |
Help me out here... What's the clean process for upgrading the Zigbee firmware, or the ESP32 firmware? |
I could agree with you, but unless you are deep into Zigbee communications, this is how it appears to people: I don't usually have to think about what else may be going on when I tell a device to update. |
|
|
Thanks for the info. After I let it just sit overnight, it healed.
So the Z2M component doesn't need to be shut down, as the update process
stops communicating before starting the update.
The help is appreciated!
…On Sun, Jul 14, 2024, 08:10 xyzroe ***@***.***> wrote:
I could agree with you, but unless you are deep into Zigbee
communications, this is how it appears to people: So, this device has an
update available. I tell it to update. I expect the device will do whatever
it needs to do to update properly.
I don't usually have to think about what else may be going on when I tell
a device to update. And if I AM supposed to stop the Zigbee communications,
how do I disconnect the UZG-01/XZG device from the airwaves and Z2M and
still tell it to update? Why would I need to shut down Z2M? Can't the
UZG-01/XZG just "stop talking", do the upgrade, then start talking again??
1. XZG firmware, like UZG gateways and similar devices, are not
end-consumer products. Let's call them smart home enthusiast products
intended for testing and debugging software solutions. All responsibility
lies with you, and understanding the processes is required.
2. The device does everything necessary for the update on its own.
Your mistake occurred after the update was completed.
3. You do not need to disconnect the device for the update, only
stop/restart the software you are using.
4. After the firmware update, the device is "clean" and needs to be
brought back to a working state, which z2m does during its startup process.
It is not necessary to stop z2m; the gateway will stop communicating with
z2m on its own, but you must restart z2m immediately after the update. Many
users prefer to stop z2m before the update and start it afterward to be
safe. This is because z2m can make a backup of the coordinator's memory
during shutdown (on a clean firmware, this would be an empty backup), but
not all software solutions have this behavior.
—
Reply to this email directly, view it on GitHub
<#70 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB32XY5UKPLQADX4WYZMWEDZMJ2ETAVCNFSM6AAAAABJA2ALG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGM2DIMZQG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Originally posted by @xyzroe in #63 (comment)
The text was updated successfully, but these errors were encountered: