wkearney99 said:For example, the front porch light is on a motion sensor and for a majority of the time that's a great feature. But as warmer weather arrives it's nice to be out on the porch swing. This, of course, would be a great time for an over-ride. Trouble is, how do you structure this to get what you want, without unintended side-effects. Or handle motion sensors for outside lights when you have a party. A party is easy enough, if your rules are structured to take it into account. As in, I've detected motion, but party mode is set, so nevermind. This works OK for a party, but seems a bit tedious when you just want to sit on the porch for a while and not have the lights keep coming on. What's the right "user interface" for this? Using the wall switch for this runs dangerously close to the very annoying way old-school motion sensors would work; making you turn it on-off-on in some magic-dance-sequence to put them into a mode. But the sensor is close enough to the doors that it triggers when they're opened. Now, should it? Or should it err on the side of restraint and not turn on the lights unless motion outside was detected first? Ok, so instead of automatically getting lights when you go out, you have to press the button first. But how long should it wait before resetting it's motion detection? Once you're out there and the door is closed, how long should it wait before resuming a normal 'outside motion triggers lights' mode?
I think this is the sort of stuff that can be done if you capture enough data. Like you might not always sit out on the porch, but when you do it's normally between 70 and 75 degrees, after 8PM, not raining, and you're inside by 10PM. Or is a Tuesday. Or whatever. Obviously it won't be perfect, but if you know your conditionals, then it's not too difficult to program them into your controller.
I don't think it would be 100%, but 80/85 wouldn't be that much of a stretch.