Enable Optimization is off by default (I'll try turning this on)
No ghost node
The 3 outlets are all GE Z-Wave Plus outlets. The one that didn't turn off last night is a brand new device (3 weeks ago) yet the log says it was turned off when the mode changed, when in fact the outlet didn't actually turn off
You may be better off using something other than mode to trigger your lighting events.
For something like outdoor Christmas lights, I would trigger based on Sunset time.; you can a always adjust a few minutes before or after sunset as desired.
If you want the lights to stay on all night, you can use sunrise time to turn them off. If you want to turn them off at a specific time, like your normal bedtime, you can pick a specific time.
You can also choose to have the light stay on for a fixed time such as 8-10 hours and then turn off.
I'm going to throw out some half baked suggestions, and maybe it'll trigger some corrections from more knowledgeable folks.
First thought is that there are too many things happening in your mesh at the mode changes and it's getting overwhelmed and messages are getting lost.
I've got two "sets" of 3 devices that all act in unison. I've got 3 z-wave outlets that turn Meural Canvases on/off based on motion, and 3 z-wave Somfy blinds (x2 actually, as each is a double roller blind).
The outlets are not a group, so they're written into each rule as an individual device. Despite being less than 8ft away from the hub, I occasionally see that one has failed to come on.
The Blinds are in Groups, one for the 3 blackout rollers, and one for the 3 sheer shades. I will occasionally see that one of the blinds has failed to change position with the other two, but, it gets corrected within a few minutes. I suspect that this is because they're part of a group.
If there are a bunch of things happening on mode changes, you could try adding a delay to some of the other devices to lessen the load on your mesh. Or, although I haven't done it myself, I have seen others talking about adding an additional command that circles back after a certain period of time to double check that everything is set as it should be.
I could be wrong, and if I am, hopefully someone will correct me. My knowledge of HE pales in comparison to others in these forums.
I had a similar issue with turning off all the lights when we both leave. Some of the lights did not turn off, but repeating the command did turn them off.
You might try changing from a Simple Automation to a Rule and adding a delay of a few seconds between each command.
I could not find a way to add a delay in a simple automation.
In my case, moving off of mode change in favor of on at sunset and off at 10:00PM AND/OR enabling optimization, all lights turned off last night for the first time in a week
Agree with @TomG, I have had lots of issues with basic rules and simple automation not turning off all lights so I generally use RM but feel RM is very heavy for these simple things.
Well, apparently still not working correctly... 2 of the 3 outlets say they didn't get turned on tonight yet they were actually on... over the past couple of days, 1 or more don't actually turn on
The log show the Simple Automation ran at Sunset tonight, only 1 device log shows it was turned on, the other 2 do not show any log entry yet all 3 were turned on, what a mess
I created a simple RM Rule, ran it manually and all turned on, all logs reflect... I'll know more in a few days if things are better
For what it's worth, I have terrible luck with Basic Rule and Simple Automations doing what they are supposed to do... If they work, great, if not I usually move to RM
