Trying to update my aeotec range extender through zwave-js (it let me know there was an update from 1.03 to 1.05), but getting the following error “failed to call service update/install. Z-Wave error 1506: Downloading the firmware update for node 5 failed: Could not detect firmware format (ZW1506).”
1 Like
“zwave-js” isn’t very specific. Are you talking about Z-Wave JS UI?
Well both in HA through the integration or via the UI I get that message…the fact there was an update got that in HA.
Ok, this looks like a bug in Z-Wave JS with the firmware update service that has probably been fixed. You’ll have to wait for a new version of the Z-Wave JS UI add-on that includes driver version v11.10.0.
1 Like
Of course, you have the option of downloading the file and manually installing it as well if you need to update right now.
gotcha did a pull today, so maybe already on that version or will take a peek later
Did someone find a link to the firmware for manual download?
Thanks,
The firmware is always available on Aeotec’s support website.
https://aeotec.freshdesk.com/support/search/solutions?term=range+extender+firmware
I have 3 of these, one paired to ZHA, one z2m and one zwave. Zwave updated to 1.5 on its own.
Z2M and other two, I have no idea what FW version they are on, it doesn’t seem to appear anywhere. I do have OTA update set on Z2M but don’t know if it’s done it.
Where would I find it?
I have a different, but seemingly related issue…I got notified of an update for the firmware today to 1.05, and proceeded with the update. As soon as the FW update was completed, it went offline, and now my Aeotec Range Extender is showing as dead in HA. I have already attempted to unplug the range extender, left it unplugged for about 30 seconds, and plugged it back in, but no change. It is flashing white consistently (but not super quickly, so it’s not in an inclusion/exclusion mode based on my understanding…)
What should I do next? Should I factory reset it and re-include it, or is there a better/more preferred way to address this issue? Then do I remove the dead device?
You should try that. My basic rule is never apply a firmware update unless the update fixes a specific issue you are having.
Hello @ehbush, the exact same happened here.
After upgrade “dead node” the quickest way (at least in my case) was:
- Remove dead node from HA
- Factory reset extender
- Rejoin.
I have 2 extenders and it happened to both. so I guess this is “expected behavior”. (or??)
Thanks @freshcoast, I got a bit confused by the numbering scheme. the V1.05 from the website contains SDK: v7.15.4 and FW: v1.5.0
What are you guys doing for this issue? The Update notification to upgrade the firmware to version 1.5 has been there for several days.
I have the latest zwave.js version:
I am currently using the following zwave.js version:
Changelog
0.1.87
Bug fixes
Z-Wave JS: Fixed a bug where firmware links that redirected to another URL were not supported
Z-Wave JS: Change order of commands so the startup does not fail when a controller is already set to use 16-bit node IDs and soft-reset is disabled
Z-Wave JS: Soft-reset is now always enabled on 700+ series controllers
Z-Wave JS: Queried user codes and their status are now preserved during re-interview when they won't be re-queried automatically
Config file changes
Add parameters 9-13 to Minoston MP21ZP / MP31ZP
Add fingerprint to Yale YRD446-ZW2
Add and update Yale Assure ZW3 series locks
Remove unnecessary endpoint functionality for CT101
Detailed changelogs
Bump Z-Wave JS to 11.10.0
Bump Z-Wave JS to 11.10.1
Error after update install reaches 100%…
2023-08-24T22:09:21.580Z CNTRLR » [Node 009] Sending firmware fragment 8277 / 8283
2023-08-24T22:09:21.620Z CNTRLR » [Node 009] Sending firmware fragment 8278 / 8283
2023-08-24T22:09:21.660Z CNTRLR » [Node 009] Sending firmware fragment 8279 / 8283
2023-08-24T22:09:21.700Z CNTRLR » [Node 009] Sending firmware fragment 8280 / 8283
2023-08-24T22:09:21.748Z CNTRLR » [Node 009] Sending firmware fragment 8281 / 8283
2023-08-24T22:09:21.791Z CNTRLR » [Node 009] Sending firmware fragment 8282 / 8283
2023-08-24T22:09:21.831Z CNTRLR » [Node 009] Sending firmware fragment 8283 / 8283
2023-08-24T22:09:22.442Z CNTRLR « [Node 009] Firmware update (part 1 / 1) failed with status Error_InvalidFirmwareTarget
I was able to resolve my issue. I had to move the range extender closer to the Zwave controller. It was in the other room.
For the upgrade to FW:1.5.0 after a number of failures I finally placed my two extenders close to the controller. After the upgrade the new version did not show. I had to:
- exclude the extenders from the network
- Factory reset the extenders
- Include the extenders again
Hopefully they will remain stable now.