Yeah, wrote Z2M… bad habit, Z-Wave JS UI ver. 1.10
Was wondering if flipping the bootloader switch was an option also.
You would use the bootloader option if the driver is stuck in a loop trying to start. Should be evident in the logs (as mentioned).
Yes it should work if you are stuck in bootloader mode but you need to update your zwavejs ui add-on to v1.10.1. That version brings zwave-js/zwave-js-ui to v8.13.1 which has the fix robertsLando did two weeks ago for OTW upload failing in bootloader only mode.
Based on your updated note that you had the failed OTW in zwavejs UI it sounds like you ran into the same issue I did trying to update one of my ZST10-700 sticks last month. The above solved it for me (I just had to do the bootloader only OTW on a separate RPi running the latest docker image because it wasn’t merged into hass add-on yet).
If you see something like this in your logs then you are stuck in bootloader mode and will need to enable bootloader only option to retry OTW:
14:58:17.508 SERIAL « Gecko Bootloader v1.12.01
1. upload gbl
2. run
3. ebl info
BL >
14:58:17.511 CNTRLR [BOOTLOADER] version 1.12.01
This is what is happened just now when trying to an update
2023-04-11T16:19:28.078Z CNTRLR Performing soft reset...
2023-04-11T16:19:28.090Z CNTRLR Waiting for the controller to reconnect...
2023-04-11T16:19:29.323Z CNTRLR reconnected and restarted
2023-04-11T16:19:29.340Z CNTRLR Entered bootloader
2023-04-11T16:19:29.341Z CNTRLR Beginning firmware upload
2023-04-11T16:19:29.389Z CNTRLR OTW update was aborted by the bootloader. file error 0x50
2023-04-11 12:19:29.392 INFO Z-WAVE: Controller 1 firmware update OTW finished with error.
Status: Error_Aborted. Result: [object Object].
2023-04-11T16:19:29.395Z CNTRLR Leaving bootloader...```I would contact Zooz about that. That error is a known issue, but supposed to be fixed in some version of 7.18.
Yeah Zooz would be my next step as well. Their stick is still 7.17.x so that could certainly be the issue.
For what it’s worth, these sticks pretty cheap so if ZWave being down is detrimental to your smart home functioning, I recommend just having a backup on hand and enabling regular NVM backups. For $20-30 it worth it to me having saved me from my ZWave network being down for days or weeks a few times.
I was already on this version, so this is my confusion after seeing the suggestions you and @freshcoast having been giving so far.
I think I’m gonna leave well enough alone for the moment and order another stick real quick…Hell maybe just get the 800 and call it a day an excuse to spend a $100 or more at Smartest House for free shipping.
Thanks for both of your help so far…appreciate it
You said you were on 1.10. 1.10.1 came out six hours ago, so unless you updated this morning you are not on the latest version which contains the OTW fix for bootloader only mode.
The fix you are referring does not solve the device returning a 0x50 error.
That fix was also added to 8.12.0, which is add-on version v1.9.0.
Yeah, the update hit early this morning I went from 1.10 to 1.10.1 after my original post…damn I’m failing on the typing today! I do appreciate your time and help to this point…Thanks!
Haven’t needed anything from Zooz in awhile, so maybe time to update my ZEN30s (500 series) to some ZEN32 (700 series) also.
Ah gotcha. And yeah as the other person noted, if you are getting the 0x50 error, that’s likely something else.
As for replacing your 500 series with 700: I didn’t have Zooz 500 switches (I switched from GE 500 series) but personally I don’t know how much benefit you’ll see out of upgrading 500 > 700 if they work fine now. If anything, personally I’d wait til 800 series switches start coming out before doing a bunch of rip and replace. Just my 2c.
Wife had asked me about the ZEN32, think she likes the idea of the 4 buttons. I only have 3 and the rest of them are ZEN77, so I’ll let her decide what she wants.
0x50 Error yeah that happened, so not sure if I should just go ahead and grab the 800 series stick… have to look into it more.
Yeah if you have a use for them, the extra buttons are nice. I had a few but ended up taking them back out and just using more ZEN77 instead. I didn’t really have a great use for the extra buttons in the end and partner likes the hold to dim up/down functionality anyways. Also sometimes the buttons would stick in my ZEN32s which was mildly annoying. I originally had planned to leverage the extra buttons and multi-color LEDs on them for things like controlling and showing status of alarm system, light automations, etc. but never found a great way to implement that. Plus having low reach light switches and a toddler made me abandon that idea altogether. Now I just use ZEN77/ZEN76 nearly everywhere and heavily rely on scene control and smart switch mode for controlling Hue bulbs (and for an easy way to temporarily disable switches in a room to combat the terrorist toddler fingers lol). There’s a nice blueprint that let’s me do quite a bit of advanced extra actions from 2x/3x/4x/5x presses.
Yep, my whole house is Hue and love all my ZEN77 switches.
The wife thinks the 4 buttons would be better for fan speed controls… I somewhat agree.
We have wall tablets, so don’t use switches much or often at all with all the automations going on anyway, but she likes poking at them sometimes…I guess.
Back on topic, think I’m going to give the ZST39 800 a whirl if I’m going to order some stuff.
I have Home Assistant running on a raspberry pi, with Z-Wave JS installed. The HA GUI offers and “update” button. How risky is it? For example, will it automatically detect my ZST10-700 is not US?
(I have the latest version of HA and the stick is still running 7.16.0)
I saw it’s officially recommended by Zooz themselves since HA 2023.3.0, hence I went ahead with the EU firmware file I had downloaded myself.
Worked like a charm, really cool not having to plug that into a Windows PC (which I don’t have), etc.
Anyone with ZST10-700 on firmware v7.18.3? Do you see any reliability improvements versus v7.17.x?
I have read this https://www.silabs.com/documents/public/release-notes/SRN14889-7.18.3.0.pdf but it’s hard to decipher.
P.S. My ZST10-700 is currently on v7.17.2 and some zwave devices goes offline once in awhile. I would love a firmware update that improves this situation.
I’ve been running x.18.3 for a few months now.
I still get the occasional dead node…
1 Like
A noob question: when we say “get dead nodes”, what exactly do we see, or how exactly do we find out when a dead node happens?
Would Z-Wave JS UI somehow show you: “you have a dead node here”, or you would not notice until something is off?
- If you have a “dead node”, your activation (automation, command… etc.) will fail.
- You’ll raise an error in the logs.
- In JS-UI you will see a red ‘frowny face’.
Unless something is truly wrong with the node, sending a ‘ping’ brings the node back to life in HA. In my case it’s extremely rare that the node is actually down.
It’s always perplexed me why HA doesn’t handle this situation very well.
1 Like