Seeking clarification re Aeotec Multi-Sensor installation and use

Other Devices & Integrations Lighting & Load Control
1

While studying how to best link the Aeon Labs Aeotec Multi-sensor with a Vera 3 I’ve encountered contradictory instructions. Vera’s doc page re this sensor says to bring it to the Vera for inclusion. Elsewhere I read that you should install the sensor in its destination location, have it powered by the method it will remain in (USB or battery), and bring the Vera to it for inclusion. I believe the issue users are dealing with is that the sensor needs to know its neighboring z-wave devices to ensure proper communication with the Vera. To add to my confusion there are references online to “the overnight heal” – like it’s a common installation step, which I can only assume is because the sensor wasn’t included properly. Any comments about how to properly include it (move sensor to Vera or move Vera to sensor for inclusion, “overnight heal”, etc.)!?

My goal with the sensor is to have it detect motion in the driveway. Upon detection I want it to turn on a light if it’s dark outside. This seems like an obvious application but I can’t find docs that describe how to do it with the Aeotec sensor and a Vera. Instead, I’ve found a tutorial at Vesternet that describes how to do this with a different sensor and there they recommend having the sensor talk directly to the light switch instead of going through the Vera. Another Vesternet tutorial describes using the Aeotec sensor to control a scene, which seems to contradict their assertion that direct association is better. Mainly, though, the latter tutorial doesn’t deal with having the trigger be conditioned on the sensor’s illumination detection. More confusion. Has anyone seen docs that deal with my specific application (motion sensor detects motion which triggers switch on only if sensor says it’s also dark outside)?

Thank you.

2

Just yesterday I swapped a Schlage motion sensor for an Aeotec 4-in-1 so I have some recent experience with it (this is the second 4-in-1 I’ve installed).

As in my previous install I had to do it more than once … it appears to be a Plug-and-Play device, you have to plug it and play with it for a while before works. Anyway, make sure that you have the latest firmware, 1.18 as recall. You can get the update from their web site.

Once it installs you will have to restart Vera several times to get it to config the various sensors. But once it’s done it’s fine.

You can also find some additional config info on the forum, search for Avon 4-in-1 and Aeon multi-sensor, there is some good info on setting up reporting intervals, etc.

3

[quote=“clippermiami, post:2, topic:180796”]Just yesterday I swapped a Schlage motion sensor for an Aeotec 4-in-1 so I have some recent experience with it (this is the second 4-in-1 I’ve installed).

As in my previous install I had to do it more than once … it appears to be a Plug-and-Play device, you have to plug it and play with it for a while before works. Anyway, make sure that you have the latest firmware, 1.18 as recall. You can get the update from their web site.

Once it installs you will have to restart Vera several times to get it to config the various sensors. But once it’s done it’s fine.

You can also find some additional config info on the forum, search for Avon 4-in-1 and Aeon multi-sensor, there is some good info on setting up reporting intervals, etc.[/quote]

Thank you for replying, clippermiami. Did you include the 4-in-1 by moving it close your Vera or did you install the 4-in-1 and take the Vera to it?

4

In this particular case they were within a few feet of each other anyway.

5

I installed 3 of these without issue. All were done at the Vera and then put into their location. Other than the quirks listed all over the place here (initial inclusion and getting all devices to show properly) they have worked flawlessly for about a year. Mine are all battery powered.

6

Great questions timmy2 - did you ever get a resolution?

I’m working through the same thing at the moment, have always included units by bringing the Vera lite to the unit (should be the same for the Vera3) and have got a motion sensor turning on some lights when the light in to room drops below a certain level via some luup code - which works fine.

I then have a second scene that triggers when the motion detector stops detecting motion and with a 3 minute delayed event, switches off the lights.

Issue I am facing is once the lights are turned back off - the motion detector then wont sense motion for a period if time (haven’t tried to test exactly how long), but the typical scenario of:

  1. walk into room lights come on
  2. sit down and after x minutes lights turn off
  3. Wave hand - or stand up and walk to motion sensor doesn’t turn the lights back on

I started to look into direct association and have likely read the same articles as you and yes, I cant seem to see any way to have it include light level logic?

