I am having some issues with my occupancy sensor + Inclusive + Lutron Connect.
The first issue is that whatever vacancy delay I set in Inclusive gets tacked on to whatever the manually-programmed delay on the sensor is. So if I have the delay on the sensor set to five minutes and the delay in the software set to 30 minutes, the lights don't turn off after 30 minutes but after 35 minutes. The situation is the same if I reverse the times. If Inclusive is set to five minutes and the delay on the sensor is 30 minutes then the lights stay on for 35 minutes.
Is this stacking of delays how it's supposed to work? I suspect that this is just how it works but not necessarily how it is intended to work because it doesn't make any sense to me. When you're setting up delays in Inclusive you are flying totally blind unless you personally set the delay of every single sensor. Why on earth is RR2 paying any intention to the delay set on the sensor?
The next issue I have is the status of lights in the Lutron Connect app, and this issue is more serious. When the lights in the room come on Lutron Connect shows that the lights are on as expected but Lutron Connect relies on the vacancy sensor to tell it when the lights are off. In both examples above the lights stay on for 35 minutes but LC will show that the lights have turned off after five minutes (first example) or after 30 minutes (second example).
Here is why this is a major problem. Due to the stacking of delays, it only makes sense to set the delay on the sensor to one minute. That way the actual delay for the lights to turn off is one minute more than what you set in Inclusive. So if Inclusive is set to 120 minutes the lights actually turn off after 121 minutes. But the app will always show that the lights turned off after one minute even if they are on for two more hours. This is how I would expect some cheap, poorly designed, off-brand Chinese junk to work. Someone please tell me that this is user error and I am doing something wrong!