Having trouble updating Z-wave smart switch firmware

thany · December 22, 2025, 10:12am

Trying to update a Shelly smart switch model QNPL-0A112 over Z-wave. It’s currently on firmware 10.4, and it wants to go to 11.4. It even shows a sensible list of improvements in the update notification.

After a long process of sending the new firmware to the device, the log goes at the end:

2025-12-22 10:53:57.494 CNTRLR » [Node 007] Sending firmware fragment 6880 / 6881
2025-12-22 10:53:57.531 CNTRLR » [Node 007] Sending firmware fragment 6881 / 6881
2025-12-22 10:53:57.679 CNTRLR « [Node 007] Firmware update (part 1 / 1) failed with status Error_InvalidFirmwa
                                 reTarget

This log is in device info → Configure → Logs.

I’ve tried it 3 times by now, so this is not a fluke.

There’s also an entry in the system log:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:331
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 01:10:06 (3 occurrences)
Last logged: 10:53:57

[139939357739904] Error during service call to update.install: Error Invalid Firmware Target
[139940064274176] Error during service call to update.install: Error Invalid Firmware Target
[139939340925536] Error during service call to update.install: Error Invalid Firmware Target

Which I think is basically the same information, just with the WebSocket thing there. I don’t think the error is caused by a faulty WebSocket service, as other firmware updates (of different devices, admittedly) went perfectly alright.

I’m on the following versions of everything involved, meaning I get no additional update notifications for any of these:

HA Core 2025.12.4
HA Supervisor 2025.12.3
HA Operating System 16.3
Z-wave Driver version: 15.15.0
Z-wave Server version: 3.4.0

Does anybody know what’s actually going on, and perhaps a fix?

checking12 · December 22, 2025, 11:20am

the fact this error is indicating the firmware is not meant for this device, makes it kinda concerning.Maybe look for an other source downloading the firmware and apply manually?

thany · December 22, 2025, 1:30pm

Can try that. How do I “apply manually” though? As mentioned, it’s a Z-wave device, so it kinda has to go through HA, as I don’t have another Z-wave capable hub or anything like that.

checking12 · December 22, 2025, 2:27pm

now this gets funnier. Seems I have the same device in my network (while figuring out where OTA could be triggered for you).
in ZWAVEJSUI

points to FW at

github.com/QubinoHelp/Shelly_Wave_FW_OTA

Wave_Plug_S/README.md

d16fc6e14


**version [11.04] - [2025-05-15]**
  - Added kWh precision, 2 decimals 
  - Added min value for Par 105 -> 0 - off
  - Added Indicator Command Class
  - Removed Parameters 91 - 94
  - Removed Association group 3
  - Removed voltage & ampere reports
  - Other minor Fixes & Improvements

**version [10.04] - [2024-10-30]**
- initial firmware release

but fhe file name suggests a LR device.

I went bold and pressed update:

and it finally succeeded:

you have a option to use zwave JSUI?

thany · December 22, 2025, 4:03pm

I just moved to the JS UI, and I’m getting the same as you. The tricky bit I find, is that this firmware is nowhere to be found on Shelly’s website. Was trying to look there, for they might specify which range of devices this update is applicable to.

At the OTA archive though, I found this:

Yes, QNPL, rather than QLPL.

And also this issue:

github.com/QubinoHelp/Shelly_Wave_FW_OTA

"White" Wave Plugs S LR Firmware

opened 05:51PM - 07 Nov 25 UTC

memphi2

I saw that a firmware update to FW 11.04 and SDK 7.23.1 had been released for th…e Wave Plug S. The file name contains a reference to long-range functionality: Wave_PlugS_800_EU**_LR_**20250519_1500_QLPL-0A112EU_[11.04]___9DD2F96C.gbl Unfortunately, LR does not work with the white plugs. No Long Range Smart Start Request is sent. I just see this request in the log: ``` [REQ] [ApplicationUpdateRequest] type: SmartStart_HomeId_Received ``` but expecting this: ``` [REQ] [ApplicationUpdateRequest] type: SmartStart_LongRange_HomeId_Received ``` The black plugs with identical hardware and firmware, on the other hand, of course runnnig smoothly in LR mode. Is this limitation intentional? Will there be a “working” update for LR mode in the future? The black plugs are just too ugly, my wife refuses to install them. And the range without LR is just too short :( Regards, Oliver

I find it rather confusing, tbh. They are two different devices, but the maintainer basically says “trust me bro, it works because so-and-so”, and case closed, not realising this is causing errors.

thany · December 22, 2025, 4:17pm

But, after trying it anway just like you did, no success:

And just to confirm:

Back where it started.

checking12 · December 23, 2025, 10:01am

Thats weird, would almost suspect the download is faulty. I dont know the process if download is cached or downloaded everytime you try the update.

The only thiing i could think of to try:

remove device from zwave network
include the device again
try updating firmware

Really hope it’s something stupid thats get resolved by readding the device.

bidouilleur · December 23, 2025, 3:31pm

I have just been struggling with these plugs too though I have the feeling there is some bug. I found the firmware online for my EU version and applied that one manually (slow). After update it says failed (something of mismatch of hardware and firmware).
But when I open the details I see this. Not sure what is what and the plugs still are to be updated according the HA.

checking12 · December 23, 2025, 3:53pm

in that case i would do a reinterview or look in JSUI for firmware reported. Curios what will happen in all cases

noXi0815 · December 23, 2025, 9:36pm

Thanks god I am not allone. I have two plug S EU. One went smooth and on the secound i have the same issue. Tried already manual update and the old “non LR named Version” from archive here: Shelly_Wave_FW_OTA/Wave_Plug_S at main · QubinoHelp/Shelly_Wave_FW_OTA · GitHub

thany · December 24, 2025, 9:48am

The firmware entity is a bit confusing. It should either say “up-to-date” or display the version that it can update to. So your screenshot is correct in saying “Firmware: 11.4” - it just means there’s an update available to 11.4.