search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.94k stars 30.52k forks source link

Problem updating firmware for Inovelli LZW30-SN #82641

Closed mtehonica closed 1 year ago

mtehonica commented 1 year ago

The problem

I have an Inovelli LZW30-SN running firmware 1.9 and Home Assistant is showing an update to 1.20 available. When I attempt to upgrade, the logs show the node not respond and then goes into Dead status. Then I have to manually pull the air-gap switch and push it back in to get the device to reconnect. I've tried updating multiple times and same issue each time.

After the attempted update, the device status is:

ID: 17
Status: Dead
Ready: Yes
Highest security: S2 Authenticated
Z-Wave Plus: Version 1

If I try to update again after the air-gap reset and the device is reconnected, it tells me there is already an update in progress. The only way to stop this message is to restart my zwave-js-server container.

Starting logging event forwarder at silly level
2022-11-24T15:09:41.320Z CNTRLR   [Node 017] OTA firmware update started, downloading 1 updates...
2022-11-24T15:09:41.321Z CNTRLR   [Node 017] Downloading firmware update 0 of 1...
                                    URL:       https://files.inovelli.com/firmware/LZW30-SN/LZW30-SN_1.20.otz
                                    integrity: sha256:181fba03fae76da027627b45c47b1157999881c095e4ea13b919c1f630
                                  2ef724
