Aeon 4-in-1: How to make motion sensor turn on a light?

Other Devices & Integrations Door Locks & Sensors
1

How do I configure the motion sensor to turn on say, my wall outlet? Is it via trigger, or in the configuration for the motion sensor?

2

You want to create a scene that turns on your light.

Then on the trigger tab configure motion as the trigger.

3

Cool, thanks.

So if I follow this: http://docs5.mios.com/doc.php?language=1&manual=1&platform=3Pro&page=sensor_scene

The only thing that seems to confuse me is:

  • Why does it have “Turn off the light when an armed sensor is not tripped”… How does a “not tripped” trigger fire?

Is it possible to set the duration of time that the light stays on for after being tripped?

4

I guess what I am saying is, if my light is schedule to be on from 6PM - 8PM, and I have a trigger to turn the light on if it detects motion and off when it doesn’t. Which one overrides which, between the hours of 6 and 8? Or should I be handling it on a schedule to fit around the 6 - 8 thing?

5

You should try PLEG for this or use luup to cancel the scene if it is not in the window of time you want the scene active.

there are tons of examples of both the PLEG and the Luup solutions on the forum.

6

@johnes, take a look at Conditional Scene Execution for help with using Lua code in your scenes.

You may also want to check PLEG Basics to see whether that is a better solution for you.

7

Thanks! I’ll take a look… startin g slow, and will add devices as I become more comfortable. Really appreciate the help.

8

Yeah, PLEG is definitely the way to go. Thanks for pointing me in the right direction.

9

Yes the PLEG worked example from Rex B is the way to go.

Once I got around the typos I had made it works fine.

The logic takes a bit to get your head around as there are three areas to input in this case:

  • The Inputs which I have set as 3 x Triggers (Night, Motion, Light is off) to turn it on, plus another (NotMotion) to turn off after time

  • The Conditions which test the triggers, but I worked out can refer to other Conditions! Go figure (but actually makes sense - this way you can check if a Condition is met or not met meaning one’s IF / THEN / ELSE logic is more powerful). This was perhaps the biggest mindshift I needed to figure out.

  • The Actions which is where the heavy lifting is done. It undertakes various steps depending on which Conditions are fulfilled. It seems there is a 1:1 correlation between each Condition and each Action (again makes sense).

So perhaps my advice to myself is work backwards: What Actions do I want undertaken when various Conditions are met (or not met, or no longer met). Then build Conditions and Inputs which meet that making sure there are no conflicts which create an endless loop (Rabbit Season, Duck Season, Rabbit Season, Rabbit Season etc.)