I have an Aeotec zwa011 Z-Wave door sensor that I’d like to update the firmware on. The update is supposed to correct a deep sleep issue.
I use Z-Wave JS and have a copy of the firmware file for the device. I’m trying to use the update feature for the device, however, no matter what I try, the update fails.
On a couple of occasions the upload starts then fails at about 13% with a “fetch failed” error. Whatever that means? On other attempts the upload never starts and an error is received, "cannot connect (might be fine) the device.
I’ve made several attempts at updating the device even going as far us downloading and using SiLabs PC Connect application. Attempts and errors were similar.
I always make sure the device is awake prior to starting the upload and always press the small button on the side of the device when instructed to do so.
Who here has successfully updated a (Aeotec) Z-Wave device using Z-Wave JS? What steps did you take to do so?
That release added Aeotec update support. No need to download a file and attempt to upload it. After updating HA I found the zwa011 showed an update was available. Starting HA’s update process, removing the cover from then taping the button on the sensor, the update occurred. Nice!
I am on 2023.8.4 and saw the new FW for my AEOTEC devices popping up in the UI as well (in the past I already tried to update the FW manually without success).
But I don’t succeed with this either. It usually starts but never finishes.
Even on the mains powered one (no wake up to start the update needed, I guess)
I think I found at least one issue.
(I will report when confirmed)
But just a quick question:
Is it always required to re-include the device after an update?
By the way - one culprit I found is a alarm system close by (Lupus XT1 Plus using Zigbee).
Whenever I tried an update, the Alarmsystem went to communication error.
After switching off the Alarmsystem completely, I was able to update the AEOTEC Range extender.
however, I still have problems with 2 AEOTEC Temperature sensors (2 out of 4 are done though)
No, I meant re-include.
This was in fact required for my AEOTEC Range Extender, which is not a big deal though.
For other devices it would because of new node IDs / names to be changed in automations and dashboards.