Is there anyone else here who has successfully implemented the this type of logic? or experienced the non-motion events I’m seeing?

Cheers,
Damian

p.s. sorry for the old thread revival :wink:

7

I have no issues with mine. Bring the Vera to the sensor for inclusion, include the sensor, then hold down the plus button on the Vera to turn it off. If it needs to heal you did not include it correctly.

You are correct that it needs to by included using the same power source that it will be using, if you switch from USB to battery for example you’ll need to exclude and re-include it.

I would recommend USB power if possible so that you can increase the reporting frequency without worrying about battery life.

8

[quote=“Harto, post:6, topic:180796”]Great questions timmy2 - did you ever get a resolution?

I’m working through the same thing at the moment, have always included units by bringing the Vera lite to the unit (should be the same for the Vera3) and have got a motion sensor turning on some lights when the light in to room drops below a certain level via some luup code - which works fine.

I then have a second scene that triggers when the motion detector stops detecting motion and with a 3 minute delayed event, switches off the lights.

Issue I am facing is once the lights are turned back off - the motion detector then wont sense motion for a period if time (haven’t tried to test exactly how long), but the typical scenario of:

  1. walk into room lights come on
  2. sit down and after x minutes lights turn off
  3. Wave hand - or stand up and walk to motion sensor doesn’t turn the lights back on

I started to look into direct association and have likely read the same articles as you and yes, I cant seem to see any way to have it include light level logic?

Is there anyone else here who has successfully implemented the this type of logic? or experienced the non-motion events I’m seeing?

Cheers,
Damian

p.s. sorry for the old thread revival ;)[/quote]

There is probably nothing wrong with the sensor. You may want to look into the available parameters of the sensor such as the motion timeout, Option 3 under the Device Options tab. Since the default motion timeout is 4 minutes and your scene turns the light off after 3 minutes you’ll have to wait another minute before you can trigger motion again. Sorry misread that, is your device wired? Maybe play with the polling intervals? The motion sensor is supposed to report instant status. I’ve not had any problems with delays between motion events.

9

[quote=“joey52685, post:8, topic:180796”][quote=“Harto, post:6, topic:180796”]Great questions timmy2 - did you ever get a resolution?

I’m working through the same thing at the moment, have always included units by bringing the Vera lite to the unit (should be the same for the Vera3) and have got a motion sensor turning on some lights when the light in to room drops below a certain level via some luup code - which works fine.

I then have a second scene that triggers when the motion detector stops detecting motion and with a 3 minute delayed event, switches off the lights.

Issue I am facing is once the lights are turned back off - the motion detector then wont sense motion for a period if time (haven’t tried to test exactly how long), but the typical scenario of:

  1. walk into room lights come on
  2. sit down and after x minutes lights turn off
  3. Wave hand - or stand up and walk to motion sensor doesn’t turn the lights back on

I started to look into direct association and have likely read the same articles as you and yes, I cant seem to see any way to have it include light level logic?

Is there anyone else here who has successfully implemented the this type of logic? or experienced the non-motion events I’m seeing?

Cheers,
Damian

p.s. sorry for the old thread revival ;)[/quote]

There is probably nothing wrong with the sensor. You may want to look into the available parameters of the sensor such as the motion timeout, Option 3 under the Device Options tab. Since the default motion timeout is 4 minutes and your scene turns the light off after 3 minutes you’ll have to wait another minute before you can trigger motion again. Sorry misread that, is your device wired? Maybe play with the polling intervals? The motion sensor is supposed to report instant status. I’ve not had any problems with delays between motion events.[/quote]

An approach I took, and not claiming success just yet… I trigger my scenes on motion detected (armed or not) only. In short, when you enter the room, the motion sensor detects, and the lights come on. The lights are only turned OFF when you leave the room, and another motion sensor (outside the room) detects motion.

I tried turning the light off after the motion sensor stops detecting motion (picture waving arms)… I tried extending the timeout, and NEVER got that to work. I tried other motion sensors; the Aeon 4-in-1 is about the best of many poor choices.

Wiring the sensor was something I did NOT try; getting an electrical connection to the sensor would just be too hard.