Controller reporting "Jammed" and then "Ready", operations hang #6512
Replies: 31 comments 154 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.
-
|
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.
-
|
This is pure crap. I have around 45 lights, and every time they are turned on or off, the error message "unable to set target value" appears, resulting in one or more lights failing to turn on or off. It's not fun to wake up in the morning only to find that some lights have been on all night. My Z-Wave network is otherwise in good shape, so that can't be blamed. I'm really fed up with this, and the fact that no firmware exists to fix this issue... TERRIBLE! |
Beta Was this translation helpful? Give feedback.
-
|
That sucks. Can you not switch to an 800 stick? Or downgrade to a 500? With Zwave JS UI you can create and restore nvm backups. |
Beta Was this translation helpful? Give feedback.
-
|
I have the 700 stick! Is the 800 free from these issues? |
Beta Was this translation helpful? Give feedback.
-
|
Switched from 700 to zoom 800 pretty much same errors |
Beta Was this translation helpful? Give feedback.
-
|
OK! Sad to hear that! I think I have to buy a 500 stick. Seems like they run flawless. |
Beta Was this translation helpful? Give feedback.
-
|
I'm on zst 39 ... from zooz
A way much better then the 700 from aeotec.
Can't say anything about 500 ... I've got one from aeotec and always got
random freeze.
As for today ... the zst 39 is my best stable setup. ( 7.22.1)
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Lun 2 Dic 2024, 16:16 Spazpeker ***@***.***> ha scritto:
… Switched from 700 to zoom 800 pretty much same errors
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSRONE7S3TD3FQB2ME52T2DR2VPAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBTG44DKMA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Check the community forums of HomeAssitant. There are people who have done it. It depends on the firmware the stick is running. |
Beta Was this translation helpful? Give feedback.
-
|
I backed up 700 and put on 800 |
Beta Was this translation helpful? Give feedback.
-
|
You can always follow the controller shift process to change between controllers (500<>700<>800<>500,etc). |
Beta Was this translation helpful? Give feedback.
-
|
Yeah! Since I made the mistake to go for the Aeotec I may need to stay there. Will most likely go back to a 500 stick. |
Beta Was this translation helpful? Give feedback.
-
|
The 500 series stick must have a firmware based on SDK 6.61 or newer. Assuming you'll use an Aeotec Z-Stick 5, that means firmware 1.2 is required. As long that is the case, you can freely migrate back and forth using NVM backup/restore in Z-Wave JS UI. Do not use PC Controller to do the migration, since that won't perform the necessary conversions. |
Beta Was this translation helpful? Give feedback.
-
|
A heads up: the Simplicity SDK has a new release, 7.23. The release notes make a bold claim that this is now fixed.
|
Beta Was this translation helpful? Give feedback.
-
|
Does that mean that 700 series is basically dead feature wise? |
Beta Was this translation helpful? Give feedback.
-
|
Not sure but seems so. Any info on when Aeotec will have FW based on 7.23 for the 800? |
Beta Was this translation helpful? Give feedback.
-
|
Nice! Hopefully it won't take Zooz a year to put out the new firmware. |
Beta Was this translation helpful? Give feedback.
-
|
Any news on when Zooz wil release a new Firmware for the 800? The last firmware is still SDK 7.22.1 |
Beta Was this translation helpful? Give feedback.
-
Well I emailed them yesterday asking to be put on the waitlist for 7.23 since my issues weren't resolved with 7.22.1 and they told me "Silicon Labs has released firmware 1.50 for the ZST39 800LR Stick, which has resolved the lockup issue in most cases." Sooooo no I'm not sure when they'll have something lol. |
Beta Was this translation helpful? Give feedback.
-
|
Yup,
nailed it!
Starting from SDK 7.22
3.5 - Deprecated Items
<https://www.silabs.com/documents/public/release-notes/SRN14930-7.22.2.0.pdf>
As of the 7.22.0 stack release, the 700 platform is not supported by the
Simplicity SDK.
<https://www.silabs.com/documents/public/release-notes/SRN14930-7.22.2.0.pdf>
The 700 platform will be maintained through the 7.21.x release stream.
<https://www.silabs.com/documents/public/release-notes/SRN14930-7.22.2.0.pdf>
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Gio 19 Dic 2024, 20:01 Niccolò Belli ***@***.***> ha
scritto:
… Does that mean that 700 series is basically dead feature wise?
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROJ3SRJ72TZIPSCYEOD2GMJZFAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRSGEYDEMI>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Far as I can tell, Aeotec hasn’t dropped any Z-Wave 800 controller yet.
Maybe they’re still buffering or stuck in dev mode.
[image: image.png]
Crippa Andrea
Il giorno gio 19 dic 2024 alle ore 20:27 Magnus Lundberg <
***@***.***> ha scritto:
… Not sure but seems so. Any info on when Aeotec will have FW based on 7.23
for the 800?
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROJGXXP4OACV4QGOLWL2GMM3HAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRSGEYTQNI>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah, just realized that so obviously those of us with a aeotec 700 are stuck since migrating from 700 to 800 not seems to be possible through nvm backup restore. So bad this… |
Beta Was this translation helpful? Give feedback.
-
|
Migrated mine from 700 to Zooz 800 via backup worked ok, had to re enter some of the names of secondary switches |
Beta Was this translation helpful? Give feedback.
-
|
Ok. Good News. Did you do through nvm on zwave ui? |
Beta Was this translation helpful? Give feedback.
-
|
If I recall correctly, @AlCalzone, the developer of the Z-Wave JS app, has
confirmed this multiple times that migrating from 700 to 800 is definitely
possible using the Z-Wave JS backup-restore NVM function.
Avoid using "PC Controller" to do the migration, since that won't perform
the necessary conversions between versions.
Just for example , I've started my network on aeotec 500 chip, migrated to
aeotec 700 chip and then to zooz 800 chip
Crippa Andrea
Il giorno gio 19 dic 2024 alle ore 20:54 Magnus Lundberg <
***@***.***> ha scritto:
… Yeah, just realized that so obviously those of us with a aeotec 700 are
stuck since migrating from 700 to 800 not seems to be possible through nvm
backup restore. So bad this…
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROJDBESZ47ASSOCMCRD2GMP6XAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRSGEZTOOA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Good News. Will try:) |
Beta Was this translation helpful? Give feedback.
-
|
Yep....
Z-Wave JS UI ---> General actions --> NVM Management --> Backup (and then
Restore on the new one)
Crippa Andrea
Il giorno gio 19 dic 2024 alle ore 21:29 Magnus Lundberg <
***@***.***> ha scritto:
… Ok. Good News. Did you do through nvm on zwave ui?
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROMSGMOS33R74ITNG532GMUDNAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRSGE3DENA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Is the 800 stable or are you facing the same issue as with the 700? |
Beta Was this translation helpful? Give feedback.
-
|
*Hopefully it won't take Zooz a year to put out the new firmware.*
Typically, it should take a couple of months or so.
Right now, I'm on FW: v1.50 SDK: v7.22.1, and I haven't encountered any
issues (or only very occasional ones).
I'm really satisfied with this release.
I'm currently managing around 100 nodes with no problems (mixed in No
Security , S0 and S2)
Crippa Andrea
Il giorno gio 19 dic 2024 alle ore 21:34 Ryan Worrell <
***@***.***> ha scritto:
… Nice! Hopefully it won't take Zooz a year to put out the new firmware.
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROK4565SIXDKHFPKGIT2GMUW7AVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRSGE3DQMI>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
*Is the 800 stable or are you facing the same issue as with the 700?*
As mentioned earlier, I'm on FW: v1.50 SDK: v7.22.1, and I haven't
encountered any issues (or only very occasional ones).
Crippa Andrea
Il giorno gio 19 dic 2024 alle ore 21:41 Magnus Lundberg <
***@***.***> ha scritto:
… Is the 800 stable or are you facing the same issue as with the 700?
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROIX6FFUVG4D7LGP3JT2GMVN7AVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRSGE3TENQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
During Christmas, I cleaned up my setup by addressing issues such as avoiding duplicate calls to the same devices and re-interviewing or removing faulty devices. I also scheduled the Zwave JS UI Addon to restart three times a week, which has significantly improved the network's stability. Despite these efforts, I find it frustrating that the underlying jamming issue remains unresolved. As an additional measure, I have ordered a new ZooZ 800 stick. Hopefully, this will provide further improvements, though I remain skeptical... |
Beta Was this translation helpful? Give feedback.
-
|
This explains why I've been seeing all these jamming messages, and surprising number of dropped messages! I average about 200-300 of these messages daily. I really hope Zooz is planning on updating the ZST39 stick firmware to 7.23.0, and that finally fixes this. |
Beta Was this translation helpful? Give feedback.
-
|
In the meantime If not already done you can try to schedule a restart of the ZWave UI Addon every night |
Beta Was this translation helpful? Give feedback.
-
Yeah , that's too disruptive imo. It's not horribly unstable, but indeed could be better. |
Beta Was this translation helpful? Give feedback.
-
|
Restarting Z-Wave JS UI shouldn't have any effect other than doing a soft-reset (restarting the stick). This may be automatable through MQTT: https://zwave-js.github.io/zwave-js-ui/#/guide/mqtt?id=softreset |
Beta Was this translation helpful? Give feedback.
-
|
What's brutal about this bug is that it most impacts those who invested deeply in Z-wave with a big network. It would cost a fortune to swap to a new platform for homeowners (like me) from countries that aren't allowed to touch their home wiring. I spent a week over Christmas splitting my ZWaveJS network into 3 separate ZWaveJS controllers, each with no more than 27 nodes. Lots of time crawling in the roof, associating, then reconfiguring Home Assistant entities, groups, scenes, etc. Still no good. Control of any individual light is rapid, but it is slow/fails with a "9am turn all lights off" automation - a smart home task which seems modest to a layperson. Humble feature request: could we give users a global option to add a (configurable) delay between commands sent to the network? I reckon even 100ms would help a lot. I realise this requires queues which could be a headache. But, in the absence of a firmware solution from SiLabs, this is a step that the zwave-js project could take. Configurable delays might also benefit non-buggy networks. Does anyone else think a configurable delay could help? |
Beta Was this translation helpful? Give feedback.
-
Always possible, of course. But I will say that when I would send the 20+ individual commands when it failed I would see/get the Controller Jammed message from the controller. When I send a few multicast messages with many devices per message I never get the Controller Jammed error logged from the controller. I've watched it on my zniffer, and there is obviously a firestorm of status update/ACK messaging after the multicast sets go out but the controller itself doesn't seem to jam in those scenarios as I never get that error/message. |
Beta Was this translation helpful? Give feedback.
-
|
Isn't the controller more prone to jamming when it's receiving, not sending? The vast majority of my devices with high dropped commands are power switches with reporting. IME the dropped RX count for the controllers tends to shoot up when the controller jams. |
Beta Was this translation helpful? Give feedback.
-
|
Anecdotally, lots of incoming traffic can cause the issue more easily. Maybe multicast causes the controller firmware to take a different code path that is not as affected. |
Beta Was this translation helpful? Give feedback.
-
|
Could be. Or it could just be a quirk of my specific mesh/controller. One data point isn't exactly conclusive proof of anything. |
Beta Was this translation helpful? Give feedback.
-
here you go ... Feature Request #7557 |
Beta Was this translation helpful? Give feedback.
-
|
Well, the latest firmware for the Zooz ZST39 does not seem to complete solve the problem. Still getting "jammed" messages and returning back to "ready". Also I have Error: Unable to set value 70-38-0-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts (ZW0202) messages suddenly. This never happed on my older 500 stick. Nor ever seen the Z-Wave 202 errors. before in the 5+ years I have a Z-Wave network. As I have S2 devices added now with S2 security, I am thinking of going back to an Aeotec 500+ stick. It supports S2. The Aeotec sticks with the 500 chips were so stable. Rocksolid. Never had these kind of issues with them. Newer is not always better it seems. |
Beta Was this translation helpful? Give feedback.
-
That is the version I ordered. I have S2 devices that I want to keep connected with S2. 🙂 |
Beta Was this translation helpful? Give feedback.
-
There is nothing in the Z-Wave protocol in regard to S2 where the controller is involved. The only modern thing that requires controller support is SmartStart. You could include devices via S2 on a 300 series controller if you really wanted. |
Beta Was this translation helpful? Give feedback.
-
|
I never walk around with my stick. :-) So that should not be a problem. My only S2 devices are temperature sensors. I pair them when they are close to the controller and move them after pairing. |
Beta Was this translation helpful? Give feedback.
-
|
What I will say is check back regularly on the Zooz firmware site for the 800 series stick. |
Beta Was this translation helpful? Give feedback.
-
|
I found what y'all are referring to in the changelog for the Aeotec stick:
This is irrelevant - Z-Wave JS is the primary controller. |
Beta Was this translation helpful? Give feedback.
-
|
As far as I recall, when I was using the S2 stick, I had to upgrade the
firmware to enable S2 support.
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Ven 17 Gen 2025, 20:23 Zac ***@***.***> ha scritto:
… The gen5 stick does not support it, but gen5+ does. This is the one you
need for S2: https://store.aeotec.com/products/z-stick-gen5-plus-zw090
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROL2JQWW63EDGY5GTCL2LFKEPAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBXGA3TOMY>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
https://aeotec.freshdesk.com/support/solutions/articles/6000252294-z-stick-gen5-v1-02-firmware-update
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Ven 17 Gen 2025, 20:25 Andrea Crippa ***@***.***> ha
scritto:
… As far as I recall, when I was using the S2 stick, I had to upgrade the
firmware to enable S2 support.
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Ven 17 Gen 2025, 20:23 Zac ***@***.***> ha scritto:
> The gen5 stick does not support it, but gen5+ does. This is the one you
> need for S2: https://store.aeotec.com/products/z-stick-gen5-plus-zw090
>
> —
> Reply to this email directly, view it on GitHub
> <#6512 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AGGSROL2JQWW63EDGY5GTCL2LFKEPAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBXGA3TOMY>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***
> com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
I started messing around with some Matter-over-WiFi devices... and
honestly, the tech feels super raw. The same smart plug with WiFi
integration on the local network shows like 6 entities, but in Matter, you
only get one for basic on/off.
Mail inviata da dispositivo Mobile
Crippa Andrea
Il Ven 17 Gen 2025, 20:29 Anakins ***@***.***> ha scritto:
… I confirm. I downgrade form my aeotec 700 stick to GEN5+ stick (with S2).
0 issue since I do this. Before the zwave freeze every 24/48H.
It's an incredible shame that Sigma doesn't take into account the problems
its customers have been facing for a lot of months. Especially since only
large customers with a lot of modules are imapacted. I really have the
impression that they want to kill the zwave and that we are all going for
zigbee...
—
Reply to this email directly, view it on GitHub
<#6512 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGGSROLG4NYGIHWGOCUATUL2LFK2TAVCNFSM6AAAAAA7WQORQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBXGA4DENQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
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