joemurrayaz wrote:Why is there a one-minute delay on the motion sensor?
The 1 minute delay is the factory default. Unfortunately, the only way to change it is by sending it an INSTEON Extended Data Command. Extra unfortunate is the fact that the PowerLinc 2414U cannot send Extended Data Commands. The PowerLinc PLM can, but Indigo doesn't support the PLM yet. It is on our ToDo list, however. I tried to talk SmartLabs into adding a non-Extended command to change those settings, but they didn't have time to do it.
Changing the jumper so that the detector does
not send the OFF command makes it pretty useless for Indigo usage. In that scenario you'll get the initial ON command, but then if motion continues at intervals less than 1 minute you won't ever receive additional ON commands. So from Indigo's perspective there is no way to tell the difference between having 1 motion event and having infinite motion events if they are spaced less than 1 minute apart.
So in an example where you want Indigo turn ON a Device when motion is detected, then turn it OFF 15 minutes later I would:
- Make sure the motion sensor's jumper is in the default position so that OFF commands are sent.
- Create a Trigger Action that on motion sensor ON turns on the other module. Add another action as well that Executes this embedded AppleScript:
- Code: Select all
remove delayed actions for device "remote device name here"
- Create another Trigger Action that on motion sensor OFF turns off the other module, and use the Delay by 15 minutes option in the action panel.
I think that will work, although I haven't tested it.
There are other approaches to solve the problem as well, such as using an Indigo Variable or the Enable/Disable Trigger action types. Looks like we probably need to build in some additional logic to Indigo to handle the delayed auto-off scenario in these cases, but in the mean time there are workarounds.