This reply you got was written by me. The S2 devices you have Included all were reporting as “S2_FAILED” which is going to be an issue for their performance.
The V1 Hub didn’t support S0 per @jlv’s comment.
Presently, you have a bunch of non-secure devices (pre-S0), a handful of S2 devices that have all failed S2 enrollment, and a small amount of S0 devices. I feel that it is a fair summary to say that security level issues due to a mixed bag of Z-Wave devices likely explains at least some of your issues.
I never said it was impossible for your current setup to be operable on a newer V3/Aeotec Hub, just that at present you are having several issues that you would not have been aware of on a V1, due to how old the Z-Wave Radio on that unit was. On a V1, everything would have downgraded to pre-S0, non-secure communication, which would have served you well since I would say offhand 60% of your Z-Wave devices fall into that category inherently (back of napkin math, I did click into a lot of your devices, but not all).
The delays speak to one of two things (in my opinion):
- More messages than can be handled efficiently and a backed up “queue.”
- Insufficient physical coverage by the mesh or distance related issues.
Since you have many devices, and seemingly didn’t have issues prior, I feel that #1 is the more likely explanation (this is also to @jlv point above).
Let’s continue troubleshooting, I don’t think my theory will turn out to be completely wrong, but there may be more to the story. The first step we provided was a “Z-Wave Network Repair” after we had deleted two ghost Node IDs for you. The next would be getting your S2 devices properly enrolled as S2-Authenticated or S2-Unauthenticated devices (depends on model). After that, if there are still issues we can certainly walk you through getting Hub Logs to identify if a particular device (or devices) are “chatty” and causing a queue to build, which would lead to delays.