So maybe getting somewhere. I just built this Zwave network from the inside out on the HE hub when I got it and migrated from ST. So the devices were all working OK there. I also did what you said. I did a full reset on them so that it left ghost devices in ST and then added completely new to Hubitat. So all resets. I have since ran zwave repairs in HE....but what does OZWCP do that Zwave repair doesn't?? I'm all for getting this speed thing fixed!! Any info you can provide on OZWCP is greatly appreciated...
This is the ultimate question though...as I don't think we should be needing to run 3rd party software as a resolution. If we can develop a pattern though. HE repair doesn't help, but OZWCP does..then I think we could make a good case for something being amiss in the HE repair.
I wish I would know all the details of OZWCP, I just stumbled over it as I found out that this tools lets you see which device has which other devices as neighbors. I didn't expect it to run a full route update on my existing network. Don't get me wrong, I am glad it did as I am sitting grinning over the speed of my routines now.
I am going to see if I can find some more information on OZWCP. I basically came to OZWCP via this thread: Z wave mesh frozen completely and have about 10 minutes of experience with it...
I have this and will be the first to admit I was afraid of doing more damage than good but not 100% understanding what I was doing in there. Does anyone know of a decent writeup of how to check the health/mesh in Zensys?
Bump. I am on the latest release and experience the same issue. Groups and scenes take up to 5 minutes to execute. Reboots and resets don't help. People have been mentioning this in multiple threads and has been a long time issue.
With each new release we get new (obscure) drivers added, but where are the real fixes for long time problems?
Could you show the group you are having a problem with, and what kind of devices these are. This is not normal behavior at all. Groups are typically very quick to turn on/off.
I have about 8 different groups. I only use them to turn devices off as part of a goodnight, away. etc. type modes.
My devices in these groups are lutron switches and directly connected hue lights (no hue hub). Those are the only two types of lighting devices I use.
I don't nest groups in groups. If I control the device as a single light (after a motion event) it responds normally. However when changing modes and my RM4 triggers a group "off" event, is where I see a very long delay. 5 minutes might be exaggerated, but 2 minutes is not.
I switched all my groups to v2.1 groups. I don't suspect the lutron hub because single light events work fine.
I do use hubconnect.
Can't take screenshots right now, but hope I have given some useful info
If HubConnect is in the middle of this, you're going to have to do some work on the logs to see what is actually going on. As I said, it would not be a normal circumstance for a Group turning off some lights to take very long at all. You might also try isolating the groups to specific types of devices, to see if each of Lutron and Hue work as expected from a Group.
So in an effort to reduce possible weird network traffic, I replaced a few devices from ZWave to Zigbee. Weird thing... I can create a NEW group with these new devices in them, but not add new devices to existing groups. It is not showing up in the list of devices when editing an existing group.
Tried that on both the parent as well as the child app. Still no luck. Works fine with a new group. It's a Generic Zigbee outlet by the way (if that matters).
