Aeon Labs 4 in 1 Multi Sensor False trigger fix!

This is the first coding I have done with MIOS, so this may be a bit sloppy (I’ve trimmed stuff down a bit from my previous attempt earlier if you saw that).

But here’s the idea.

  1. Set the motion sensor timeout to a much faster setting than usual (i.e. 1 second if you really want to eat the batteries lol). Unfortunately this is key to be able to detect a repeat movement.
  2. Figure out how far apart your false triggers are. Mine seems to be once or twice a day.
  3. Set the DELAY variable in the lua code to something that is much shorter than the time between your false triggers. For example, if your false triggers happened every 12 hours, don’t set it to 11 hours. If you walked by the motion detector at the 10th hour, the DELAY would reset to another 11 hours from then, so at the 12th hour your false trigger would run the scene! Set it to something like 20 or 30 seconds. Or maybe a little longer would be ok. Just remember, the longer you set the DELAY variable, the more likely you will catch the false trigger within that time frame and it will run the scene. Also remember, if you set the DELAY too short, the multisensor may not have time to reset it self to detect a second motion from the same instance of the person walking by, and therefore it will not run the scene.
  4. Use the code below in the scene you want your multisensor to trigger and fill in the variables at the top with your own numbers (SENSOR is your multisensor motion sensor device number and DELAY is the delay we discussed above in statement 3).

[code]local SENSOR = 51
local DELAY = 20

local SS_SID = “urn:micasaverde-com:serviceId:SecuritySensor1”

local lastTrip = luup.variable_get( SS_SID, “LastTrip”, SENSOR)

if (os.time() - lastTrip >= DELAY) then

return false

else

return true

end[/code]

Well, after testing this for a day, it definitely fixes the false triggers, and for my purposes (using them as a security motion sensors at night outside the house) it works ok. But they just aren’t responsive enough in general it seems for indoor use for triggering lights, etc… overall very disappointed with these.

Hi all.
False triggers are in conjunction with the wakeup time. Wakeup = 5 minutes then false trigger every 5 minutes. Wakeup = 12 hours then false trigger every 12 hours.
I’ve done several tries for this.
Bye.

Thanks to the many who’ve posted on the false triggers with the 4 in 1. As best I can tell, there isn’t a fix. Mine is indoors and gives a false trigger every few hours. Just for laughs, I took it down, put it in a drawer, and I’m still getting motion alerts every few hours, even when the house is void of occupants.

I did the firmware update before installing it.

Is the correct solution to just return it? It appears there is no hope for success.

I am in the same boat. Even when fully covered I get occasional false motion alarms. They seem to be related to the configured wake up time, but happen multiple times a day.
Very disappointing for such a rather expensive sensor. I’ll have to try to get it replaced under warranty, since my return period has passed.

[quote=“mikewop, post:5, topic:175872”]I am in the same boat. Even when fully covered I get occasional false motion alarms. They seem to be related to the configured wake up time, but happen multiple times a day.
Very disappointing for such a rather expensive sensor. I’ll have to try to get it replaced under warranty, since my return period has passed.[/quote]

I do not think a replacement will help you here. There are many reports of false triggers and some solutions to limit them. But in the end, I think you will still have these issues.

  • Garrett

Removing the batteries before putting it in a drawer will fix the false triggers problem :wink:

Could you use some logic that basically gets a second poll if there is motion detected? I haven’t worked with the logic for this one, wondering if this is possible.

Psuedocode:

If (motion detected) Do Nothing Check for motion Again in 1 second If (no motion on this second check) Ignore everything and pretend nothing happened else Assume there is actual motion Initiate Trigger

That way if the trigger is set because of a wakeup issue, it won’t cause anything to happen. The recheck could be set to as low a value as possible.

Great I have this issue and can confirm it is related to wake up time. Not every 28 minutes but always a multiple of 28. Setting the time to 999999 will reduce the triggers. Can I disable it with 0?

Just saw this thread.

A better fix for this is here: http://forum.micasaverde.com/index.php/topic,3831.msg149761.html#msg149761

Note that any motion detection will still be reported in a timely fashion.

I guess it is nice to see workarounds to trick your vera into overlooking false trips, but the device should not do this.

I now (finally) have three working on battery power. None of them false fire. I also have other types of motion sensors, none of them false fire.