Since I upgraded to a Vera3 (on the latest firmware), I have noticed that sometimes the system takes an incredibly long time to start and/or execute scenes. A quick check of memory and CPU load on the Vera didn’t indicate a shortage of resources.
Normal scenes (even with a fair number of devices) seem to execute normally. There are some complex scenes that kick of a number of subscenes, each controlling a number of devices. Turning to the log, this slowdown seems to center around these complex scenes. The log indicates that the trigger is picked up promptly and the subscenes are started immediately after, following that the Z-wave commands are sent out.
At this point, the log shows that almost all Z-wave commands come back with a transmission failure, in one case even culminating in a LUA engine crash. In other cases, the log reports the Z-wave stick to be in a bad state, whatever that means. The visible result is that it sometimes takes 30 seconds before the first light is turned on, and over 2 minutes for the scene to run to completion.
This behaviour is only apparent when these complex scenes are executes, at other times the system behaves normally.
Is it possible that kicking off 4-6 subscenes all at once chokes the Z-wave command queue somehow? I am curious if anyone else has observed this behaviour. MCV support has had a look at the system but I’ve yet to hear their conclusions…
[quote=“intveltr, post:1, topic:171032”]Since I upgraded to a Vera3 (on the latest firmware), I have noticed that sometimes the system takes an incredibly long time to start and/or execute scenes. A quick check of memory and CPU load on the Vera didn’t indicate a shortage of resources.
Normal scenes (even with a fair number of devices) seem to execute normally. There are some complex scenes that kick of a number of subscenes, each controlling a number of devices. Turning to the log, this slowdown seems to center around these complex scenes. The log indicates that the trigger is picked up promptly and the subscenes are started immediately after, following that the Z-wave commands are sent out.
At this point, the log shows that almost all Z-wave commands come back with a transmission failure, in one case even culminating in a LUA engine crash. In other cases, the log reports the Z-wave stick to be in a bad state, whatever that means. The visible result is that it sometimes takes 30 seconds before the first light is turned on, and over 2 minutes for the scene to run to completion.
This behaviour is only apparent when these complex scenes are executes, at other times the system behaves normally.
Is it possible that kicking off 4-6 subscenes all at once chokes the Z-wave command queue somehow? I am curious if anyone else has observed this behaviour. MCV support has had a look at the system but I’ve yet to hear their conclusions…[/quote]
Hi intveltr
I have noticed that even running simple scenes takes from 45-120 seconds on a Vera 3. Complex scenes seem to take even longer. Any thoughts what’s causing this. The load on the Vera3 is consistently less than 20%.
I have noticed that even running simple scenes takes from 45-120 seconds on a Vera 3.
A delay of that length suggests that something is not right in your Z-Wave mesh. I have seen this happen when Vera is waiting for several battery-operated nodes to wake up. It could also happen if several devices are not responding and require transmission retries. It can definitely be caused by a rogue device that is flooding the network with packets.
In all these cases I would expect to see some evidence in LuaUPnP.log.
I just upgraded to a Vera3 with UI5, and I did have some problems with two scenes that always run at the same time - I would get 30 second delays on both. So I combined the two scenes and it works much more reliably than they did separately - the combined scene runs within a second or two.
Best Home Automation shopping experience. Shop at Ezlo!