Why would an action become very slow?

[bobbyD]

@william.cage

I do appreciate your help on this though

Could you please share the make and model of your devices? Sorry if you did and I missed it.

[william.cage]

The switches are all GE Enbrighten Z-Wave Smart Switches. I think the model number is ZW4009.

[william.cage]

BINGO! So, rolled back to 2.2.3.118. That was the oldest version available. When I first tried it, the light did not come on at all. When I went to look at the rule (I am using the simple automation rule that we introduced) it gave a message that there was an unexepected error. I assume there are changes in the two platforms that caused the rule to become invalid. I deleted the rule and re-added it. The light now works instantaneously as it had before.

For completeness sake, I will update to the current platform again to see if the problem reappears and then roll back so that I can replicate. That will confirm that it is in the platform, but doesn't narrow it down at all. I will post my results from my test shortly.

[Sebastien]

I suspect you will find that it doesn’t work on the latest version. @bobbyD has confirmed to me that it is a known issue and that it should be fixed in 2.2.5.

[william.cage]

Yep, 2.2.4.158 causes the problem to return. Thanks for your help on this. I will roll back and hang tight until 2.2.5 comes out.

[william.cage]

I am curious, having gone through the debugging, is the cause (or at least the area) known?

[Sebastien]

Yes, see the following link:

16s delay between door sensor and light on (Simple Lighting)

There's a known issue w/2.2.4.158 and battery powered sensors that can cause delays, especially when the sensors have been "sleeping" for a while. A fix is coming in the next FW release, timing TBD, but we expect soon in the new year. Does the delay in the light coming on tend to go away once the automation has been triggered more than once and the sensor has been triggered? A few key posts in a thread related to this:

[william.cage]

Yep, that does the trick. I switched the driver to the Ring Alarm driver instead of the Generic Z-Wave Contact Switch and all is well with the 2.2.4.158 platform. You and I were headed the right way with drivers, but I would not have gone with the contact switch driver. I was thinking the light switch. It still doesn't quite make sense to me given the log output, but clearly smarter people than I figured it out.

Thanks for hanging in with me on this to get to a solution.

[Sebastien]

I’m glad it was fixed!

[CAL.hub]

I have the exact same thing happening, except my Z-wave sluggishness is only about ¼ of the time and long preceded 2.2.4.xxx. In my rule, to test, I added a Zigbee device and another Z-wave device: The Zigbee was always immediate and the 2nd Z-wave corresponded to the first Z-wave device (a Zooz Zen24 Z-wave Plus, but the device doesn't seem to matter) responsiveness.

I sent a support request with logs to HE and another one a week later. That was mid-December. I gave up and replaced my Z-wave switch with a Caseta.

[Sebastien]

@CAL.hub

my Z-wave sluggishness is only about ¼ of the time

That sounds like a Z-Wave mesh issue. What hub version do you have, a C-5 or a C-7? Have you checked Z-Wave details to see if there are devices with issues (or Ghost devices)?

[oldcomputerwiz]

@CAL.hub

I have the exact same thing happening, except my Z-wave sluggishness is only about ¼ of the time and long preceded 2.2.4.xxx

I had the same thing on a C5 running 2.2.3 and 2.2.4. I kept thinking it was mesh (because it sure acts like a mesh issue) but it wasn't. It was the HE generic zwave contact sensor driver.

I have quite a few goControl zwave contact sensors. As soon as I switched to a ported Smartthings driver for these sensors my zwave delays went away.

I recently ran into another user that had this issue with the goControl contact sensors too.

What type of contact sensors do you have?

[CAL.hub]

@Sebastien

That sounds like a Z-Wave mesh issue. What hub version do you have, a C-5 or a C-7? Have you checked Z-Wave details to see if there are devices with issues (or Ghost devices)?

Thanks @Sebastien. It's a C-3. I don't see any ghost Z-wave devices.

@oldcomputerwiz

I have quite a few goControl zwave contact sensors. As soon as I switched to a ported Smartthings driver for these sensors my zwave delays went away.

Interesting. No goControls. I think the only Z-wave contact sensor is an Econet garage door tilt switch. How would I diagnose this?

[Sakman]

@CAL.hub

think the only Z-wave contact sensor is an Econet garage door tilt switch. How would I diagnose this?

Is this an Ecolink garage door tilt sensor? There are a few threads with issues with the Ecolink and other battery contact sensors causing issues. You can search this forum for them. The batteries in these contact sensors can cause havoc with the mesh. The recommended temporary solution is to change the driver for the Ecolink sensor to Ring Alarm contact sensor.....Not the G2 one. There is a fix for this supposedly coming out in 2.2.5. I have one of these Ecolink sensors and I did change the driver to the Ring Alarm contact sensor without any problems. This seemed to help.

[cdikland]

@Sakman

There are a few threads with issues with the Ecolink and other battery contact sensors causing issues.

Wow, I wish I saw this post before going through hours of debugging my Zen21 switch. I came to the same conclusion. Switch good, Ecolink Sensor bad.

Zooz ZEN22 and ZEN30 stopped working for no reason