motion sensor, some questions

hi everybody,
at the moment i’m using x10 and i’m running a small NSLU2 with heyu and domus.link.
i have two motion sensors which control one light (motion sensors are on the left and right side of a hallway); the system is flexibel - i can switch the system, so that the motion sensors are ignored and the light stays on or off (i can also control this), or the motion sensors control the light and a timer runs everytime a motion is detected.
so i have 3 situations: 1. motion sensors ignored and light on, 2. motion sensors ignored and light off, 3. motion sensor control the light

is it possible to configure micasa in the same way?

regards
raimund

Hi Raisch,

I haven’t tried that yet so I don’t have an answer for you but I too have a similar question that hopefully someone can answer.

The scenario that I’d like to setup is as follows:

I have a hallway with two 3-in-1 motion sensors at either end and I want to know if VERA can determine the direction a person is walking in. Example (see attachment below):

A - Sensor (in Room B)
B - Room B (just outside Sensor C)
C - First Sensor in hallway (outside room B)
D - Second Sensor in hallway (outside room E)
E - Room E (just outside Sensor D)
F - Sensor in Room E

If Sensor C detects motion first then Sensor D right after it, turn off light in Room B (only if their isn’t any motion in the room from Sensor A) and turn on light in room E (only if the ambient light from Sensor F is below a certain level.

Then… you can reverse that scenario for walking in the other direction.

Can that be done with VERA ???

[quote=“raisch, post:1, topic:164348”]hi everybody,
at the moment i’m using x10 and i’m running a small NSLU2 with heyu and domus.link.
i have two motion sensors which control one light (motion sensors are on the left and right side of a hallway); the system is flexibel - i can switch the system, so that the motion sensors are ignored and the light stays on or off (i can also control this), or the motion sensors control the light and a timer runs everytime a motion is detected.
so i have 3 situations: 1. motion sensors ignored and light on, 2. motion sensors ignored and light off, 3. motion sensor control the light

is it possible to configure micasa in the same way?

regards
raimund[/quote]

For the moment Vera doesn’t support X10, but your scenarios can be easily implemented in Vera using Zwave technology.
If the sensors are armed they will control the light, else they won’t. You can set the light to be turned on and after a time off and a lot more.

[quote=“Kozanator, post:2, topic:164348”]Hi Raisch,

I haven’t tried that yet so I don’t have an answer for you but I too have a similar question that hopefully someone can answer.

The scenario that I’d like to setup is as follows:

I have a hallway with two 3-in-1 motion sensors at either end and I want to know if VERA can determine the direction a person is walking in. Example (see attachment below):

A - Sensor (in Room B)
B - Room B (just outside Sensor C)
C - First Sensor in hallway (outside room B)
D - Second Sensor in hallway (outside room E)
E - Room E (just outside Sensor D)
F - Sensor in Room E

If Sensor C detects motion first then Sensor D right after it, turn off light in Room B (only if their isn’t any motion in the room from Sensor A) and turn on light in room E (only if the ambient light from Sensor F is below a certain level.

Then… you can reverse that scenario for walking in the other direction.

Can that be done with VERA ???[/quote]

By default Vera doesn’t alow creating scenes with complex events ( if sensor x and then sensor y ), but this can be achieved creating multiple scenes with events.

Scene 1/2 - Event 1/2 - If Sensor A/F - tripped → turn on Light B/E and disarm sensor C/D
Scene 2/3 - Event 2/3 - If Armed Sensor C/D - tripped → turn on Light B/E and disarm sensor C/D
Scene 4/5 - Event 4/5 - If Sensor C/D - tripped → arm sensor D/C

[quote=“cj, post:4, topic:164348”]By default Vera doesn’t alow creating scenes with complex events ( if sensor x and then sensor y ), but this can be achieved creating multiple scenes with events.

Scene 1/2 - Event 1/2 - If Sensor A/F - tripped → turn on Light B/E and disarm sensor C/D
Scene 2/3 - Event 2/3 - If Armed Sensor C/D - tripped → turn on Light B/E and disarm sensor C/D
Scene 4/5 - Event 4/5 - If Sensor C/D - tripped → arm sensor D/C[/quote]

Thanks cj,

I’m going to have to save this post and refer back to it when I have the rest of my equipment to make this scenario work. I look forward to trying it out.

Thanks for the post, I’ve got a 3-in-1 Motion sensor from ExpressControls and have properly paired it with Vera and the Z-wave system

Here are my questions/Problems:

  1. I have the sensor pointed at the door, and have added a global scene when the Motion sensor is TRIGGERED to turn on an intermatic light switch. The sensor is armed and I can see temp and brightness. I lowered the polling time to 360 so I can see the light levels and temp at a more recent reading than the default

No matter what, I can’t get the “Motion” Scene I put in to trip the light. Yet, I hit the GO button on the scene and the light goes right on. I’ve also put the 3-in-1 sensor in TEST mode and made sure that the LED lights up when testing motion. It seems to be detecting motion properly, any idea why it’s not working?

Question: Let’s say I get this working, now I want to tweak it so the light only stays on for 5 min or less. Then once that works, I want to add a time based rule, so in the spring/summer, I want the motion sensor to trigger the light ONLY between 8pm and 7AM. In the Fall/Winter, I want it to turn on from 4PM to 6AM only. Can this be done?

Default pooling interval it’s 10 seconds for a device, but note that if you have multiple devices could take a while until it’s pooled again.( http://wiki.micasaverde.com/index.php/Polling_Settings )

  • check that your motion sensor it’s working: has the green cog
  • when you trip the sensor you get a message from it in the zwave logs
  • try bringing the sensor closer to vera ( note that zwave it’s a mesh network and if you change the network topology you need to run a heal network for al the devices to re-learn their neighbors )

In order to archive what you want you need to create several scenes:

  1. Motion_Scene → add event When Armed Sensor tripped → Add command light - turn on - after 5 min - turn off
  2. Spring/Summer_Arm_Sensor_Scene → add timer → at 8pm - Command : arm sensor
  3. Sprin/Summer_Disarm_Sensor_Scene-> add time → at 6am - Command bypass sensor

Cj what does polling have to do with a sensor. when the sensor is tripped it should be quick .

as far as light and temp the quicker you wake the device the quicker the battery will drain.

won’t polling the Muti-sensor just get fails. The motion sensor will only wake when tripped or timed to.

The sensors are polled only when they issues a ‘wakeup’. At that time we get the current light/temperature. Motion causes the sensor to send a notification so you don’t need to wait for a poll to get motion; only light/temp.

that is basically what I said…
Also battery devices are not repeaters.