The Problem
Automating lighting in a small room using Z-Wave is fairly easy and can be done by associating the Z-Wave motion sensor directly with the Z-Wave light switch, and then configuring the motion timeout command to turn the light off after an interval of your choice. Alternately (and for less money), you can purchase non-Z-Wave wall switches with motion sensors built into them at your local home improvement store. These sensor/switches are often installed in bathrooms.
However, automating lighting in larger areas usually requires the use of multiple motion sensors for best coverage. In these situations, it is no longer desirable to associate the sensors directly with the switch as this will generate multiple "on" and "off" commands from each sensor as people move about the area. You'll need to use HomeSeer to manage this!
Logic:
Solution
Event #1: Do Things When Motion is Sensed by Either Sensor
IF Motion Sensor 1 changes and becomes Motion
OR IF Motion Sensor 2 Changes and becomes Motion
THEN Set Master Motion Device to On
THEN Start Master Motion Timer
Event #2: Turn Living Room Lights On When Master Motion Device Changes to On
If Master Motion Device changes and becomes On
THEN Set Living Room Lights On
Event #3: Do Things When No Motion is Sensed for 10 Minutes
IF Master Motion Timer is more thank 10m, 0s
AND IF Master Motion Device has a value equal to On
THEN Set Master Motion Device to Off
THEN Set Living Room Lights to Off
THEN Stop Master Motion Timer
note: Event #1 could be changed to turn the living room lights on directly. However, this will lead to sending redundant "On" commands to the wall switch adding unneccessary Z-Wave traffic to the network. However, sending redundant "On" commands to a virtual device is harmless. Event #2 provides the necessary buffer by only sending a Z-Wave "On" command when the virtual device CHANGES and becomes On.
Automating lighting in a small room using Z-Wave is fairly easy and can be done by associating the Z-Wave motion sensor directly with the Z-Wave light switch, and then configuring the motion timeout command to turn the light off after an interval of your choice. Alternately (and for less money), you can purchase non-Z-Wave wall switches with motion sensors built into them at your local home improvement store. These sensor/switches are often installed in bathrooms.
However, automating lighting in larger areas usually requires the use of multiple motion sensors for best coverage. In these situations, it is no longer desirable to associate the sensors directly with the switch as this will generate multiple "on" and "off" commands from each sensor as people move about the area. You'll need to use HomeSeer to manage this!
Logic:
- Turn light on when motion is sensed by any motion sensor
- Turn light off when no motion has been sensed by any motion sensor for [interval of your choice]
Solution
- Create a HomeSeer Virtual Device and name it "Master Motion Device" (or something similar)
- Create a Timer and name it "Master Motion Timer"
- Create The Following 3 Events:
Event #1: Do Things When Motion is Sensed by Either Sensor
IF Motion Sensor 1 changes and becomes Motion
OR IF Motion Sensor 2 Changes and becomes Motion
THEN Set Master Motion Device to On
THEN Start Master Motion Timer
Event #2: Turn Living Room Lights On When Master Motion Device Changes to On
If Master Motion Device changes and becomes On
THEN Set Living Room Lights On
Event #3: Do Things When No Motion is Sensed for 10 Minutes
IF Master Motion Timer is more thank 10m, 0s
AND IF Master Motion Device has a value equal to On
THEN Set Master Motion Device to Off
THEN Set Living Room Lights to Off
THEN Stop Master Motion Timer
note: Event #1 could be changed to turn the living room lights on directly. However, this will lead to sending redundant "On" commands to the wall switch adding unneccessary Z-Wave traffic to the network. However, sending redundant "On" commands to a virtual device is harmless. Event #2 provides the necessary buffer by only sending a Z-Wave "On" command when the virtual device CHANGES and becomes On.
Comment