More unwanted scene delays (not related to state updates from devices)

Community Playground General Discussions
1

As stated in the other thread, I too have issues sometimes with delays in scene execution. The other thread centers around issues with state updates from scene controllers, so I started a new one since my problem appears to be a different one. At first I suspected the scene controller, memory issues, or perhaps a plugin loading down Vera causing the delay. But lately I noticed something that eliminates these are causes.

I’ve replaced a bunch of lights in my living room with Philips Hue bulbs, controlled via the Vera plugin for these lights. Since then I notice the following: when I run a scene affecting all the lights, the Hue lamps react almost instantly, while the Z-wave controlled lights take much longer to respond, sometimes up to a minute. So the problem isn’t Vera’s engine or the scene controller; it’s something in the interaction between Vera and the Z-wave network. What could be causing this, and what would be a good way to diagnose this?

2

I noticed the same kind of issue. My prowl message (or push-email) arrives quickly while my z-wave devices may take up to several minutes to react.

In the logs that I have posted in my thread I can see what is going on: The trigger arrives quickly, then my prowl message is sent and received promptly. But before the scene that switches some z-wave switches is executed the triggering device is polled again (no idea why, it has triggered the scene already and is not involved in the scene any further). This sensor does react to the polling although sometime it also fails. It is polled many times over a period of minutes and then suddenly the scene executes.

You can see this issue in the attached log between line 56 and 214.

This issue clearly has nothing to do with slow state updates but with failing z-wave communication. I hope that someone that understands these logs better than I do wants to have a look and identify the problem.

It would be interesting to see whether your problem is also caused in a similar way. Did you make log readings of the issue? Maybe you could also use a push-email or prowl message as notification that the trigger has arrived.