2022-11-24T15:09:41.783Z CNTRLR   [Node 017] All updates downloaded, installing...
Z-Wave error ZWaveError: Failed to start the update: A firmware upgrade is already in progress! (ZW1500)
    at ZWaveNode.updateFirmware (/app/node_modules/zwave-js/src/lib/node/Node.ts:3883:10)
    at ZWaveController.firmwareUpdateOTA (/app/node_modules/zwave-js/src/lib/controller/Controller.ts:4706:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Function.handle (/app/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:218:27)
    at Client.receiveMessage (/app/node_modules/@zwave-js/server/dist/lib/server.js:105:62) {
  code: 1500,
  context: undefined,
  transactionSource: undefined
}

Running HA in Docker using image: ghcr.io/home-assistant/home-assistant:2022.11 Running zwave-js-server in Docker using image: kpine/zwave-js-server:1.24.1-10.3.1 using the zwave adapter usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller

zwave logs set to silly:

2022-11-24T14:54:11.115Z CNTRLR   [Node 017] OTA firmware update started, downloading 1 updates...
2022-11-24T14:54:11.116Z CNTRLR   [Node 017] Downloading firmware update 0 of 1...
                                    URL:       https://files.inovelli.com/firmware/LZW30-SN/LZW30-SN_1.20.otz
                                    integrity: sha256:181fba03fae76da027627b45c47b1157999881c095e4ea13b919c1f630
                                  2ef724
2022-11-24T14:54:11.460Z CNTRLR   [Node 017] All updates downloaded, installing...
2022-11-24T14:54:11.481Z SERIAL » 0x011a00a901110e9f034c005648052ee4a138c950fe25000000001b93          (28 bytes)
2022-11-24T14:54:11.481Z DRIVER » [Node 017] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      27
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 76
                                    └─[FirmwareUpdateMetaDataCCMetaDataGet]
2022-11-24T14:54:11.488Z SERIAL « [ACK]                                                                   (0x06)
2022-11-24T14:54:11.488Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-11-24T14:54:11.488Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:11.488Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-11-24T14:54:11.543Z SERIAL « 0x011d00a91b00000501be7f7f7f7f00000303000000030100007f7f7f7f7f97    (31 bytes)
2022-11-24T14:54:11.544Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:11.545Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            27
                                    transmit status:        OK, took 50 ms
                                    repeater node IDs:      3
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -66 dBm
                                    ACK RSSI on repeaters:  N/A
                                    ACK channel no.:        0
                                    TX channel no.:         0
2022-11-24T14:54:11.622Z SERIAL « 0x012100a8000111189f03ab00d5b98c2a86ac943c056cf1ca08d0120fe3f349430 (35 bytes)
                                  0be32
2022-11-24T14:54:11.626Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:11.628Z CNTRLR   [Node 017] [translateValueEvent: value updated]
                                    commandClass: Firmware Update Meta Data
                                    endpoint:     0
                                    property:     firmwareUpgradable
                                    propertyKey:  undefined
                                    internal:     true
                                    secret:       false
                                    event source: undefined
2022-11-24T14:54:11.629Z CNTRLR   [Node 017] [~] [Firmware Update Meta Data] firmwareUpg [Endpoint 0] [internal]
                                  radable: true => true
2022-11-24T14:54:11.630Z CNTRLR   [Node 017] [translateValueEvent: value updated]
                                    commandClass: Firmware Update Meta Data
                                    endpoint:     0
                                    property:     additionalFirmwareIDs
                                    propertyKey:  undefined
                                    internal:     true
                                    secret:       false
                                    event source: undefined
2022-11-24T14:54:11.631Z CNTRLR   [Node 017] [~] [Firmware Update Meta Data] additionalF [Endpoint 0] [internal]
                                  irmwareIDs:  =>
2022-11-24T14:54:11.632Z CNTRLR   [Node 017] [translateValueEvent: value updated]
                                    commandClass: Firmware Update Meta Data
                                    endpoint:     0
                                    property:     continuesToFunction
                                    propertyKey:  undefined
                                    internal:     true
                                    secret:       false
                                    event source: undefined
2022-11-24T14:54:11.632Z CNTRLR   [Node 017] [~] [Firmware Update Meta Data] continuesTo [Endpoint 0] [internal]
                                  Function: "unknown" => "unknown"
2022-11-24T14:54:11.633Z CNTRLR   [Node 017] [translateValueEvent: value updated]
                                    commandClass: Firmware Update Meta Data
                                    endpoint:     0
                                    property:     supportsActivation
                                    propertyKey:  undefined
                                    internal:     true
                                    secret:       false
                                    event source: undefined
2022-11-24T14:54:11.634Z CNTRLR   [Node 017] [~] [Firmware Update Meta Data] supportsAct [Endpoint 0] [internal]
                                  ivation: "unknown" => "unknown"
2022-11-24T14:54:11.635Z DRIVER « [Node 017] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -66 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 171
                                    └─[FirmwareUpdateMetaDataCCMetaDataReport]
                                        manufacturer id:         798
                                        firmware id:             513
                                        checksum:                63878
                                        firmware upgradable:     true
                                        max fragment size:       28
                                        additional firmware IDs: []
                                        hardware version:        undefined
                                        continues to function:   unknown
                                        supports activation:     unknown
2022-11-24T14:54:11.640Z CNTRLR   [Node 017] Updating firmware (part 1 / 1)...
2022-11-24T14:54:11.641Z CNTRLR » [Node 017] Starting firmware update...
2022-11-24T14:54:11.675Z SERIAL » 0x012400a90111189f034d0029bea6c39ef81ba813cef672354a04d318deeafa250 (38 bytes)
                                  00000001c92
2022-11-24T14:54:11.676Z DRIVER » [Node 017] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      28
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 77
                                    └─[FirmwareUpdateMetaDataCCRequestGet]
                                        manufacturer id: 0x031e
                                        firmware id:     0x0201
                                        checksum:        0x3e58
                                        firmware target: 0
                                        fragment size:   28
                                        activation:      false
2022-11-24T14:54:11.683Z SERIAL « [ACK]                                                                   (0x06)
2022-11-24T14:54:11.683Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-11-24T14:54:11.684Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:11.684Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-11-24T14:54:19.504Z SERIAL « 0x011d00a91c0102ff007f7f7f7f7f0101070000000002190e110000000000d7    (31 bytes)
2022-11-24T14:54:19.506Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:19.507Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            28
                                    transmit status:        NoAck, took 7670 ms
                                    routing attempts:       25
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    TX channel no.:         1
                                    route failed here:      14 -> 17
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2022-11-24T14:54:19.518Z CNTRLR   [Node 017] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-11-24T14:54:20.019Z SERIAL » 0x012400a90111189f034d0088ab96b36b498935305dcd1ecb0a7243b1c3590c250 (38 bytes)
                                  00000001c63
2022-11-24T14:54:20.020Z DRIVER » [Node 017] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      28
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 77
                                    └─[FirmwareUpdateMetaDataCCRequestGet]
                                        manufacturer id: 0x031e
                                        firmware id:     0x0201
                                        checksum:        0x3e58
                                        firmware target: 0
                                        fragment size:   28
                                        activation:      false
2022-11-24T14:54:20.026Z SERIAL « [ACK]                                                                   (0x06)
2022-11-24T14:54:20.032Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-11-24T14:54:20.032Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:20.032Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-11-24T14:54:27.111Z SERIAL « 0x011d00a91c0102b7007f7f7f7f7f0001070000000002120e11000000000095    (31 bytes)
2022-11-24T14:54:27.112Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:27.112Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            28
                                    transmit status:        NoAck, took 6950 ms
                                    routing attempts:       18
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    TX channel no.:         1
                                    route failed here:      14 -> 17
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2022-11-24T14:54:27.115Z CNTRLR   [Node 017] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-11-24T14:54:27.620Z SERIAL » 0x012400a90111189f034d00844b1bff049fb7885797be01eb01fcecdd41fef0250 (38 bytes)
                                  00000001c0a
2022-11-24T14:54:27.621Z DRIVER » [Node 017] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      28
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 77
                                    └─[FirmwareUpdateMetaDataCCRequestGet]
                                        manufacturer id: 0x031e
                                        firmware id:     0x0201
                                        checksum:        0x3e58
                                        firmware target: 0
                                        fragment size:   28
                                        activation:      false
2022-11-24T14:54:27.627Z SERIAL « [ACK]                                                                   (0x06)
2022-11-24T14:54:27.633Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-11-24T14:54:27.634Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:27.635Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-11-24T14:54:34.778Z SERIAL « 0x011d00a91c0102bd007f7f7f7f7f0001070000000002120e1100000000009f    (31 bytes)
2022-11-24T14:54:34.779Z SERIAL » [ACK]                                                                   (0x06)
2022-11-24T14:54:34.780Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            28
                                    transmit status:        NoAck, took 7010 ms
                                    routing attempts:       18
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    TX channel no.:         1
                                    route failed here:      14 -> 17
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2022-11-24T14:54:34.786Z CNTRLR   [Node 017] The node did not respond after 3 attempts, it is presumed dead
2022-11-24T14:54:34.787Z CNTRLR   [Node 017] The node is now dead.
Z-Wave error ZWaveError: Failed to send the command after 3 attempts (Status NoAck) (ZW0204)
    at Driver.sendMessage (/app/node_modules/zwave-js/src/lib/driver/Driver.ts:3990:23)
    at Driver.sendCommandInternal (/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4181:28)
    at Driver.sendCommand (/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4296:15)
    at Proxy.requestUpdate (/app/node_modules/@zwave-js/cc/src/cc/FirmwareUpdateMetaDataCC.ts:147:23)
    at ZWaveNode.beginFirmwareUpdateInternal (/app/node_modules/zwave-js/src/lib/node/Node.ts:4181:41)
    at ZWaveNode.updateFirmware (/app/node_modules/zwave-js/src/lib/node/Node.ts:3992:15)
    at Function.handle (/app/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:218:27)
    at Client.receiveMessage (/app/node_modules/@zwave-js/server/dist/lib/server.js:105:62) {
  code: 204,
  context: SendDataBridgeRequestTransmitReport {
    host: [Driver],
    type: 0,
    functionType: 169,
    payload: <Buffer 1c 01 02 bd 00 7f 7f 7f 7f 7f 00 01 07 00 00 00 00 02 12 0e 11 00 00 00 00 00>,
    _callbackId: 28,
    transmitStatus: 1,
    txReport: {
      txTicks: 701,
      numRepeaters: 0,
      txChannelNo: 1,
      routeSchemeState: 7,
      repeaterNodeIds: [],
      beam1000ms: false,
      beam250ms: false,
      routeSpeed: 2,
      routingAttempts: 18,
      failedRouteLastFunctionalNodeId: 14,
      failedRouteFirstNonFunctionalNodeId: 17,
      txPower: 0,
      measuredNoiseFloor: 0
    }
  },
  transactionSource: '    at Driver.sendMessage (/app/node_modules/zwave-js/src/lib/driver/Driver.ts:3990:23)\n' +
    '    at Driver.sendCommandInternal (/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4181:28)\n' +
    '    at Driver.sendCommand (/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4296:15)\n' +
    '    at Proxy.requestUpdate (/app/node_modules/@zwave-js/cc/src/cc/FirmwareUpdateMetaDataCC.ts:147:23)\n' +
    '    at ZWaveNode.beginFirmwareUpdateInternal (/app/node_modules/zwave-js/src/lib/node/Node.ts:4181:41)\n' +
    '    at ZWaveNode.updateFirmware (/app/node_modules/zwave-js/src/lib/node/Node.ts:3992:15)\n' +
    '    at Function.handle (/app/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:218:27)\n' +
    '    at Client.receiveMessage (/app/node_modules/@zwave-js/server/dist/lib/server.js:105:62)'
}

What version of Home Assistant Core has the issue?

2022.11.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

zwave

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)

zwave_js documentation zwave_js source (message by IssueLinks)