Originally Posted by wkearney99
I seem to recall HS3 was able to track vacancy for the sensor. As in, the sensor has detected there's nothing happening after the sensor-configured amount of time, so it then fires the vacancy scene. I just looked in my HS3 setup and it does have the ability to track a device changes and becomes 'No Motion', which is the HS3-ish name for what Lutron calls Vacancy.
Honestly, Ra2's occupancy/vacancy is excellent. Why would you want to skip it?
Yes, HS3 can track motion/no motion (occupancy/vacancy). However, the RA2 sensor only sends the occupancy/vacancy notification if it is tied to a device.
I agree that the RA2 occupancy/vacancy sensors work very well. The response time is great. The problem comes when you would like to trigger events off of different time intervals, or temporarily disable the motion detector (MD). Once you set the time interval on the MD, that is the value you have to live with. Neither RA2 or HS3 can direct the sensor. And since the motion-controlled light behavior is entirely within RA2, HS3 can't change this.
For instance, I currently have the MD in the garage set to turn off the lights in 1 minute. If I happen to be in a corner of the garage that is out of range of the MD for even 1 minute, the lights go off. I would like to be able to temporarily disable this behavior. I was able to do it with HS3, but only by detecting when the lights go off and then immediately turning them back on. With a Zwave MD, the HS3 software interprets the MD signal, and the event logic can be manipulated.
Similarly, it would be nice to know within a minute or so when a room had become unoccupied. However, if you set the MD to 1 minute, then the lights go out way too quickly.