RA2 Occupancy Sensor. Why Are Easy Things So Arduous? I'm Experimenting With An Occupancy/vacancy RA2 Sensor LRF2-OCR2B-P With RA2 Choose System.I Need To Automate Entry Lights So They Turn On Robotically When Homeowner Enters The House.I Don’t Need The L

RA2 Occupancy Sensor. Why Are Easy Things So Arduous? I'm Experimenting With An Occupancy/vacancy RA2 Sensor LRF2-OCR2B-P With RA2 Choose System.I Need To Automate Entry Lights So They Turn On Robotically When Homeowner Enters The House.I Don’t Need The L

RA2 Occupancy sensor. Why are easy things so arduous? I'm experimenting with an occupancy/vacancy RA2 sensor LRF2-OCR2B-P with RA2 Choose system.I need to automate entry lights so they turn on robotically when homeowner enters the house.I don’t need the lights to automatically shut-off. Homeowner will manually resolve when/if they want to show the lights off. They've an open-plan area so entry lights also present accent and task lighting for https://splice.com/bulbcan40 kitchen area. I've thought of sophisticated alternate options resembling using a Philips Hue motion sensor which is accessible to HomeKit, but then I might have to install a Zigbee bridge for it.I've additionally thought of utilizing a dummy Lutron appliance module and setting the RA2 sensor to regulate that module only and set guidelines in HomeKit when that "dummy" module turns on to then activate the actual entry lights. Again, Rube Goldberg-ish workarounds for a quite simple thing - from the end-consumer/homeowner perspective.Only for laughs, if I improve them to a full RA2 major repeater and join bridge, would or not it's any simpler or is this limitation of the RA2 sensor still the problem?