Today, if you query the firmware update service, you will only see updates if there are firmware updates available for the device in question. When you don't see any updates, however, it's hard to know whether that means that the device IS supported by the update service but has no updates available or the device ISN'T supported by the update service and therefore has no updates available.

One suggestion @AlCalzone had on Discord was to return a null instead of an empty list to indicate that the device is not supported by the service. Not sure if this needs to go into the service itself or into the caller, but starting here for tracking purposes

there is a mistake in the version number of the range extender 7 from Aeotec. On their homepage is 1.0.5 published as the actual Version. In zwabe-js its numbered as 1.5.

see https://aeotec.freshdesk.com/support/solutions/articles/6000244478-update-range-extender-7-v1-05

i tried to update via zwave-js an got an error, maybe that's the reason?

The install succeeds, but the version is misreported.

#40
Some customers outside the United States have had the United States firmware installed on their device bricking it in the process. Would like to be able to lock firmware files to a specific region if possible

Hey @AlCalzone , received your email on the issue.
We have .gbl files hosted on our website but I am unable to find the documentation if .gbl files are compatible.

e.g.
#26
Current that is failing:
"url": "https://gist.githubusercontent.com/habhomegit/b9101ec4b3e3b57dde31458f48055bd0/raw/a410973b437ac72d96930bb6faf7732cfbc6c827/iBlinds_V3.12.hex",
"integrity": "sha256:f0007bd8e41ebe12f05d06c90c1e0ae15581eb60a88ccd2802f63ac43b62261b"

Possible Solution:
"url": "https://support.myiblinds.com/wp-content/uploads/2021/09/iBlinds_v3.12_US.gbl",

Some manufacturer of z-wave devices provides their firmware files via "z-wave europe" (official files).
https://z-wave.freshdesk.com/support/solutions/articles/80001056676-firmware-for-devices

May be it is possible to include these files as an optional update path?

1.30 is actually 1.30.1
1.20 is actually 1.20.1

Hi

Aoetec host firmware for their Smartswitch v6 on their website, but it is not showing through the zwave-js update service. I assume this is because a definition file has not been created.

Is the firmware listed on this Aeotec support article going to be okay to build a definition for, or is there more to the process?

https://aeotec.freshdesk.com/support/solutions/articles/6000134294-how-to-update-smart-switch-6-z-wave-firmware-

Thanks!

Add multi target support for Inovelli Red Series 2-in-1 VZW31-SN. Requires target 0 for otz and target 1 for bin.

node:path keeps backwards slashes on Windows, path-browserify does not like them.

see #72 (review)

Hello,

After updating these nodes I lost power monitoring and the keypress 2X triggers the scene and the relay at the same time. Before the update, a double click would only trigger the scene.

Thanks

See support page here: https://hubconnecteddecorasmart.leviton.com/hc/en-us/articles/4407521680155-Can-Leviton-Z-Wave-Products-Firmware-Be-Updated-

Looks like these updates are included in Homeseer.

#121 added ZEN51, but only added 0x0904:0x0201 for Type:Id
My device is reporting as 0x0104:0x0201 so it is not detecting the update.

Both of these product types are listed for this device in the Device Database

It is possible that other Zooz devices are similarly missing detection from alternate product identifiers. Here are the devices I found from the database which had alternate identifiers listed which are not in this repo:

• ZEN17
• ZEN21
• ZEN32
• ZEN51
• ZEN52

This also requires to update FirmwareUpdateInfo interface on zwave-js side

Hi,

I'm not an expert of this repo, so i'm not really sure how to add these firmwares to the database.

But Shelly has made their firmwares publicly available for their 4 new Zwave modules

https://support.shelly.cloud/en/support/solutions/articles/103000258471-firmware-updates

Could some integrate them to this repo ? Or tell me how to do so ? Thanks in advance :)

I'll be on paternal leave for the rest of 2022

This means I won't review Pull Requests here, unless I need to kill some time.
If an update should be added here in the meantime, make sure to follow the documentation and especially the parts about the changelog and providing the correct integrity hash in this section. This makes it more likely that I'll be able to merge the updates.

In case of emergency (like firmware updates that must be removed)
...please reach me on the zwave-js Slack - it may still take a bit of time to answer

Take care and see you in 2023
– AlCalzone

https://www.npmjs.com/package/@fastify/helmet

Please provide support for Zooz devices, as per https://www.support.getzooz.com/kb/article/1158-zooz-ota-firmware-files/

