Firmware update fails - Inovelli Red Series Dimmer

Configuration Z-Wave
1

I just tried to use the zwave js firmware update feature, but it doesn’t seem to update the firmware on my Inovelli Red series dimmers. Here is the log:

2022-09-17T13:21:25.387Z CNTRLR » [Node 019] Sending firmware fragment 388 / 389
2022-09-17T13:21:25.470Z CNTRLR » [Node 019] Sending firmware fragment 389 / 389
2022-09-17T13:21:25.939Z CNTRLR « [Node 019] Firmware update completed with status OK_RestartPending
2022-09-17T13:21:25.942Z CNTRLR   [Node 019] Firmware updated, scheduling interview in 5 seconds...
2022-09-17T13:21:25.959Z CNTRLR   [Node 019] Downloading firmware update from https://files.inovelli.com/firmwar
                                  e/LZW31-SN/Beta/1.61/LZW31-SN_1.61.otz...
2022-09-17T13:21:26.739Z CNTRLR   [Node 019] Firmware update https://files.inovelli.com/firmware/LZW31-SN/Beta/1
                                  .61/LZW31-SN_1.61.otz downloaded, installing...
2022-09-17T13:21:27.841Z CNTRLR   [Node 019] Timed out while waiting for a response from the node (ZW0201)
2022-09-17T13:21:30.967Z CNTRLR   [Node 019] Beginning interview - last completed stage: None
2022-09-17T13:21:30.970Z CNTRLR   [Node 019] new node, doing a full interview...
2022-09-17T13:21:30.974Z CNTRLR » [Node 019] querying protocol info...
2022-09-17T13:21:31.043Z CNTRLR « [Node 019] received response for protocol info:
                                  basic device class:    Routing Slave
                                  generic device class:  Multilevel Switch
                                  specific device class: Multilevel Power Switch
                                  node type:             End Node
                                  is always listening:   true
                                  is frequent listening: false
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     100000 kbps
                                  protocol version:      3
2022-09-17T13:21:31.051Z CNTRLR   [Node 019] Interview stage completed: ProtocolInfo
2022-09-17T13:21:31.054Z CNTRLR » [Node 019] querying node info...
2022-09-17T13:21:31.144Z CNTRLR « [Node 019] node info received
                                  supported CCs:
                                  · Z-Wave Plus Info
                                  · Multilevel Switch
                                  · Configuration
                                  · Association
                                  · Association Group Information
                                  · Transport Service
                                  · Version
                                  · Manufacturer Specific
                                  · Device Reset Locally
                                  · Powerlevel
                                  · Security
                                  · Meter
                                  · Security 2
                                  · Central Scene
                                  · Supervision
                                  · Protection
                                  · Application Status
                                  · Firmware Update Meta Data
2022-09-17T13:21:31.153Z CNTRLR   [Node 019] Interview stage completed: NodeInfo
2022-09-17T13:21:31.160Z CNTRLR   [Node 019] Interviewing Manufacturer Specific...
2022-09-17T13:21:31.162Z CNTRLR » [Node 019] querying manufacturer information...
2022-09-17T13:21:31.243Z CNTRLR « [Node 019] received response for manufacturer information:
                                    manufacturer: Inovelli (0x031e)
                                    product type: 0x01
                                    product id:   0x01
2022-09-17T13:21:31.249Z CNTRLR   [Node 019] Interviewing Version...
2022-09-17T13:21:31.251Z CNTRLR » [Node 019]   querying the CC version for Version...
2022-09-17T13:21:31.335Z CNTRLR   [Node 019]   supports CC Version (0x86) in version 2
2022-09-17T13:21:31.337Z CNTRLR » [Node 019] querying node versions...
2022-09-17T13:21:31.415Z CNTRLR « [Node 019] received response for node versions:
                                    library type:      Enhanced Slave (0x03)
                                    protocol version:  6.4
                                    firmware versions: 1.52, 1.45
                                    hardware version:  1
1 Like
2

Open a bug report with node-zwave-js and attach the entire debug log file, before, during and after the upgrade.

3

Having the same issue. Following!

4

Created ticket here: Updating Inovelli Red Series Fails · Issue #5081 · zwave-js/node-zwave-js · GitHub

5

Hmm… HA 10.9.5 didn’t help. Still quits after 50%.
Now with the Zwave JS update (10.1.0), it’s no longer prompting the dimmer needs an update. And it’s still on the older firmware.

