C7 Occasionally Slow Response w/ Z-Wave via webCoRE Piston

All of the overhead lighting in my house is controlled by Jasco Z-Wave motion dimmers. I have webCoRE PIstons that tell the light to turn on when motion is detected. They're very basic actions with no restrictions except for location mode (they don't turn on if mode is "night"). 95% of the time they work perfectly, but every now and then I will enter the room and nothing happens for 5-10 seconds and then the lights will come on. It will happen with several lights at once, too. For instance, if I walk down the hallway to the bathroom, the hallway light and then the bathroom light should turn on. Neither will turn on. About 5-10 seconds later, both will turn on at the same time. The logs in webCoRE and in Hubitat both show everything working correctly as far as device states, sent commands, etc. Nothing seems out of the ordinary there.

What I have confirmed during troubleshooting is that there are no ghost nodes. The Z-Wave mesh looks solid. I've also confirmed that the hub is not using too much CPU or RAM when this happens. It's almost like the thing just goes to sleep and needs to "wake up" before it sends commands.

This is only mildly infuriating, but I'd like to sort it out. Does anyone have any suggestions on what might be happening or how I can troubleshoot it further? Thanks.

Update - this had quit happening for several months, but started happening again after a recent update.

@dbowles1975

Can you post your z-wave details page in it's entirety? (Use windows snip?

Shut down hub, unplug power for 1 minute and bring back up to see if it starts behaving.

What platform are you on?

I get this randomly. I have tried to find the cause....no luck.

I had this years ago and it drove me nuts on SmartThings.
I think I had an Enbrighten switch flooding the networks or Ghosts, which I was uneducated about, at the time.
HE rarely does this now and the two main causes seem to be a Ghost, improperly joined or unjoined, or a Z-Wave anomaly that just requires a shutdown, power off and restart for the radio.
You can post your Settings | Z-Wave Details and we can see if there is anything lurking.

I've done the power down thing a few times. It never seems to help. I've added screenshots of my Z-Wave details. I'm not sure what's up with that last device. That's new. I haven't bothered to figure out what it is yet. Clicking discover does nothing.




Most of the type is quite blurry and small but I don't see any ghosts.
However, I rarely get more than 2 hops and you have a lot of 4 hoppers.
What does you r Mesh look like? Looks like you need better placement of your hub or the external antenna hack. I did that and most of my devices said "Direct" after that.

Settings | Z-wave Details | VIew device topology

2 Likes

it's a ghost, click refresh then remove

Also what platform are you on?

Platform 2.3.9.200

I removed the ghost and it didn't seem to matter. About 95% of the time the Jasco Z-Wave motion / dimmers turn on instantly. The other 5% of the time, they take 8-10 seconds to turn on. They ALWAYS turn on immeidately when triggered from HE directly. That's why I'm leaning towards it being an issue with some sort of delay between webCoRE and HE.

Strange. I can read the type just fine.

Some of those routes make no sense, but I've often read they typically don't make sense, so I've just left them alone.

I'll probably try the antenna hack just for the hell of it.

This is my no means the answer but I have been to hair pulling stages a few times with devices working from the Devices tab but not functioning properly from WebCore..
In the end a few of these instances were fixed but deleting the piston and recreating it, usually from a copy of another similar one.
Something can get corrupt, I don't know what, but this fixes it every time.

I'll have to try that next time.