3 Second delay between switches

Hi!

I have an Enbrighten 47899 switch (A) wired to a light. At the bottom of the stairs I have another Enbrighten 47899 switch (B) which is not hard wired to the light or switch A. I'd like switch B to be able to control the light.

I am able to create rules to connect the switches wirelessly, but when I use switch B there is a solid 3 second delay in turning on/off the light.

For the setup I have, does this delay sound long? The hub is one floor above switch B but maybe only 30 ft linear away. Any ideas how to reduce the delay?

Thank you for any help!!

Welcome to the Hubitat forums!

Three seconds is pretty bad, I would not expect this in most cases. Maybe a half second would be more reasonable in my experience.

Screenshots (not copy/paste) of your rules so we can see how things are set up is always the best way to start. Because you are new, you won't be able to post screenshots for now. That will change after you read the forums for a bit, or post a few times or maybe staff can change this setting.

For now, it would help to describe what app you used to do this. There is Basic Rules, Simple Automations, Rule Machine, and others, so we can give better advice if we know what you are using.

Also, what is the response time from the device's settings page? (Device tab, then go into these switches) There should be on and off buttons on those pages to activate the light. Is the response time instant for the switches when using those?

The other thing that usually helps us is if you can tell us what hub firmware number you are on, (not just latest as that can change pretty quickly sometimes) The newest firmware is 2.2.9.146 as of today.

@bobbyD can we change @pumpkinhead288 permissions so they may post screenshots?

1 Like

Done!

@pumpkinhead288 welcome aboard! The latency may not be related to either switch A or B, but rather caused by other devices in your network. 3 seconds is a significant delay. Check this blog about devices that are demanding too much Z-Wave bandwidth:

2 Likes

Thank you!

I've attached screenshots from Basic Rules below.

When I use the device page, the light responds instantly to switch A (wired), but does not respond at all to B.

I just updated to the newest firmware this morning as well.

Thanks @bobbyD. I just moved into the home and other than my laptop these are the only devices connected to my network.

Screenshot 2021-11-04 at 15-35-47 When Switch basement stairs down turns on, turn on Switch - basement stairs top|690x477

I paused those rules and gave the Rule Machine a try instead. Now when I use switch B from the device screen it works perfectly! But when I physically use the switch the 3 second delay is still happening.

If this is a dimmer, it may only report the new status to the hub after it finishes ramping up or down. This can help to explain a delay.

Also the new GE dimmers like to take their sweet time to report status.

If you are using a driver with the capability to, change the exclusion key press to the alternate exclusion setting. It has an interesting side effect of making status report significantly faster.

That is definitely an option in my Enbrighten driver, and I use it a lot.

3 Likes

Typical zwave....but 3 seconds is longer than it "should" be.

I just installed your Enbrighten drivers on them!

Am I able to create an association between the switches using your driver?

edit: I just used your alternate exclusion trick and it works like a charm in regards to delay time! But if I can create an association I'd rather go that route if possible.

@pumpkinhead288 I'm a bit late to this, but try triggering on Device Turns On or Button 1 is pushed.

Device Turned On may require that the switch fully complete its transition before it reports. But central scene "Button 1 is pushed" may report immediately.