There are two settings that you can alter via the Admin Console that greatly affect how the MS-II works, "Motion Report" and "Motion Timeout".
"Motion Report" controls whether the motion sensor sends both an ON command when it detects motion and an OFF command when motion has ceased. "Motion Timeout" controls how long there must be no motion before the motion sensor decides that motion has ceased.
Out of the box, I believe the MS-II has "Motion Report" set to "ON and OFF". If you plan to use a program to turn OFF the device you're controlling with the motion sensor, then you'll want to change "Motion Report" to "ON Only"
Also out of the box, I believe that "Motion Timeout" is set to 30 seconds. This means that there must be at least 30 seconds of no motion before the motion sensor sends an OFF command. Now here's where things will get confusing. If you're going to use a program to control turning a device off, you don't want the motion sensor to send an OFF command and so you think the "Motion Timeout" doesn't matter. Unfortunately, the way Insteon implemented the motion sensor code, the "Motion Timeout" also controls the time period during which the motion sensor won't send another ON command.
At this point, an example is probably called for:
Say you have the motion sensor set to only send ON commands and you have the timeout set to 1 minute:
You walk into the room and the motion sensor sends an ON command, it also starts a one minute countdown
15 seconds later, you leave the room
15 seconds later, you reenter the room - since you're still within 1 minute countdown, the motion sensor does not send another ON command, but it does restart it's own 1 minute countdown
15 seconds later, you leave the room,
15 seconds later, you reenter the room - (see above)
So long as the motion sensor detects your movement within its timeout period, it restarts its internal timer. This means that you can go long periods without the motion sensor ever sending another ON command even though there is motion. So any program that executes a countdown based on no motion gets starved of the knowledge that motion is actually happening.
The best you can do is set the "Motion Timeout" to the shortest period allowed (10 seconds), and hope that sometime during the program countdown period (in your case 4 minutes and 25 seconds) there is at least 10 seconds of no motion so that the motion sensor countdown will finish and it will send another ON command which will restart your program countdown period.
There is an alternative, but it's often one people don't find acceptable. That is to set the motion sensor up to send both ON and OFF commands, but don't add the motion sensor as a controller in a scene to control the device. Instead use a program to both turn the device ON and OFF. This way the motion sensor does what it does best, reports both the presence as well as the absence of motion. There are at least two downsides though:
Using a program to turn ON a device after it receives an ON command from the motion sensor adds a lag to the device actually being turned on. Usually at least a second, and sometimes more
Device to device communication (i.e. motion sensor to light) is more reliable than program to device communication. For two reasons: device to device uses acknowledgements and retries, while program to device does not; and device to device only needs one command to succeed (ms to device) while program to device needs two commands to succeed (ms to program followed by program to device).
