I found out the hard way that you can only have 3 decisions (I think) in a given macro. Notice a time window takes two.
Never heistate to create a another macro. Many (if not most) macro failures are because the creator tries to cram too much into one macro... instead of using two or three macros.
You may what to create a timer macro that turns on a (dummy, ghost, or) fake module (ON at 10pm OFF at 4AM). The module will need to be on the "monitored" House code. The monitored House Code is the one house (letter) code selected for the interface to "remember" the status of the modules.
Then you could use a simple conditional macro with the condition being that the assigned fake monitored module is also ON.
The "tricky part" to wrap your head around... is the sensor now becomes nothing more than a trigger. Meaning the sensor will need to be set to a code different from the light that it is turning ON.
It will look something like this:
- Timer macros turns ON and OFF M1 (monitored house code #1)
- Motion sensor set to A1 sends trigger A1 for motion
- Light is set to L1
- Trigger A1 causes macro to look for condition (is M1 ON) if M1 is ON it turns on light L1
And.... of course everything turned on... must also be turned off. This may be as simple as a 5 minute delay built into the conditional macro... that delays for 5 minutes then turns L1 OFF.