Here are the logs. Where I've inserted the arrows is where I think the lights should've turned off but they didn't. You can see that the next time they activate there's no message to say they're already activated:
What I can also see is that after the first activation, the Hue Bridge integration (built in) threw an error, and that seems to be the start of the issue:
I don't think that is related. That would only relate to parsing state changes that come in from the bridge (and would be caught up on the next poll, just like used to be the only option), not sending commands. I don't see where RL ever tries to send the "off" command, though I can't tell why from your setup.
There were some release notes for .151 concerning "And Stays" in Rule Machine, which IIRC said to click "Done" for each rule. Does that advise also apply to Room Lighting? Just spitballing here.
Can you explain what the relationship of "Landing (Hue Group" is to the other 3 lights? Are they all 4 unique lights, or are 1, 2, or 3 of the others part of "Landing (hue Group)"?
I have a feeling that answer may be related to issues with this setup.
Perhaps related, but why is "Landing - Landing S2" even in this? (it has no actions/settings)
Landing (Hue Group) is as it says a group defined in Hue consisting of 5 GU10s in ceiling downlights. It's only used when turning 'Off'
Landing S1 is a Hue scene that sets the group above to a particular level and temperature
Stair Lights is a set of 12 decking type LEDs that illuminate the individual stair risers. The PSU supplying them is switched by a Fibaro Z Wave outlet.
Landing S2 is another Hue scene that sets the group to a very dim level and warm temperature. It is only used during the 'In Bed' mode, whereas the table shown is showing settings for 'Night"
Yes that's what I'm seeing. This rule has been generally working fine but on a couple of occasions lights have not turned off and there was nothing present in the logs to show a turn off command being sent with the log entries just stopping with 'stays time over'.
@bertabcd1234 - I'm guessing I might have fouled something up somewhere but can't see it. I have other rules such as a 'Goodnight' rule that turn on the same lights; this is to put a series of lights all on rather than wait for me/my wife to trigger motion sensors. However that rule doesn't run until 10PM ish so cannot account for the issues here. It's not connected to this issue, but I'm wondering would I be better to take the overlapping lights out of my 'Goodnight' rule and instead add the 'Goodnight' switch turning on as a means to activate this RL instance? Thanks.
Ugh, I somehow totally overlooked your time-period setup (I'll blame lack of sleep - it's been a long week!)-- that readily negates whatever possible snags I was thinking of. My apologies for the red herring there.
