Aeotec Recessed Door Sensor 7 (ZW187) Firmware Update Fails with Error_InvalidFirmwareTarget

[martinecker]

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.

[AlCalzone]

@Aeotec-ccheng do you have an idea what's going on?

[Aeotec-ccheng]

I am not sure here, but i've seen some failures with firmware update that don't process like this from time to time. The only solution i have seen is to unpair and re-pair the sensor and then try updating again.

Worst case, see if you can process the update in PC Controller 5.

[workingmanrob]

Well.. me too.

And there is a new firmware that also does the same thing. https://aeotec.freshdesk.com/support/solutions/articles/6000243778-update-recessed-door-sensor-7-v1-06-01

I have 2 ZW187 door sensors. When 1.6 firmware was released one updated fine the other said failed with status Error_InvalidFirmwareTarget

I just tried with firmware 1.6.1 and the one that took 1.6 updated fine the other is still on 1.5 and will not apply the update.

Using zwave JS via home assistant.

The log of the updated node..

2024-04-01T17:44:58.052529-04:00 berry addon_core_zwave_js[878]: 2024-04-01T21:44:55.127Z CNTRLR » [Node 018] Sending firmware fragment 6504 / 6504
2024-04-01T17:45:05.435876-04:00 berry addon_core_zwave_js[878]: 2024-04-01T21:45:05.434Z CNTRLR   [Node 018] Firmware updated, scheduling interview in 5 seconds...
2024-04-01T17:45:06.733058-04:00 berry addon_core_zwave_js[878]: 2024-04-01T21:45:06.026Z CNTRLR « [Node 018] received wakeup notification

And the failed node..

2024-04-01T18:53:34.559141-04:00 berry addon_core_zwave_js[878]: 2024-04-01T22:53:34.455Z CNTRLR » [Node 021] Sending firmware fragment 6504 / 6504
2024-04-01T18:53:37.640083-04:00 berry addon_core_zwave_js[878]: 2024-04-01T22:53:37.636Z CNTRLR « [Node 021] Firmware update (part 1 / 1) failed with status Error_InvalidFirmwa
2024-04-01T18:53:37.640624-04:00 berry addon_core_zwave_js[878]:                                   reTarget

I don't currently have another zwave controller so I can't try updating from a different system.

Will try the unpair - repair option but being an in wall sensor it's not easily accessible.