OTA Update Error

demockery · February 2, 2023, 12:46am

Whenever i click the OTA update menu on any device - a red error modal pops up with the following error message:

Error while calling api getAvailableFirmwareUpdates: Cannot check for firmware updates for node 13: Cannot read properties of undefined (reading 'includes') (ZW0261)

Is this normal? Did I miss some instruction on properly configuring this?

The status of every device reports “No updates available”

freshcoast · February 2, 2023, 12:54am

github.com/zwave-js/zwave-js-ui

Migrated from Z-Stick 7 to Z-stick 5 (non +) - Issues with checking firmware

opened 06:11PM - 01 Feb 23 UTC

Hooverjc

question

I finally had enough with dealing with all the dead nodes and performance issues… related to my z-stick 7 and performed an NVM backup and restore to a Z-stick 5. All is working much better now, but I've noted in the logs that i'm getting an error on most of my devices at boot and if I manually try to check for firmware updates. When I manually check for an update, I see this error in the UI and log: 2023-02-01 10:06:51.505 INFO Z-WAVE: Cannot check for firmware updates for node 58: Cannot read properties of undefined (reading 'includes') (ZW0261) getAvailableFirmwareUpdates undefined when I reboot, I see the following error for every node: 2023-02-01 10:09:06.359 ERROR Z-WAVE-SERVER: Cannot check for firmware updates for node 24: Cannot read properties of undefined (reading 'includes') (ZW0261) ZWaveError: Cannot check for firmware updates for node 24: Cannot read properties of undefined (reading 'includes') (ZW0261) at ZWaveController.getAvailableFirmwareUpdates (/usr/src/app/node_modules/zwave-js/src/lib/controller/Controller.ts:5234:10) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Function.handle (/usr/src/app/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:205:30) at Client.receiveMessage (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:106:62) I've attempted to re-interview the nodes, refresh values, heal them, update topics, but none of these appear to resolve this issue. Is this expected behavior on a 500 series device (maybe unhandled due to my swap) or is there an issue going on here? I can only find one reference to this error online, so trying to get some more information on what else may be wrong. Also, for clarity, running the latest release: zwave-js-ui: 8.8.3.649eb88 zwave-js: 10.5.5 Z-stick Gen 5 is running FW 1.2 with SDK 6.81.6 Thanks!

eljefesote · February 2, 2023, 3:18am

I have the same error. I cannot manually update firmware either. Maybe related. Haven’t found any solutions.

freshcoast · February 2, 2023, 3:42am

The error message reported here and in the GitHub issue only arise from using the OTA service, they wouldn’t be involved in manual updates. If you have some other problem related to manual updates, you might want to provide more detail.

ElectroStaticD · February 2, 2023, 2:14pm

I’m getting the same error.

demockery · February 3, 2023, 2:08am

appears to be an upstream bug. They just reverted how they were handling cach’ing

Wolfgeek · February 8, 2023, 4:09am

Any solution for this yet?

demockery · February 11, 2023, 10:33pm

looks like the latest docker image has the fix.