Controller reporting "Jammed" and then "Ready", operations hang #6512
Replies: 8 comments 61 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.
-
|
It's already on my list: #6814 |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thank you for all your hard work! This has been a nightmare and Silicone Labs doesn’t seem to care enough to fix it in a timely manner - 9 months and counting! I have to say, my problem got much worse after adding Zooz Zen30 double switches. Not sure if it has anything to do with it or not. |
Beta Was this translation helpful? Give feedback.
-
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