I have recently added a RA2 Main Repeater to my Hubitat in addition to my Caseta Pro Hub. (I changed the Pico and Motion sensor frequencies on the RA2 Main Repeater for better performance so it doesn't take up the frequency my caseta pro hub is using) I have migrated all my Picos to the Ra2 Main Repeater and everything is working well using Picos to control my Caseta/other Hubitat devices; but I have only been able to get 1 of my 5 Radio Powr Savr (LRF2-OKLB-P-WH) motion sensors accurately reporting motion events over Telnet.
It seems like the RA2 Main Repeater is just sending 'inactive' then within a few milliseconds 'active' state even though there is no discernible motion/presence in the room. Not sure why the main repeater is sending these telnet states back to back without motion in the room? I am running the RadioRA 2 Inclusive version 12.10.0 and the repeater's firmware is up to date as well.
The only difference between the motion sensor that is working correctly ('OmotionBR3') and the others that are not working is that I do not have a motion lighting rule set up on any of the non-working motion sensors. Since hubitat's telnet is just receiving what the Ra2 Main Repeater is sending; I can't imagine the a rule in Hubitat would resolve this issue so I haven't set up a rule on any of the non-working ones yet. I am running Hubitat version 184.108.40.206.
I have not been able to tell if I have to add dummy switches/lighting zone to the Ra2 main repeater or not, but doing so has not resolved the odd telnet behavior I am seeing in the logs on Hubitat.
Any additional thoughts or troubleshooting steps anyone has would be greatly appreciated. (I have reached out to Lutron Support already to see if they have any suggestions but I haven't gotten any definitive answers there either.)
Not sure if @bravenel has any experience with odd telnet behavior or not?