Thanks! :)

Hi,

I have two Aeotec Recessed Door Sensors ZW187 that I've been trying to update the firmware for from 1.5 to 1.6.
I tried both using the firmware registry built-in to zwave-js as well explicitly with the .glb file (for US frequency) downloaded from here: https://aeotec.freshdesk.com/support/solutions/articles/6000243778-update-recessed-door-sensor-7-v1-05

Every time I hit this failure after the upload of the .gbl file succeeds:

2/4/2024, 2:19:06 PM - FIRMWARE UPDATE FINISHED
Arg 0:
└─success: false
└─status: 4
└─reInterview: false
2/4/2024, 2:19:03 PM - FIRMWARE UPDATE PROGRESS
Arg 0:
└─currentFile: 1
└─totalFiles: 1
└─sentFragments: 6504
└─totalFragments: 6504
└─progress: 100

The last few entries from the debug log for one of these sensors (Main Fence Gate):

2024-02-04 16:21:08.542 DEBUG MQTT: Publishing to zwave/Outside/Main_Fence_Gate/lastActive: { time: 1707092468541, value: 1707092468501 } with options { qos: 1, retain: true }
2024-02-04 16:21:08.752 DEBUG MQTT: Publishing to zwave/Outside/Main_Fence_Gate/lastActive: { time: 1707092468751, value: 1707092468737 } with options { qos: 1, retain: true }
2024-02-04 16:21:08.988 DEBUG MQTT: Publishing to zwave/Outside/Main_Fence_Gate/lastActive: { time: 1707092468987, value: 1707092468947 } with options { qos: 1, retain: true }
2024-02-04 16:21:09.199 DEBUG MQTT: Publishing to zwave/Outside/Main_Fence_Gate/lastActive: { time: 1707092469198, value: 1707092469191 } with options { qos: 1, retain: true }
2024-02-04 16:21:09.441 DEBUG MQTT: Publishing to zwave/Outside/Main_Fence_Gate/lastActive: { time: 1707092469441, value: 1707092469250 } with options { qos: 1, retain: true }
2024-02-04 16:21:12.470 DEBUG MQTT: Publishing to zwave/Outside/Main_Fence_Gate/lastActive: { time: 1707092472469, value: 1707092472469 } with options { qos: 1, retain: true }
2024-02-04 16:21:12.477 INFO Z-WAVE: [Node 010] Firmware update finished with error.
   Status: Error_InvalidFirmwareTarget.
   Wait before interacting: No.
   Result: {"success":false,"status":4,"reInterview":false}.
2024-02-04 16:21:12.480 INFO Z-WAVE: Success zwave api call firmwareUpdateOTA { success: false, status: 4, waitTime: undefined, reInterview: false }
2024-02-04 16:21:12.719 DEBUG MQTT: Publishing to zwave/Outside/Main_Fence_Gate/lastActive: { time: 1707092472719, value: 1707092472469 } with options { qos: 1, retain: true }

I'm not sure what the error InvalidFirmwareTarget means. Z-Wave JS UI shows the Target as being 0 and that's also the only one I can choose.
Anyone have any ideas or suggestions?

Thanks.

Is there a way to pull Zooz firmware into the service? All their firmware files are on their site.

https://www.support.getzooz.com/kb/article/1158-zooz-ota-firmware-files/

Thanks

Hello,

it seems firmware for the shelly wave devices is made public on github. Is this usable?
https://github.com/QubinoHelp/Shelly_Wave_FW_OTA/

Edit: source on their website directing to the github repo: https://support.shelly.cloud/en/support/solutions/articles/103000258471-firmware-updates

For anyone interested:
https://byjasco.com/support/resource-library/connected-home-firmware-downloads
https://github.com/jascoproducts/firmware

I purchased a Zooz ZEN04 800 series smart plug and it came with firmware 2.10.1 (as reported by Home Assistant/Z-Wave JS). I then used HA to update the firmware via OTA, from an automatic notification in HA, to firmware 2.20.1. After the update, the firmware as reported by the device is now 2.20, causing HA to think it still needs a firmware update to 2.20.1. When I attempt to update the firmware again, I get the error: Failed to call service update/install. zwave_error: Z-Wave error 263 - Cannot update firmware for node xx: The update is for a different original firmware version! (ZW0263)

I believe the version in ZEN04-800.json should be "2.20" rather than "2.20.1", since this is what the device reports.

Link to publicly available firmware:

https://minoston.com/pages/minoston-firmware-drive