I'm new to Hubitat and can't seem to get my Lutron RadioRa2 sensors working.
I have a RadioRa2 main repeater and bridge with devices that are added into Hubitat without any issues. I can manually control all my Lutron switches via the Device page on Hubitat.
However, I can't seem to get my Lutron sensors to work properly. I am using multiple LRF2-OCR2B-P sensors which work fine if I program them using the RadioRa2 Essential software, but one of the main reasons I wanted to use Hubitat is to have time sensitive motion responses (which wasn't easily possible using Lutron controller alone).
I have all the sensor devices manually added into the integration as "m" devices. However, per logs, they do not seem to activate when I am moving in front of the sensors (even taking into account the sensor time-outs).
Any suggestions on how I should be setting these sensors up?
I had no luck with those sensors in my RA2/HE setup. It would only ever report when the button was pushed or motion was almost touching it. Maybe someone else here had better luck.
In the end I returned mine and replaced them with Aeotec MultiSensor 6. Plugged in I have zero issues with AM6. If you run via battery, you need to use the community driver, and set the prefs. (I use it over the stock driver anyway).
After a while I added a door contact sensor to turn the light on faster when entering. Paired with a second AM6 outside to measure luminance. On contact open or motion, lights on, if less then 100 lumens. No motion for 3 minutes, turn lights off. When above 100 lumen (sun is out) not needed. It all works great now.
First thing is the timeout on the sensor. By default it's 5 minutes, I think -- way too long for this sort of automation work. You should set them to 1 minute timeout, the minimum it supports. Instructions on how to do this are included with the sensor, and involves holding the timeout button on the back of the sensor.
Next, once that's done, you should check the logs for Lutron Telnet, on the Logs page. You can isolate for just those events. When the sensor goes active, you should see that event in the Log. This is what it looks like:
What will be different for you is the 41. That's the integration id number for the sensor. Also, you should double check those numbers against the Lutron Integration report. When the sensor goes inactive, it will report DEVICE,41,2,4
These are the basic troubleshooting steps. If you are not seeing these log entries for Lutron Telnet, then there is something wrong with how the sensor is setup in the RA2 system. If you see these but no motion is shown in the logs for the integration motion sensor, then there is something wrong with how the Lutron Integration for that device is set up.
One minute is very long compared to most other motion sensors on the market. This has certain impacts on how automations work or don't work.
For example, suppose you have an automation to turn on some lights from motion. If someone turns off the light manually, and then someone enters the motion sensing space during that one minute, the lights will not turn back on. In fact they won't turn back on until there has been no motion for a full minute; in other words, until that person has left the room completely for at least a minute. That means that turning off such a light manually can have a nasty result, with very low WAF.
Most other sensors timeout in 10 to 30 seconds, with most around 15. It's much easier to get a motion inactive event out of such a motion sensor than to get one out of a Lutron occupancy sensor. Lutron had a totally different use case in mind than home automation for these sensors.
