I am having an issue with extreme delays on my C-8 hub. I have about 125 devices (some with sub devices). Some of the commands take up to 60 sec. to process.
I have remove all ghosts. Indeed I at the beginning add device with security. That feature should work but it does not. Many of my Ghost were probably related to this. I had to use 2 type of secondary radio and my old C-7 hub though the Silicon lab software to get rid of of all ghost. The problems now seem to come with the Aquara devices with are battery operated. The z-Wave one become ghost when the hub does not seem them. For some reasons the hub is telling me that the zigbee network is overloaded. I thin its polling the battery status or something. In regards to the software update I have about 60 Zooz devices. I do suspect that the original firmware is causing issues but I cannot update it through Hubitat. I would have to unpair use a secondary radio and repair. That is 2-3 days of work which is too much.
My real issue is that some commands take a full 30-60 sec to process.
I actually don't know why it is so slow. It seem that most commands done using Zooz Scene controller button (The 4 buttons on the zooz32) are the slowest ones.
Any idea where to start to find out why it is so slow? (BTW the C-7 was fine, it is only started about 3 months after I moved to C-8).
The hub is very central in the house and has a clear unobstructed path to about 60% of the devices.
Someone suggested that it must be a bad mesh which I am not what is a good or bad mesh. here is picture of my mesh.
I'm little confused here.
Aqara devices are all ZigBee only AFAIK.
You refer to them as part of the Z-Wave issue which has nothing to do with the ZB network being overloaded.
You might need to show the Z-Wave Mesh table as this has relavent data for problem determination.
ZIgBee s a whole other issue. There is a Settings | ZigBee Details page to see if they are all talking.
I assume you have done a shutdown and unplug for 20 minutes just so the radios and devices can clear their heads?
Indeed I know that Aqara device are Zigbee. I mentionned both Zigbee and Z-Wave since I do not know which one is making the hub slow. Indeed, I did all kind of shutdown, reset. Update etc... Here is the table
I wished it was that simple. I remove all ghosts about one a month but th hub keep creating them. When I get rid of ghost it is a little faster but not much.
open your app, look if anything is in smart start, trash can it in the app, then go back and try to remove it. If they're that difficult to remove you will need a z-wave stick paired as a secondary controller to remove them.
FWIW, using S2 when joining Z-Wave devices is no longer generally discouraged, and can actually help w/Z-Wave device reliability in responding to commands. Using it when adding new devices has not been seen to cause additional issues w/creating ghosts during pairing.
Hubs also don't usually create a bunch of ghosts on their own...did you add or remove Z-Wave devices after you removed your ghosts? Or did you make any other changes to your Z-Wave network, like moving mains powered Z-Wave devices to new locations?
They are infact ghosts. See that discover button? 86 & 87 we're probably caused by failed proper pairings of 89. These devices won't route properly and are probably the cause of your mesh delays.
You will need a z-wave stick paired as a secondary controller then to remove them.
Well after all I found who was guilty for these delays. It was the various ZooZ Zen32 scene controller. I have 7 of them. I had to change them that just stopped working. It seems that these switches were not only creating ghost (which I always had to remove) but also created delays even when no ghost were present.
For now I am keeping them but I had to:
Flash the new 10.40 firware (using firware updater);
Exclude the device
Reset the device to factory setting
Include
Redo the rules that included them
Many people are complaining about the Zen32 and hey are right you should avoid these devices. Also the ZEN16 (relay box) are very problematic. I had 2 and had to completly remove one and replace it with something else.
I have about 50 Zooz devices of all types and I regret using them. Randomly they stop working and I have to pull the air gap switch to make them work again. And when I say stop working I do not mean just z-wave I mean they stop working when physically press the switch.
ZooZ are medium cost but they are very cheap and badly built.
One of 7 is 800lr and that one is no problem. Even the old series when I replaced one that one was OK also. So its clearly a hardware defect on earlier batches. Maybe they fixed it in version 10.40 but the release note does not say it. This is no surprise because they will not acknowledge a defect in the release note. If this is still good in 2 weeks then I will know.
I can now say that I was right in the first place. After months of hunting ghost, replacing switches etc... it was always becoming very very slow. Last week I replaced the C-8 for a C-8 pro and voila, problem solved. So the C-8 cannot handle the 100+ devices. Whatever was said here by HE or others it was a very simple issues of processing power. It also means that Hubitat knows and that is why they released the C-8 pro so close to the C-8 because C-8 had not enough power
It’s not that the C-8 hub is underpowered—it’s actually capable of handling hundreds of devices. The limitation is that the C-8 doesn’t really support the latest Z-Wave JS implementation, which significantly improves the Z-Wave experience and resolves issues that older Z-Wave versions couldn’t.
I have not even used the new Z-Wave JS yet. I tried but since it would require me to re interview all devices I gave up for now. So the problem has been solved staying with the legacy Z-Wave. I will eventually switch to the new protocol but only when I will have a lot of time to fix migrations issues.
So it is truly only the effect of processing power and RAM of the C-8 pro
BTW I now have definitive results. The delays were caused by the C-8. When I switched top the C-8 pro the delays stopped. I waited 6 months to switch to zwave js. It went well but had no influence on the delay. The delay never returned on the C-8 pro. SI I can now tell for sure that the limitation are real. It is propbably why Hubitat decided to release the C-8 pro so soon after, the knew about the problem and releasing a new unit was their way of fixing it,
