erktrek
January 31, 2022, 2:01pm
18
I apologize - meant no offense! Checking back on the status is perfectly fine though the answer is still kind of the same. Yes there has been improvements but that is certainly true of most active systems out there.
You had some issues with motion lighting and you want to know if those kinds issues have been resolved/improved? Maybe?
correction - need coffee apparently. There was a Z-Wave firmware update that supposedly resolved some of the more cantankerous db issues. There is some other contention issue that Silicon Labs has yet to or maybe recently addressed but that affects all of their 700 series radios I think.
If you have a UZB-7 stick there is a firmware update available:
Links to the US 7.17.1.344 UZB FW are here for those interested in updating their UZB sticks. If you have the Silicon Labs stick the instructions are in the Ghost Removal doc .
And EU here:
here is an explanation of the issues taken from the above thread.
opened 03:56PM - 15 Dec 21 UTC
closed 06:53AM - 28 Apr 22 UTC
It seems that **700-series sticks** (including the currently latest firmware 7.1… 7) have some problems which mostly appear on networks that:
* are relatively busy (lots of unsolicited reports like motion sensor, power meters)
* are large and/or
* contain some battery-powered devices
When lots of reports reach the controller in a short time, the 700-series sticks are not able to send any message.
It looks like the stick is somehow blocked and simply doesn’t send anything, maybe not even the protocol level acknowledgements for receiving the messages, causing end nodes to repeat their messages over and over, making the situation even worse.
### 👷🏻♂️ EDIT: Fix available, see [below](https://github.com/zwave-js/node-zwave-js/issues/3906#issuecomment-1065109783) for direct links to the updated firmware 7.17.2
### 🔥 Bug in NVM conversion routine, potentially causing connectivity issues. Details see [below](https://github.com/zwave-js/node-zwave-js/issues/3906#issuecomment-1068031298)
#### 🗳 If you've updated, please take part [in the survey](https://github.com/zwave-js/node-zwave-js/issues/3906#issuecomment-1026889320) so we can see if the update helps.
---
We believe the following symptoms are all caused by this:
- Huge delays (up to 60 seconds) when sending messages
- Failure to send anything (`TransmitStatus: Fail`)
- Floods of incoming reports that are transmitted over and over
- Incorrect neighbor information (e.g. controller doesn't list some/any nodes as neighbors, etc.)
- Failure to heal the network or individual nodes, especially in busy situations
---
Additional background info:
https://forums.homeseer.com/forum/homeseer-products-services/homeseer-z-wave-products/smartstick/1483440-does-anyone-have-a-solid-working-g3-system-at-this-time/page4#post1510687
---
**A workaround** until this is fixed is **migrating back to a 500 series stick**, using the migration tool 700<->500 series. Description:
https://github.com/zwave-js/node-zwave-js/issues/3906#issuecomment-997484466
1 Like