If multiple events get triggered on the hub for unknown reasons then wouldn't looping through and generating more events possibly exacerbate the situation?
The lock I recommended for my client was the YRD256 with the Zigbee module - which I use at my house. Just paired that 2 days ago and it seems to be working very well so far. It is the only ZB device on that hub at present. I am glad I went that route.
The biggest issue for me right now is the inconsistency. Devices are delayed in their commands/events, pairings partially succeed creating ghosts and preventing further inclusions or fail to pair sometimes but succeed other times. Mesh seems unstable even with a bunch of repeaters everywhere.
The problem I'm having is being able to discern when the trouble is with the hub or a device itself. Until things settle for the hub I'm kinda in a holding pattern with troubleshooting device specific issues unless there is some obvious physical issue.
edit: something odd just happened with the forum on my browser. I thought my post immediately followed yours but all of a sudden there was a bunch of posts that popped up in between. I guess my browser did not refresh properly... seems to be all about the refresh!
While I'd like to think there are major zwave tweaks coming i am thinking it's not so. Historically when staff have found and fixed an issue anywhere it is promptly posted an announced for "next release" while I have seen some of these i have not seen any saying this zwave thing is better or that is fixed.
So I remain hopeful. Though I am starting down the path of wishful thinking.
Of course the larger/more complicated the update the longer the testing and lead time. We are soo spoiled with these rapid updates from Hubitat it's easy to get impatient - I am totally guilty of this. I am just thankful they are as responsive as they are.
Yes. Its not weak meshes. it not "send logs", its just, "Yes. " Yes there are major problems prticularly with ZWave. There are a number of explanations for why this happened, but if you look through these forum, there are many "fixed in 2.2.4" responses from Hubitat staff, so I remain hopeful. But until that's released, its a bit of a mess for many of us suffering with slow responses, repeating events, daily reboots, and stuff just not working right.
Resetting the radio 3 times is not expected, nor required to have a functional Z-Wave mesh. @wogfun I would like to make sure your hub doesn't have an odd hardware malfunction, as what you are reporting is not common. If you didn't do so already please send us an email at support@hubitat.com so we can further investigate.
Hi Bobby, sorry I'm just seeing this now. No news is good news, and while the last 15 days haven't been perfect, they've been acceptable. Some slow responses, but nothing that doesn't clear itself up in about 45 seconds.
The thread is long so I'll repeat it here. What finally got me able to pair all my devices was unclicking all the security features on inclusion and NOT entering the DSK. The first 3 times around I was leaving security features checked and entering DSK codes. This did not work for me. If the hub gets crazy again I'll shoot you a message, thank you.
Reporting issues of "FAILED" devices still isn't fixed in the settings --> Z-Wave Details page for me, but the devices still appear to be functioning ok (just like before).
I only had one z-wave device do this on 2.2.4.143 (Aeotec recessed door sensor Gen5) and simply opening the door, waiting 10 seconds and closing the door solved the problem.
In previous FW editions, I had a bunch of motion sensors impacted too and they needed to be triggered by motion and then repaired.
.. Major Z-Wave C7 updates in 2.2.4.
