I've got an install where an LRF2-OWLB will unexpected sense and trigger the occupied setting. Doesn't happen with any kind of predictability and isn't repeatable.
I happened to run across Application Note 497:
I have tried a different sensor and the problem recurred. So it wasn't that particular sensor, but it was the same model. There is 2.4ghz equipment in the room. It's a wiring closet, so it's not like the gear can be moved! That and the sensor's location is pretty much the only option to get the kind of triggering desired.Quote
Anyone else run into this? Is there any kind of way to determine what tripped the sensor if this kind of interference was involved?