Rules Engine triggers scene - very unreliable

I have a scene to turn on all my outside lights. I use a rule in the Rule Machine to trigger the scene at dusk. My first attempt was to trigger the lights in the rule itself. I did not have the greatest outcomes there, even when putting in short delays. I then read about putting a scene together and then triggering the scene. I did that, it was better, but still some lights stayed off. I noticed that the state of the lights was not always correct, so it didn't turn on lights it thought was on.

My latest rule polls all the lights and then activates the scene. At night another rule triggers the Outside Lights Off scene.

The first shot shows the log from the scene. You can see the scene logged on and off.

Note that after the Scene is logged on, I look at the Groups & Scene menu and see that both the Outside Lights on and Outside Lights off scene are "On"

If I click into the scene, it shows the Scene is in fact not set. Why does the menu before say it is on?

After I click the Activate Scene button, the lights come on.

Now the Groups & Scene menu shows the scenes correctly.

I have a C-8 Pro running 2.3.9.201

It is rarely working this week. I need to constantly manually trigger the scene.

I'd assume my issues are devices/network, but the fact the system shows both scene's "on" is making me think otherwise.

Any ideas?

See most post earlier this week. Room Lighting Reliability Issue Resolved

Although it references room lighting really any task that triggers a lot of activity at the same time will run into this issue. Bottom line, try staggering them by a few seconds.

what protocol are all these devices?
If you could PM me your HUB ID I can have a look at your engineering logs...

2 Likes

Hi. All Zwave devices. I have one zigbee device on the hub, not part of the scene.

Regarding the spacing out the commands, I initially had it as a rule only and put delays in. Also, when i click activate scene, everything comes on right away. Scene has 5 or 6 devices in it.

I'm sure its not related but i put a delay on all devices in groups - I've got 17 groups and I set a larger value the more devices are in the group. that stopped my problematic on/off's a long time ago. Maybe others might report doing this as well.

I picked up on the delay a while back from a previous thread. I have 50ms delay configured for the group. It's only 6 devices. Shouldn't be a big deal.

Quick update... I changed the setting on the scene to send commands regardless of previous state. Turned off the efficiency setting.

Thought it had an impact, but only helped with one day. Back to same issues.

Will try creating a new scene.