The rules should override things because they basically just change what your previous setting was.
So, if I start with my notifications turned ON in the camera’s settings, then I set a schedule rule to turn the notifications OFF at 6pm, I’ll be able to go back into the camera’s settings after 6pm and see that the settings now say that the camera notifications are OFF. So it’s not so much that rules “override” settings, per se – it’s that the rules SET the settings. Does that make sense?
By the way, if the rule is to turn something on or off, I’d probably do that as two separate rules rather than one rule with a “duration”. So, a rule to turn it off at 6pm and a rule to turn it on at 11am. The logic is a little weird/unpredictable otherwise. For example, what happens if you manually decide to turn notifications on when they’re supposed to be off? Will it retain your new setting until the duration is over? Will it immediately switch it back off, since that’s what the schedule says? Will it stay on until it decides to randomly check in with the server, at which point the server realizes it’s supposed to be off? Will it change it if the camera or app restarts? (I actually don’t know. I haven’t tested all these scenarios in Wyze, but since it’s a weird way to write logic, I wouldn’t be surprised if any of these scenarios were true)
It’s just a weird way to write logic to me. (Durations for on/off behavior) If it’s two rules – one that turns something on at a specific time, one that turns something off at a specific time, it’s much easier to follow logically and predict the behavior.
The “duration” rules are more useful for behaviors that should be triggered every time they occur during certain timeframes but not others, for example.