Aeotec Motion 4 Gen 5 doesn't send "Burglary" status for at least 45 seconds???

Other Devices & Integrations Door Locks & Sensors
1

I’ve spent days on this problem and I’m finally going to let the experts think about this one.

I have a Aeotec Motion 4 Gen 5 detector set up outside a doggy door where I have a scene which turns on the outside lights when the puppy dog goes outside at night. So I have a scene that arms the motion detector at sunset and disarms it at sunrise. I have another scene that if the motion is armed, and motion is detected, it turns on the outside light.

However, 95% of the time, the outside light doesn’t go on for up to 45 seconds once motion is detected… Occasionally, it goes on within a few seconds but not very often.

Looking at the motion detector logs (included below), the motion does create a log IMMEDIATELY that the device has tripped. Then there are up to two more logs indicating another movement, then finally no movement. The next log is finally the “Burglary” status which fires off the scene to turn on the outside lights. But this happens 45 to 60 seconds AFTER initial motion is detected.

I obviously would like the motion detector to fire off the scene to turn on the lights immediately for a timed period. It just doesn’t work when it fires off 45 seconds later.

Current firmware for verEdge is 1.7.1598.

Motion detector is Aeotec 4-1 Gen 5. I have not updated firmware because only firmware I see is for NON Gen 5. I have added and deleted device many times. It’s powered by USB. The wakeup interval is set to 720, poll this node is set to 360.

Device options for the motion detector is

4, 1 byte dec, 1
5, 1 byte dec, 2
3, 2 byte dec, 30

Logs

Date/Time Description Source Type Action
Today
01/08/2016 10:57:15 AM N/A Dog Door Motion User created tr…
01/08/2016 10:57:15 AM N/A Dog Door Motion Burglary
01/08/2016 10:56:35 AM Dog Door Motion Dog Door Motion Device changed …
01/08/2016 10:56:35 AM Dog Door Motion Dog Door Motion Device changed …
01/08/2016 10:56:03 AM Dog Door Motion Dog Door Motion Device changed …

So again, It looks like the scene fires off when the status is “Burglary”, but that takes a long time from when motion is first found. Any ideas???

2

Don’t quote me on this as I never played fully with my Aeon sensor yet but is there not a parameter for multiple movements before it flags tripped when armed?

Also can you not just use the “tripped whether armed or not” function to set the lights?

Rather than using armed as a condition just use any trip as the trigger and sunset/sunrise as a condition.

3

Actually, what you said makes sense to just have it activate during any device change. And yes, it works. I will change my scene. But I don’t like making the scene from a certain hour to a certain hour. I can figure out the Luup code for night time, but I would like to add into it an hour after sunset to an hour before sunrise.

If anyone has an example of the luup code for an hour after and and hour before sunset, I would appreciate it. Otherwise, I’ll keep looking.

Thanks so much…

4

This is an example of code that run after sunset and before 10 PM. You should be able to adjust any of the local variables to accomplish your scene.

Good Luck,
db

Begin Example Code:

local end_hour = 22
local end_min = 00
local sunset_hour = os.date(“*t”, luup.sunset()).hour
local sunset_min = os.date(“*t”, luup.sunset()).min

local date_seconds = os.time({year=os.date('t’).year, month=os.date('t’).month, day=os.date('t’).day, hour=0, sec=0})
local end_seconds = date_seconds + end_hour3600 + end_min60
local start_seconds = date_seconds + sunset_hour3600 + sunset_min*60

if ( os.time() > start_seconds and os.time() < end_seconds ) then
luup.log(“debug — Executing evening scene”)
return true
else
luup.log(“debug — Skipping evening scene because it is daytime or night”)
return false
end