Zwave status delay causing event trigger delay - HS Zwave Plugin or Hardware?

[Ltek]

I could really use some help fulling figuring out what is causing this. Event & Log screenshots attached

Issue:
Delays of 4 to 10 seconds completing an event when triggered physically using a Zooz ZEN30 dimmer. The same event completes instantly when using HS4 Web UI to control the same dimmer (which triggers the same event).

Event:
EasyTrigger Groups are used. 'Any' device change detected in Group triggers a sync of 'all' dimmers in this group (4 dimmers).


In the log, I see HS4 event running all commands within 1 second. I'm assuming when HS knows about the change of a given dimmer in the event triggers instantly, no delay... which is why using the Web UI made all the dimmers update withn 1 second.

this makes me conclude that either....

(A) delay is caused by a lag with HS Zwave Plugin processing the Zwave status from the dimmer when its sent from the dimmer, not the UI
or
(B) Zooz ZEN30 dimmer has delays sending status to HS


I'm not sure if I can use HS4 debug to actually when the Zwave PI receives a status update from a device? Have not had time to work that yet.

If you have seen this issue, or have any troubleshooting advice... much appreciated!

[rmasonjr]

You might need to see how many hops the switch is using to talk to HS, especially if the route includes slower devices.

[Ltek]

rmasonjr All the dimmers have direct routes to Homeseer (confirmed with zwave audits). I'm starting to suspect the issue is the Zwave Plugin has problems after a while. About 2 weeks ago someone posted they restart it every 3 hours or it starts to have issues. I think I'm seeing that. I debug logged everything (Zwave & HS) initially from click to light change was 8 seconds (I manually timed several tests - Zwave debug logs showed multiple seconds between commands send to each device)
THEN restarted the Zwave PI and like magic response is under 2 seconds.

I'm still on v3 of the Zwave plugin... wonder is v4 is any better? I've been warry since so many problem reports on v4 even recently. Some people saying they went back to v3.

[randy]

I could really use some help fulling figuring out what is causing this. Event & Log screenshots attached

Issue:
Delays of 4 to 10 seconds completing an event when triggered physically using a Zooz ZEN30 dimmer. The same event completes instantly when using HS4 Web UI to control the same dimmer (which triggers the same event).

Event:
EasyTrigger Groups are used. 'Any' device change detected in Group triggers a sync of 'all' dimmers in this group (4 dimmers).


In the log, I see HS4 event running all commands within 1 second. I'm assuming when HS knows about the change of a given dimmer in the event triggers instantly, no delay... which is why using the Web UI made all the dimmers update withn 1 second.

this makes me conclude that either....

(A) delay is caused by a lag with HS Zwave Plugin processing the Zwave status from the dimmer when its sent from the dimmer, not the UI
or
(B) Zooz ZEN30 dimmer has delays sending status to HS


I'm not sure if I can use HS4 debug to actually when the Zwave PI receives a status update from a device? Have not had time to work that yet.

If you have seen this issue, or have any troubleshooting advice... much appreciated!

Not sure if this has anything to do with your issues, but I would delete 3 of the 4 “Remove Delayed Device Actions”. The duplicates were caused many months ago after one of the beta Z-Wave plugins. There are likely many Events to which that may have happened.

The more troubling is the loop where you look for a change in any light in a group, then launch an action potentially changing all the lights in the group, triggering the Event again, potentially with a new global variable. If you have a “Cannot Re-Run For” set you might mitigate repeated triggers. Your sync Event ran at 8:39:19, 8:39:40 and 8:40:30, each time the same second the Kitchen Panel DS kitchen light value changed.

[Ltek]

Not sure if this has anything to do with your issues, but I would delete 3 of the 4 “Remove Delayed Device Actions”. The duplicates were caused many months ago after one of the beta Z-Wave plugins. There are likely many Events to which that may have happened.

The more troubling is the loop where you look for a change in any light in a group, then launch an action potentially changing all the lights in the group, triggering the Event again, potentially with a new global variable. If you have a “Cannot Re-Run For” set you might mitigate repeated triggers. Your sync Event ran at 8:39:19, 8:39:40 and 8:40:30, each time the same second the Kitchen Panel DS kitchen light value changed.

The “Remove Delayed Device Actions" you see there are not duplicates - they are 4 different devices. That is a bug in HS4 where it does not show the entire name (Location2,Location1,Name) of the device, only 'Name'... I reported that and a few other UI bugs, several months ago. Rich must be using multiple different query and display mechanisms since there is literally multiple different Device display methods, selection boxes, etc.

I didnt mention that Cannot Re-Run is set for 3 seconds... I has it set for 10 seconds for a while since I was seeing crazy delays on Zwave. I'd expect that if EasyTrigger tells HS to set device values, that would all happen within the same second. They don't. The reason I think Kitchen Panel DS kitchen light value changed multiple times in the same second, is that the dim level changes are being reported in series, as they change. I have the dim ramp set for 2 seconds, which - in theory - should not retrigger the event when Cannot Re-Run is set to 3 seconds.