Controller reporting "Jammed" and then "Ready", operations hang #6512
Replies: 18 comments 98 replies
-
|
Every time the controller is unable to transmit (jammed), a few seconds earlier several of your power meters (46, 50, 58) are reporting the same power usage repeatedly. I'm relatively certain that this flurry of commands causes the problem. You may want to give https://zwave-js.github.io/node-zwave-js/#/troubleshooting/network-health?id=optimizing-the-reporting-configuration a read. |
Beta Was this translation helpful? Give feedback.
-
|
Not fixed in 7.21.1 either: |
Beta Was this translation helpful? Give feedback.
-
|
@AlCalzone : was checking the exact same stuff when I saw the new version :D |
Beta Was this translation helpful? Give feedback.
-
|
We have been waiting for a solution to this for a long time and are slowly finding it unreasonable for us and our customers. Can you please let us know if this issue is still being worked on and when a fix can be expected? |
Beta Was this translation helpful? Give feedback.
-
|
@homeeBerlin You'll have to ask Silicon Labs, who build the controller firmware for the Z-Wave hardware. That is the part that's not working correctly. |
Beta Was this translation helpful? Give feedback.
-
|
Can someone, ANYONE, point to anything public from SILabs that directly correlates a known issue with the SDK or the hardware to this specific issue? While the posted screen grabs -may- be a direct relation, I'd love to see a published piece of information from SILabs that directly states how this issue may manifest itself, and WHY it seems that HA users are the ones experiencing the issue while other systems do not appear to have the same experience. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Well, by the looks of it, it seems to have triggered some reaction, that post of mine on the Silabs forum. Speaking of ......... I see a new release of the Gecko SDK with version 7.20.3, and as far as I can see, I don't see the issue mentioned anymore in the release notes ... But yeah, @ember1205, let's just continue ranting about in hope someone will fix stuff ... thanks captain optimism ;) In the meanwhile, I'll get back in touch with Aeotec to see if they can produce a new firmware version based on 7.20.3 so that I can test correctly :) |
Beta Was this translation helpful? Give feedback.
-
|
I'm practical and logical. I have yet to see anything specific directly from SILabs taking ownership of the issue or even acknowledging that there MAY be an issue. Sorry that doesn't exude "optimism", but I've spent far too many years watching companies simply NOT fix issues to blindly hope for a fix. |
Beta Was this translation helpful? Give feedback.
-
|
They did already via the information communicated on the previous release notes, issue #1227385 as AlCalzone had already reported. Speaking to Aeotec, they confirmed that information, they saw 7.20.2 affected and even proposed me to test 7.21.x but the issue from their tests was not fixed yet in those versions either. You stated previously that only HA users were affected, that is false, as I'm using Zwave-JS-UI combined to Jeedom as a platform and encounter the same issues. Thanks to the informations provided by several people to Aeotec and Silabs, we may now have a fix, that is yet to be confirmed though. So, yeah, what more is expected exactly ? A communiqué where Silabs apologizes to the whole planet ? Come on ... I've worked way too long in this industry to know that this helps in no way. Chill down mate ... |
Beta Was this translation helpful? Give feedback.
-
|
Glad you got it all figured out... |
Beta Was this translation helpful? Give feedback.
-
|
We wouldn't expect an apology either, but at least some kind of communication that the problem is being worked on or is no longer being worked on. Because we have customers who have major problems with these versions and we also have to comment on them and some also return the product and we have to reimburse them, so we definitely don't see it as relaxed. |
Beta Was this translation helpful? Give feedback.
-
|
posted this morning on their forum |
Beta Was this translation helpful? Give feedback.
-
|
Jeez I hope so. My entire network has been essentially dead in the water since September I think. |
Beta Was this translation helpful? Give feedback.
-
|
Same here. I think silicon labs wants to kill the zwave protocol... |
Beta Was this translation helpful? Give feedback.
-
|
Is there any news yet? We are almost at the last of April and haven't found a new FW yet. |
Beta Was this translation helpful? Give feedback.
-
|
My zooz turn very well in EU |
Beta Was this translation helpful? Give feedback.
-
|
Do you have a 700 stick? |
Beta Was this translation helpful? Give feedback.
-
|
Yes |
Beta Was this translation helpful? Give feedback.
-
|
Hmm interesting. Maybe I should look at that one. Although I see the 800 is also for sale in the EU now. |
Beta Was this translation helpful? Give feedback.
-
|
Even if a different stick works, IMO there's really no point in buying 700 series over 800 right now - except the price maybe. |
Beta Was this translation helpful? Give feedback.
-
I bought 800 Zooz (ZST39 LR : before I had an Aeotec 700 and an Aeotec 500 before that) from UK with NA Region and RF, then contacted Zooz to get the correct procedure to convert to EU RF. By the way : to me seems that when jammed, physically unplug the stick help to stay away from the jammed issue for a more time compared to simple turn off zwavejs and turn on again. |
Beta Was this translation helpful? Give feedback.
-
|
Arf yes not a good idea in this case. Tell us what happen and if you can transfert you backup from 700 to 800 |
Beta Was this translation helpful? Give feedback.
-
|
It will be the next challenge. Aeotec to aetoc I have already do this many of times. But aeotec to zooz, it's my first time. |
Beta Was this translation helpful? Give feedback.
-
|
I just got another "controller is busy". After 2 days... Since I don't yet have the zooz 800 key, I directly connected my AEOTEC 700 without a USB extension. We'll see. I also ordered a quality 5Gbps extender to see if that changes anything. |
Beta Was this translation helpful? Give feedback.
-
|
This is a software/firmware issue, not a hardware issue. I doubt throwing money at the problem will help, until Silicon Labs finally fix the firmware. |
Beta Was this translation helpful? Give feedback.
-
|
I tried without the USB extension. It works only 24 hours... |
Beta Was this translation helpful? Give feedback.
-
|
Completely agree ....
And silicon labs isn't responding on this.
They are promising to fix on the next release.... always.... always 'the
next'.
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Dom 5 Mag 2024, 12:48 AlCalzone ***@***.***> ha scritto:
… This is a software/firmware issue, not a hardware issue. I doubt throwing
money at the problem will help, until Silicon Labs finally fix the firmware.
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROKT5R5JJGJ5TPNWWD3ZAYFBBAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGMJZGI2DK>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
my controller is jamming 5-10 times a day, my network is basically unusable. I'm using the Zooz 800LR USB stick. |
Beta Was this translation helpful? Give feedback.
-
|
The release notes for the latest SDK (7.21.3) mention a possible workaround:
@AlCalzone I only kind of understand the workaround. Is that something that would be reasonable for ZWaveJS to implement, something ZWaveJS is already doing, or something unreasonable/impossible for you to do? |
Beta Was this translation helpful? Give feedback.
-
Did they give any indication of how long they need to roll the firmware into their version? |
Beta Was this translation helpful? Give feedback.
-
Correct, this would only be for the ZST39, not their 700 series stick. I have no clue what Silabs' plan is to address those devices. |
Beta Was this translation helpful? Give feedback.
-
Likely next week |
Beta Was this translation helpful? Give feedback.
-
|
AFAIK even 7.22.x will be only a partial fix though |
Beta Was this translation helpful? Give feedback.
-
|
Seems we've blown past that timeline. Any new updates that you know of? I haven't seen anything on SI forums and talking to Zooz they didn't give me any new dates. |
Beta Was this translation helpful? Give feedback.
-
|
It appears Zooz has released firmware 1.30 for the ZST39 which is based on 7.21.3 SDK: |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
Yes |
Beta Was this translation helpful? Give feedback.
-
|
This morning my controller became jammed again. I am also on firmware 7.17.2. Zwave-js is 12.11.0. Should the workaround suppress the jammed status events when it is working? Or should the firmware be 7.21.3? It wasn't clear to me if the 7.21.3 SDK added something that is needed for the workaround or if it is applicable to other versions as well. |
Beta Was this translation helpful? Give feedback.
-
No, you'll still have short intervals where the controller status is jammed. But it should be recovered quickly with the workaround. I don't recommend 7.21.3 right now due to the issue with the complete lockups some users are experiencing. |
Beta Was this translation helpful? Give feedback.
-
|
i am now getting jamming again but the last one was for 5 seconds 9 hours ago |
Beta Was this translation helpful? Give feedback.
-
|
Sounds like this workaround does its job then:
https://github.com/zwave-js/node-zwave-js/releases/tag/v12.10.1
Does this mean we should upgrade to 7.21.3 ?
|
Beta Was this translation helpful? Give feedback.
-
|
No. The workaround only helps with the controller being unable to transmit. 7.21.3 makes the controller completely unresponsive for several users, which can only be solved by unplugging and re-plugging it. |
Beta Was this translation helpful? Give feedback.
-
|
Who will be the Guinea Pig this time ?
Crippa Andrea
Il giorno sab 22 giu 2024 alle ore 22:50 Niccolò Belli <
***@***.***> ha scritto:
… AFAIK even 7.22.x will be only a partial fix though
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROKZMCSHH6OWKXTAHFLZIXPQVAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQNBYHA4TQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I just learned about this issue. I had a small ZwaveJS network, maybe 5 devices, which seemed fine after a few months of testing. Silicon Labs 700 USB device. Then I migrated in 50 more nodes (from Fibaro Home Center 2) and ZwaveJS network performance turned awful and I noticed the "Jammed" status. I was on 7.19 firmware but upgraded to 7.21.3 - no improvement. 
|
Beta Was this translation helpful? Give feedback.
-
|
Has anyone tried version 7.22.0 ? Firmware 1.40 (based on SDK 7.22.0) https://www.support.getzooz.com/kb/article/1158-zooz-ota-firmware-files/ |
Beta Was this translation helpful? Give feedback.
-
|
Yes, see #6874 |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, I'm new here and haven't worked with Z-Wave before, but just looked into the SDK Docs for SDK 7.22.1 GA, namely https://www.silabs.com/documents/public/release-notes/SRN14930-7.22.1.0.pdf Am I reading this right, that they just dropping support for the 700 Series Sticks and devices now?
This is insane. |
Beta Was this translation helpful? Give feedback.
-
This is the existing Gecko SDK. 800 series support has been split off into the Simplicity SDK. |
Beta Was this translation helpful? Give feedback.
-
|
I received an email last night from Zooz saying that Silicon Labs had just released 7.22.1.0 and Zooz now has a version 1.5 that supposedly fixes this issue. In the SiLabs release notes, it previously showed issue number 1227385 as "The 700/800 controller can lock itself up. The controller is not able to send acknowledgements and the data transmitted is corrupted". Now in these new release notes, that issue is listed as "While the controller stability has been greatly improved in Z-Wave Classic, the workaround implementation is still recommended on the host side". Not sure why they changed the wording, nor do I understand why that is still listed under known issues if it is "fixed". However, under the list of fixed issues, you can find number 1321606 which is "Fixed an issue causing a controller to be locked in a constant beaming pattern. The behavior was caused by an incorrect configuration entered in the controller NVM" which sounds like the issue we were all seeing. Oddly enough, while you can download the 1.5 firmware from Zooz here and this is the actual file link. Interestingly, their own release notes do not yet list the 1.5 version or the changes. Still it's something. Anyone wanna roll the dice and update to see if it is fixed?? |
Beta Was this translation helpful? Give feedback.
-
|
I’ve downgraded to a gen5 Aeotec because my mesh got so bad. Since my 800 stick is already considered lost in my mind, I will install and report back. Thanks for the link! |
Beta Was this translation helpful? Give feedback.
-
|
Extremely small sample size, but after about 90 minutes for me, 7.22.1 is a huge improvement over 7.22.0. I am still seeing more dropped RX (messages and commands) than I do on my 500 series controller, but it is much better than before. I will note that in between testing 7.22.0 and 7.22.1 I did remove my LR devices and re-pair them as standard (to use the mesh), although I have no idea if that would impact stability (just wanted to make it clear it isn't exactly apples-to-apples comparison). Thanks for the pointer to the new bits!
|
Beta Was this translation helpful? Give feedback.
-
I got a similar email from them tonight regarding 1.4 for the ZAC93. They replied to my email from July 2023 😂. |
Beta Was this translation helpful? Give feedback.
-
|
I've updated my ZST39 (using Silicon Labs software).
It seems good to me for now, but the system was updated only 12 hours ago,
so I'll need more time to be sure.
Anyway, it does seem more stable. Previously, when I was on 7.22.0 (SDK
1.40), I ran into "locked" states three or four times a day.
By the way, I experienced more issues on 7.22.0 than when I was on 7.19.0.
After the update, the Z-Wave JS controller status is always in an "unknown"
state.
Mail inviata da dispositivo Mobile
Il Ven 13 Set 2024, 18:01 Bill White ***@***.***> ha scritto:
… I received an email last night from Zooz saying that Silicon Labs had just
released 7.22.1.0 and Zooz now has a version 1.5 that supposedly fixes this
issue. In the SiLabs release notes
<https://www.silabs.com/documents/public/release-notes/SRN14930-7.22.1.0.pdf>,
it previously showed issue number *1227385* as *"The 700/800 controller
can lock itself up. The controller is not able to send acknowledgements and
the data transmitted is corrupted"*. Now in these new release notes
<https://www.silabs.com/documents/public/release-notes/SRN14930-7.22.1.0.pdf>,
that issue is listed as *"While the controller stability has been greatly
improved in Z-Wave Classic, the workaround implementation is still
recommended on the host side"*. Not sure why they changed the wording,
nor do I understand why that is still listed under known issues if it is
"fixed". However, under the list of fixed issues, you can find number
*1321606* which is *"Fixed an issue causing a controller to be locked in
a constant beaming pattern. The behavior was caused by an incorrect
configuration entered in the controller NVM"* which sounds like the issue
we were all seeing.
Oddly enough, while you can download the 1.5 firmware from Zooz here
<https://www.support.getzooz.com/kb/article/1158-zooz-ota-firmware-files/>
and this is the actual file link
<https://www.getzooz.com/firmware/ZST39_SDK_7.22.1_US-LR_V01R50.zip>.
Interestingly, their own release notes
<https://www.support.getzooz.com/kb/article/1352-zst39-800-long-range-z-wave-stick-change-log/>
do not yet list the 1.5 version or the changes. Still it's something.
Anyone wanna roll the dice and update to see if it is fixed??
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROLU2H3DANDGEVR6ONTZWMD5VAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRTHE3DQMA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
when you say "After the update, the Z-Wave JS controller status is always in an 'unknown' state", you're referring to the 7.22.0 release correct? Not now with the 1.5 / 7.22.1 release? |
Beta Was this translation helpful? Give feedback.
-
|
Mine's fine on 1.5 / 7.22.1 🤷 |
Beta Was this translation helpful? Give feedback.
-
|
Hi there,
I'm referring to 7.22.1 and the latest version of zwavejs (updated at the
same time... zwavejs 13.3.0). 🤖📱
So, it may be the firmware or zwavejs version.
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Ven 13 Set 2024, 20:14 Bill White ***@***.***> ha scritto:
… when you say "After the update, the Z-Wave JS controller status is always
in an 'unknown' state", you're referring to the 7.22.0 release correct? Not
now with the 1.5 / 7.22.1 release?
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROJITJW5HGPDS6L73E3ZWMTQTAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRUGA4TANY>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Just to be more clear...
...... there is no impact at all; it's only a visual problem!
I don't have any automation based on the "zwavejs status."
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Ven 13 Set 2024, 21:03 Andrea Crippa ***@***.***> ha
scritto:
… Hi there,
I'm referring to 7.22.1 and the latest version of zwavejs (updated at the
same time... zwavejs 13.3.0). 🤖📱
So, it may be the firmware or zwavejs version.
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Ven 13 Set 2024, 20:14 Bill White ***@***.***> ha
scritto:
> when you say "After the update, the Z-Wave JS controller status is always
> in an 'unknown' state", you're referring to the 7.22.0 release correct? Not
> now with the 1.5 / 7.22.1 release?
>
> —
> Reply to this email directly, view it on GitHub
> <#6512 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AGGSROJITJW5HGPDS6L73E3ZWMTQTAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRUGA4TANY>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***
> com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
I still see jammed events on my ZST39 w/1.50/7.22.1.... But they are fairly infrequent (maybe 1x/day). Not complaining, just reporting. I can live with that, as I really like the significantly stronger signal I get on my ZST39 vs my UZB-7 (5-6 dB across the board). I have 100 nodes on my network, 67 mesh and 33 LR. |
Beta Was this translation helpful? Give feedback.
-
|
bummer :( |
Beta Was this translation helpful? Give feedback.
-
|
Same situation for me. My network is usable now at least. |
Beta Was this translation helpful? Give feedback.
-
|
Today, I experienced some repeatedly jammed events. 😤
I needed to unplug the stick and reconnect it to get normal behavior. 🛠️
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Sab 14 Set 2024, 17:53 Botched1 ***@***.***> ha scritto:
… I still see jammed events on my ZST39 w/1.50/7.22.1....
But they are fairly infrequent (maybe 1x/day). Not complaining, just
reporting.
I have 100 nodes on my network, 67 mesh and 33 LR.
—
Reply to this email directly, view it on GitHub
<#6512 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROLKEF2ICJRANILPV7TZWRLXTAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRUG42TCNQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
that's disappointing to hear :( |
Beta Was this translation helpful? Give feedback.
-
|
Same boat. I had a week or more of consistency (about 150k commands of which only 3k or so had failed). Unfortunately today the controller went into an unavailable loop. After unplugging and trying to restart zwavejs I can't even get the serial port open. Ugh, what a bummer. Perhaps back to restoring onto a 500 series stick again 😂 . |
Beta Was this translation helpful? Give feedback.
-
That's nothing to laugh at. At this point the fact that they don't allow firmware downgrades is worth a class action because they are preventing you from using your device. Apple got fined for much less. |
Beta Was this translation helpful? Give feedback.
and others
-
Checklist
I have read and followed the above instructions
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there or the fix did not work.
Describe the issue
What is happening?
I am commonly seeing my USB device (Aeotec Z-Stick 7 Plus) report being "Jammed" and then shortly after report being "Ready." Around this time, any operations will fail to occur and the system does not go back and "recover" from missed actions / automations.
What did you expect to happen instead?
Jammed status is unexpected.
Steps to reproduce the behavior:
Under the Z-Wave integration, click the "xx devices" to list out all devices. Scroll to locate the USB Stick and click to open. Information will be in the "Logbook" section showing when it is Jammed and when it changes to Ready.
Anything else we should know?
The intermittent functionality was first observed around early- to mid-September of this year (I typically keep my system fully patched as they become available). It settled back down in about a week's time then re-appeared in mid-October. The impacts to the system vary, but the Jammed state is a constant occurrence.
I have done the following troubleshooting to date (in no specific order):
The problem persists with no change from any of the above changes / steps.
Software versions
Driver (node-zwave-js): ...
Z-Wave JS UI: 3.0.2
Home Assistant Z-Wave Integration: ...
Home Assistant Z-Wave JS Addon: ...
ioBroker.zwave2 Adapter: ...
If you are using something non-standard, tell us here: ...
I have no idea how to identify the others... I don't even see node-js in my list of add-ons.
Device information
Manufacturer: ...
Model name: ...
Node ID: ...
Checklist
I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).
Upload Logfile
zwavejs_2023-11-17.log.zip
Beta Was this translation helpful? Give feedback.
All reactions