I just tell mine I did it on purpose to remind her how much easier/better having automation makes her life. However, it doesn't go over as well as it should 
2 Likes
In this example, it was a ~12 second delay. And the delay was at the level of the chime (device) responding with the desired chime and not the rule executing. Which was my suspicion.
It may also be that your contact sensor needs debouncing - because there are two events in quick succession, although the second event doesn't seem to re-trigger the rule.
I'm tagging @jtp10181 - his z-wave expertise would be valuable here.
The second log of the chime might be from some sort of retries happening behind the scenes and then both messages finally made it to the device around the same time.
I would be interested the see the event log from the Zooz Chime (device page > events). This will show when the command was actually executed, to determine if the delay was the rule sending the command, or the command getting to the device.
2 Likes
I’m out and about atm, but interesting observation. Here’s a screenshot of what you asked for. Seems indicative of the chime delaying the execution.
No. I don’t think the command is making it to the chime right away. Either radio contention or something else? The chime is probably responding as soon as it receives the command.
Do you have a lot of power reporting devices?
I wonder what would happen if the chime were paired as a mesh device and not a LR device?
I do have an anomaly with some indoor motion sensors that seem to flood occasionally. I’ve kind of ignored it but maybe this is contributing.
Sometimes there are more than a dozen rapid fire activation messages.
1 Like
@jtp10181 would be the better judge here.
Are you using ZWaveJS or Legacy Z/IP?
Looks like Zip since I have option to switch to JS
Tread carefully sir, negative WAF has killed more than one HA project....
2 Likes
I’d leave it as legacy for now. However, 2.4.4, which has not yet entered beta, is indicated to contain major improvements to ZWaveJS. I’d recommend trying it out then.
1 Like
Haha. Trust me. I understand completely. It can work flawlessly for a 1000 times, but that one time…..we’re back at drawing water from a well.
1 Like
Do you know approx what your hub uptime was in the above zwave details? Sporadic delays occasionally - #10 by jeff.turner.reid
Looks like you have multiple spammy devices based on the message counts, unless the hub had been up for weeks at that point then maybe not as bad as it looks.. Also appears you did not refresh the stats first, so we cannot see the RTT values.
I was away for two weeks over the holidays. Upon my return I had devices overwhelming the hub. Never saw that before but a reboot corrected everything back to “normal”. Up time would be about a week then.
When you say “spammy” devices, I have noticed the motion sensors reporting way too much. Is that what you are referring to?
Events from family Motion detector. Set to reset activity after 15 seconds. Seems normal, but there are multiple reports sent to the hub upon activation.
Fibaro Motion Sensor ZW5
Yeah your motion sensors and possibly some other devices are hammering the hub. I did some rough math with the devices with higher message counts, and its coming out to one message every 4 seconds. You could probably assume around 50% of the time the house is idle, so that would double it one every 2 seconds.
So I would say in high activity times you could be looking at a steady stream of zwave messages every 1-2 seconds non stop.
Seems excessive, and seems reasonable that it would cause delays on other devices.
Even though your Zooz Chime is LR, the hub still has to process and respond to the constant barrage of messages, so the outbound message may be getting queued up to be sent as soon as it can.
You will have to look into those devices with the high message counts and see if they have any settings available to dial it back. Keep in mind that the Hubitat drivers may not expose all the settings the device has available.
1 Like
I have noticed the chattiness of these motion sensors. I’m not sure why they report activity so rapidly without seemingly waiting on an acknowledgement. I’ll try resetting with a battery pull but it doesn’t make sense why they would ever do such.
They ALL (5 of them) do it.
