-
-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File upload for OTW update fails on all files #3023
Comments
Just wanted to add, I tried updating several other sticks I have today (including another ZST10-700) and both updated successfully. One of the USB sticks gave the same timeout error message (screenshot below) like I got when I first attempted to update my other ZST10-700 (the update attempt that got it stuck in bootloader mode) but it did still update and came back like normal showing the new version. But attempting to apply OTW while in "Bootloader Only" mode still fails the same as above on every file that I try and upload. I've emailed Zooz to see if there is any other way to reflash this stick stuck in bootloader mode but it appears uploading OTW specifically when zwave-js is in "Bootloader Only" mode is specifically what causes this error. |
@RyanWor Ok I found wher the problem is, this happens only on bootloader only mode because before sending the request I set the loading state on controller node but controller node doesn't exists in bootloader only... Let me prepare a quick fix for this... |
@RyanWor Fix is on master, if you are using docker you can use |
@robertsLando Spun up master docker container on a test Pi and attempted the OTW. It gets further now but is still failing elsewhere. I wonder if my stick is broken. I spoke with Zooz yesterday and they suggested I send it in for RMA replacement. Happy to hold off on that if testing further would help here though. For what it's worth, I updated another ZST10-700 with this same gbl file and it worked so I know it's not a bad gbl file. Here is the logs from my attempt to OTW in bootloader only mode:
|
@RyanWor Nope still an issue on my side, apis checks the driver to be ready before calling, in this case driver is not ready so it immediatly rejects, just submitted a fix for this wait some minutes until the new image is built and then pull again and let me know |
@robertsLando pulled master and tested again, got a "Driver is not ready" error this time versus "Z-Wave client not connected" last time. Log:
|
@RyanWor LOL there was a check also on that function, sorry. Pushed another fix to master now, hope this time it's the good one 😅 |
@robertsLando winner winner chicken dinner! That did the trick. 7.18.3 installed, no longer stuck in bootloader, and even still had all my nodes in the NVM. Great work man and again thank you so much for all you do! |
Thanks for the feedback @RyanWor, glad it works now 🙏🏼 |
Checklist
Deploy method
Docker
Z-Wave JS UI version
8.11.0
ZwaveJS version
10.12.0
Describe the bug
When attempting to apply OTW update to ZST10-700 (currently in bootloader mode due to the update failure in first attempt) UI reports "Error reading file" (screenshot below) for any files.
To Reproduce
Enable "Bootloader only" in Settings > ZWave
Save settings
Wait for status to report "Bootloader is READY"
Click "Firmware Upgrade OTW" from "Advanced Actions"
Select .gbl firmware file to be flashed to USB stick
Click "Update"
"Error reading file" displayed in red popup in top right of window
(See attached screen recording)
chrome_koYUQQIdVX.mp4
Expected behavior
ZWave-JS applies firmware update to the USB stick
Additional context
I have tested this with multiple firmware files freshly downloaded and extracted from Zooz website including 7.18.3 and 7.18.1 (example files attached in zips, GitHub will not allow upload of .gbl files).
The error message appears instantly after clicking update.
No debug messages shown in log. It does not appear zwave-js backend is even attempting the firmware update.
I have tested this one three different HAOS hosts running different hardware, all produce the same error.
ZST10_700_7_18_1_US.zip
ZST10_700_7_18_3_US.zip
The text was updated successfully, but these errors were encountered: