I vote in favour of a rule parameter such as "If time is more than x, and less than y" do the rest of the rule. This might be difficult, 'cause as I understand it right now, your Twine actually doesn't "know" what the time is, and so would consume extra power getting the time from Twine central or a web time server regularly. Unless there is a hidden on-board clock that they didn't tell us about.
Thinking about this some more, I could see a use for rules such as "If Twine is moved within 3 minutes of magnetic switch opening, do nothing, else send email or SMS" and variations on same. If away, you could then tell others in your household that upon entry they move the Twine, flip it over, or whatever, and if that doesn't happen, you get an intruder alarm. While the present rules interface is nice an simple, perhaps making available a "rule building language" that allows for flexibility by using BASIC like statements involving Twine variables and logical operations to cause actions.
Answers
Using locale, you could do "at night" or "during the day" time restrictions.
If away, you could then tell others in your household that upon entry they move the Twine, flip it over, or whatever, and if that doesn't happen, you get an intruder alarm.
While the present rules interface is nice an simple, perhaps making available a "rule building language" that allows for flexibility by using BASIC like statements involving Twine variables and logical operations to cause actions.