#Thats fine by me if it works it works if
1 messages ยท Page 1 of 1 (latest)
it's pretty hidden here:
https://github.com/zwave-js/node-zwave-js/discussions/2544#discussioncomment-4894779
That user posted a ...-nolimit.gbl.zip file containing a custom bootloader, which removes the downgrade check. You can just flash the contained gbl like any firmware, then after the stick restarts flash the firmware.
Before you do that though, you should make an NVM backup, and restore it after the downgrade.
The stick's firmware doesn't handle downgrades, but Z-Wave JS can.
I used it to get off the _v255 version I accidentally used and couldn't up or downgrade off.
Oh wow thats pretty cool! And this 'nolimit' patch will work with any Z-stick 7? I see UZB7 mentioned, but i have the Aeotec Z-stick 7 (ZST10-700
by Silicon Labs) (Model Number: ZWA010)
My eyes started working! I understand it will work for my device. Going to try in 2 minutes ๐
I did it on my Z-Stick 7
After flashing the nolimit, i should be able to flash my firmware of choice using ZWJS UI? Im getting Driver: Failed to recover from bootloader. Please flash a new firmware to continue... (ZW0100) and if i click the FW OTW button anyways, i get Error reading file
Logs keep spamming this though, so we're half way i guess ๐
2023-03-06T21:40:07.535Z DRIVER version 10.10.0 2023-03-06T21:40:07.535Z DRIVER 2023-03-06T21:40:08.574Z DRIVER Controller is in bootloader, attempting to recover... 2023-03-06T21:40:09.578Z DRIVER Failed to recover from bootloader. Please flash a new firmware to continue...
Do i have to use the Aeotec/Silab vendors windows software to flash it?
The first part is expected. The error reading file isn't. Is that error from zwave-js-ui?
Correct, from Zwave-js-ui
You could try the standalone utility
https://github.com/zwave-js/node-zwave-js/blob/master/packages/flash/README.md
After saying "please flash new firmware" it restarts and prints it all again, looping
Needs a somewhat recent version of node.js installed
Ah, linux. Is there any way of doing this via the silabs windows tools i already have installed? I see i have a bin called Commander that i think is for flashing everything and anything
Can you open an issue about that? Seems like a bug in zwave-js ui
Hmm never used the commander thing. WSL is not an option?
Unfortunately I haven't figured out yet why windows is no longer working properly
Alright, youre talking about the tool you linked right?
Ah shit, I think WSL only supports USB on windows 11
Cause the windows silabs tools arent working either, but i thought that was because of the nolimit flash
Oooh i missed a message, my bad. I don't know what WSL is
Windows subsystem for Linux
Ah true! I can set that up ๐
Basically Linux on windows
Not sure if you have access to USB there, at least it didn't work on windows 10
11 fixed that I think
I'll test my luck, I'm on 11!
I have a linux VM in VMware actually, maybe its easier to passthrough there
And yes ill open an issue for it, maybe tomorrow, i wanna fiddle more with the stick rn haha
/dev/sr0 could this be the USB?
Ah.. sorry. Does this tool flash with direct OTW, or is it a tool to flash the FW to whatever client is connected to ZWJS?
`npx @zwave-js/flash@latest 1-2 ~/protocol/z-wave/Apps/bin/gbl/zwave_ncp_serial_api_controller_BRD4206A.gbl --verbose
/home/ubuntuuser/.npm/_npx/7690b5c31200d08c/node_modules/@zwave-js/shared/build/inheritance.js:19
if (base?.prototype) {
^
SyntaxError: Unexpected token '.'
at wrapSafe (internal/modules/cjs/loader.js:915:16)
at Module._compile (internal/modules/cjs/loader.js:963:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.<anonymous> (/home/ubuntuuser/.npm/_npx/7690b5c31200d08c/node_modules/@zwave-js/shared/build/index_safe.js:20:14)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)`
Im confused
seems you're using an old version of nodejs. I'd use 16 or later.
Aaah ~$ node -v v12.22.9
way too old
Weird, well, I'm clueless. But i installed it with a very generic command that looked like it'd give me the latest..
Lmao my version is from the 90s then
Are you using the Docker version of ZUI?
"npm upgrade" is wrong?
`npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@esm2cjs/responselike@3.0.0',
npm WARN EBADENGINE required: { node: '>=14.16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
up to date, audited 157 packages in 10s
48 packages are looking for funding
run npm fund for details`
I'm on WSL rn, ubuntu install
Yes it's wrong
Ubuntu doesn't ship new versions.
Install it manually
How do you usually run ZUI?
Unraid -> VM: HASS -> Addon: ZUI
Zstick 7 passthrough to the VM. Right now the stick is in my workstation box
Oh wow, and in the ubuntu npm/nodejs you get v12.. Weird to me, but i know nothing.
I'll see if i figure out how to install the updated version manually as you described, just for the sake of learning. If i cant do it in 5-10 minutes ill plug the stick back into the unraid box
Thanks ๐
Oh, what distro and such do you use?
I think you can just extract the official tarballs into /usr/local/
Debian + nix
or Docker
Ooh i see
community ssh add-on allows you turn on protected mode to access USB devices, you can install nodejs there and do the same
Sounds like a plan.. Ran into another wall
Errors were encountered while processing: /var/cache/apt/archives/nodejs_19.7.0-deb-1nodesource1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
In the ssh add-on, i ssh into ZUI or can it be done inside the ssh install?
You use the ssh terminal. You would have to shutdown ZUI first.
It's Alpine Linux, so apk add nodejs will get you started.
Alright i replaced the ssh addon i had with that one, looks better.
Thanks! Ill see what i figure out
If the USB device isn't visible (I don't think it will be), you'll need to disable protected mode, or whatever it's called, in the add-on settings.
Thank you both so much, the time youve spent helping me is very very much apprechiated!
We made it!! The stick is now on FW 1.17.2, and operating.
I will open an issue tomorrow, or perhaps just chime in on another issue from January that i saw. I don't have the link up right now, but he had pretty much the exact issue that I just had. Except maybe the "error reading file" message was "unique" for me.
And what worked for me was installing nodejs, npm, zwave-js(?) in hassio terminal, then using @zwave-js/flash@latest to flash the gbl firmware
Separately installing zwave-js isn't necessary. The flash utility has it as a dependency which means it automatically gets installed when you execute it with npx
I'm just confused, I didn't install it like i made it sound like - but it installed the dependencies as you described
You listed "zwave-js(?)" as something you installed.
You're both right, i worded it poorly. I did not install zwave-js myself but the flash command installed the dependencies it needed
The "error reading file" issue i had, i make that at zwave-js-ui right?
Are you using HomeAssistant? If yes, please open your issue at https://github.com/home-assistant/core/issues UNLESS a developer told you to come here.