6
  1. The problem hasn’t been fixed yet.
  2. The firmware upgrade was moved to the beta channel, because it’s a beta firmware. Support to opt-in to beta release is not there yet.
1 Like
7

I am having the same problem, it started on 2022.9.0 and still an issue on 2022.10.1 (with JS Server: 1.24.0)

I have 7 dimmers that report new updates, but each time I try, it appears the dimmer begins the FW update process, but does not complete.

image
image938×856 46.1 KB

8

Same deal stops between 2-15%

9

Same here. And I have to restart the zwave-js add-on or I get this when I retry:

Z-Wave error 1500: Failed to start the update: A firmware upgrade is already in progress! (ZW1500)

Home Assistant 2022.10.4
Z-Wave JS: 0.1.74

Here is my full log:

2022-10-19T21:43:25.717Z CNTRLR » [Node 014] Sending firmware fragment 389 / 389
2022-10-19T21:43:26.191Z CNTRLR « [Node 014] Firmware update (part 1 / 2) succeeded with status OK_RestartPendin
                                  g
2022-10-19T21:43:26.192Z CNTRLR   [Node 014] Continuing with next part in 5 seconds...
2022-10-19T21:43:26.193Z CNTRLR   [Node 014] Updating firmware (part 2 / 2)...
2022-10-19T21:43:26.194Z CNTRLR » [Node 014] Starting firmware update...
Z-Wave error ZWaveError: Received no matching command within the provided timeout! (ZW0201)
    at Timeout.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4379:6)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 201,
  context: undefined,
  transactionSource: undefined
}
10

I have the same error. Even after factory reset. I just shared mine error log here too: Updating Inovelli Red Series Fails · Issue #5081 · zwave-js/node-zwave-js · GitHub

11

I got the notification that an update was available for my Inovelli Red switch (not dimmer). I did the update and it says my switch is a dead node?

I am not sure how to proceed. I don’t want to do something that will brick my switch.

2022-10-25T04:21:20.689Z CNTRLR   [Node 014] OTA firmware update started, downloading 1 updates...
2022-10-25T04:21:20.690Z CNTRLR   [Node 014] Downloading firmware update 0 of 1...
2022-10-25T04:21:21.219Z CNTRLR   [Node 014] All updates downloaded, installing...
2022-10-25T04:21:21.492Z CNTRLR   [Node 014] Updating firmware (part 1 / 1)...
2022-10-25T04:21:21.493Z CNTRLR » [Node 014] Starting firmware update...
2022-10-25T04:21:30.905Z CNTRLR   [Node 014] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-10-25T04:21:40.263Z CNTRLR   [Node 014] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-10-25T04:21:49.048Z CNTRLR   [Node 014] The node did not respond after 3 attempts, it is presumed dead
2022-10-25T04:21:49.050Z CNTRLR   [Node 014] The node is now dead.
Z-Wave error ZWaveError: Failed to send the command after 3 attempts (Status NoAck) (ZW0204)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3990:23)
    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4181:28)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4296:15)
    at Proxy.requestUpdate (/usr/src/node_modules/@zwave-js/cc/src/cc/FirmwareUpdateMetaDataCC.ts:147:23)
    at ZWaveNode.beginFirmwareUpdateInternal (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:4181:41)
    at ZWaveNode.updateFirmware (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:3992:15)
    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:218:27)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:105:62) {
  code: 204,
  context: SendDataRequestTransmitReport {
    host: [Driver],
    type: 0,
    functionType: 19,
    payload: <Buffer b9 01>,
    _callbackId: 185,
    transmitStatus: 1,
    txReport: undefined
  },
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3990:23)\n' +
    '    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4181:28)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4296:15)\n' +
    '    at Proxy.requestUpdate (/usr/src/node_modules/@zwave-js/cc/src/cc/FirmwareUpdateMetaDataCC.ts:147:23)\n' +
    '    at ZWaveNode.beginFirmwareUpdateInternal (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:4181:41)\n' +
    '    at ZWaveNode.updateFirmware (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:3992:15)\n' +
    '    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:218:27)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:105:62)'
}
12

Looks like a new Inovelli firmware is getting pushed out, but it’s failing like it did last year. Did anyone ever figure out a solution to this issue?

13

I’m getting an error installing the new Inovelli firmware 1.22 too.

[548263151424] Z-Wave error 1508: Failed to start the update: A firmware update is already in progress on this network! (ZW1508)