I hear you, but there are several zwave wall switches in the garage, and the relay still has 100kbps going directly to the hub. I might try exclude/include/reinstall app.
I'm just trying to eliminate this as a factor, that @bcopeland could confirm.
Even though I didn’t believe I was having issues, I went ahead and updated the two contact sensors I had just to see. Within 24 hours most of the routing irregularities that I was observing have disappeared.
1 Like
Just to confirm - you're referring to Econlink sensors that you changed the driver on?
My ecolink 2.5 contact sensor on my dev hub continues to respond in <1s every time - still using the in-box generic driver. 
Still a bit of a mystery to me why it works for some any not others. Unless, like Bryan mentioned, since mine have been paired for a while they never got the new battery updates scheduled/setup.
Given @thebearmay's experience, maybe even w/out issues w/the sensor responding, you'd have improved overall routing using the Ring driver?
There is also the possibity that you are just special. I hear your mom thinks so. 
1 Like
Nah, my routes are all great on mt dev hub. I don't think there is much opportunity there.
I don't think I'm special, I think it is all to do with when devices were paired/config last hit versus the en masse driver changes for battery updates.
1 Like
Correct. I had two that were on the edge of the mesh and not super critical so didn't really worry about what they were doing.
1 Like
@bcopeland I think this issue may be what is happening with my z-wave plus shades using the generic Z-Wave Shade driver. In the morning, after the blinds have not been opened or closed for the night, the blinds usually fail to open. The device page shows that the blind is open, but physically it is still closed. Using the dashboard, if I close them then wait a few minutes, then open them again, they do respond and physically open.
These shades are on my C7 hub and are battery powered.
It affects a lot of battery devices. I think has a way to search through all the drivers to find the code.
My garage doors with the Ecolink tilt sensors have been behaving of late. With the snow here, I hadn't used my car for a day, and so tonight, after driving around looking at Christmas lights, it failed to open upon our arrival. I have it on the Ring driver, which has been working great for the Ecolink contacts. I'm thinking (hoping) it could be just different enough where a new driver would do the trick.
Was it on the ring driver when it stopped working?
Alas, yes. I had been 7 for 7 (good) before today.
Per Pushover, the last time I arrived in the garage was yesterday at 12:06PM. The failed open was today at 7:05PM. So, a resting duration of 31 hours (I don't believe the door was opened-I looked at the past log for the tilt sensor, but it doesn't go that far back in time).
Any other choices if the Ring contact driver does not work. I have some older GoControl contact sensors that exhibit this very behavior described here (I am on 2.2.4.158). I tried switching over to the Ring driver but that does not work for these (it does not update contact state).
Skipped over most posts, but thought I would chime in with my experience with Ecolink devices.
-
I have an Ecolink PIR-ZWAVE2 which is very snappy and 100% reliable
-
I have a Ecolink D/W ZWAVE2 sensor which is connected to a commercial alarm contacts on my garage door via the external contacts. Again a very quick to respond device and 100% reliable.
-
Another Ecolink D/W ZWAVE2 is using the external contact with a alarm system magnet contact for a gate alarm. I use the alarm system magnet assembly to get the wide gap I can't seem to get from Zwave or Zigbee standard devices.
-
I had a Ecolink Garage Door Tilt sensor which gave me a lot of grief and I could never seem to get it working right.
For the most part I like Ecolink, but I never find them at a great price and so most of my DW sensors are Iris.
These are on a C4 with platform 2.2.4.158
I'm not aware of any other suggestion other than changing to the Ring driver...
2.2.5 is supposed to resolve these issues, so hopefully that will arrive soon.
1 Like
Ran into something similar except I was also seeing the delays going all the way back to version 2.2.3. I have been chasing this issue for months. Try this driver for your GoControl switches. It seemed to get rid of the delays the generic driver was causing in my system. MAKE SURE TO SAVE PREFERENCES after switching to this driver as there is no CONFIGURE button. You may also have to cycle your contacts a couple times too.
1 Like
Thanks for sharing that driver!
I did end up for now using the old community driver (Hubitat/GoControl Contact Sensor at master · michaelahess/Hubitat · GitHub) with the modification of disabling battery reports for now. I am still monitoring but things are promising.
That's the driver I am currently using too, with the same section commented out. The WADWAZ driver is nice in that it will let you use the external contact. The driver we are using never had the external contact child ported over (that I'm aware of).
@fpa1974, Has this driver solved your slow downs?
Is it possible to get this thread renamed (again) to reflect the now well understood scope that this issue is beyond Ecolink sensors?
