The easy answer is "Use Motion Lighting instead," which has this feature built-in. 
Before digging into Rule 4.0, I'd recommend taking a look at the documentation, which has an example nearly identical to the one provided to you above, including showing how to use the new "cancel" feature correctly in this situation.
But to keep it in RM, you have a couple options depending on how you actually want to do this:
- Check if any/all (depending on what you want) of the lights are on first; if so, don't turn them on in the rule (and also not off if that is also something you want)--this looks about like what you did in 3.0 and could be handled with an extra condition in your
IFin 4.0 - If you want the rule to not change level after you press some "on" button until you press some "off" button, create another rule (Button Device trigger would give you a Button Controller-type UI and may work well here) to set Private Boolean true on this rule when that on button is pressed and false when the off button is pressed, then don't have this rule turn on (or off if that's also what you want) these lights as long as that boolean is true (you could probably add it as another trigger here too with little extra damage, but I don't see the point of trying cram everything into one rule)
- something more creative you can probably think of on your own but I can't since you know better how you actually use these lights and switches