Rule actions can be quite powerful, and not everything that you want to test as a condition needs to be a trigger. Rule 4.0 makes you explicitly specify your triggers. Since you're apparently familiar with earlier versions of Rule Machine, I suggest reading the 4.0 docs to see what's changed and how you can convert previous thinking to the new paradigm ("classic" conditions no longer exist in that sense, for example): [Released] Rule 4.0
For your rule, you could try something like this:
Triggers: Time is sunset OR Time is sunrise OR Mode *changes*
Actions:
IF (Time is between sunset and sunrise AND Mode is Away) THEN
On: Security Lights
ELSE
Off: Security Lights
END-IF
You can customize this exact logic to do what you want. If you're mode is Away and it changes to something else, the lights will turn off, even if it's between sunset and sunrise. If mode isn't Away at sunset, the lights won't turn on but will if it becomes away any time before sunrise. I'm not sure if that's exactly what you're looking for, so again, you can tweak it for your exact desired logic. (Simple Lighting actually might be able to handle this without RM at all, but I haven't checked these exact restrictions.)
