I'm not at my computer at the moment so I can't help you with making it work but the reason it isn't working is when the trigger is set, the condition is never met as it will never have been at 255 for 30 seconds.
From memory (if you can't get it sorted I'll have a look when I'm home) you need to set a trigger when the device has been at 255 for 30s. No conditions.
Josh
Simple Reminder
- 135 Views
- Last Post 15 September 2014
rspoto
posted this
15 September 2014
Ryan-Scott
posted this
15 September 2014
I don't know what's wrong w/ my brain, but I just can't figure this one out.
I'm trying to simply create a scene that will perform an action if the sensor is tripped for 30 seconds.
I created a scene as follows:
* Added a trigger for when the sensor changes to 255 (open).
* Added a condition for the sensor being at 255 for 30 seconds.
Once I add that condition, the action never happens. I tried removing the trigger and using just the condition, but that didn't do anything either. What am I missing?
Thanks in advance.
Set a time trigger that fires every few seconds. Keep your condition as it is and you should be set. The trigger will "fire" and check if the sensor has been at 255 for 30 seconds, and if so, it'll execute your scene.
You'll find that the timer continues to check every few seconds and will continue to execute; to prevent this, create a virtual device that gets turned on as part of your scene. Add a 2nd condition that checks to make sure the virtual device is off. At this point, all you need is something that will reset your virtual device - you could have it go auto-off after 1-2 minutes.
tnamey
posted this
15 September 2014
Unfortunately there isn't a trigger option for a device with a specific time frame. You could have a time trigger that goes off every 30 seconds and have a condition that the motion sensor needs to have been on for 30 seconds.
Another issue you will run into is how often the sensor itself resets. The Aeon Multi sensors I use have a default motion reset of like 10-12 minutes. I always lower this to like 4-5 minutes but that does eat up more battery.
Basically, I not sure that when your sensor goes off that it won't ever be for less then 30 seconds unless you reprogram the sensor parameters to reset every 29 seconds.
monkey-magic
posted this
15 September 2014
I'm not at my computer at the moment so I can't help you with making it work but the reason it isn't working is when the trigger is set, the condition is never met as it will never have been at 255 for 30 seconds.
From memory (if you can't get it sorted I'll have a look when I'm home) you need to set a trigger when the device has been at 255 for 30s. No conditions.
Josh
