Lutron occupancy sensor stop reporting in certain times of day

I have RadioRa2 system running and i have only one occupancy sensor in my kitchen (where i do not have any other lutron device as switch or anything). The sensor is alone in that area, and has a very rare behavior, in certain times on the day work as expected and i can see on HA the report, but suddenly stops to report the state for few hours (4-8 hours), then without any change in config start to report it again. And can ensure that area is pretty much alive in that “pause time” of the sensor.

The RadioRa2 dont let check coms between the repeater and the sensor but they are close.

Model: LRF2-OCR2B-P-WH

The sensor has this hardware config:

  • Time: 15min
  • Sensitivity: medium
  • Light: always on

The only errors related to Lutron i have on my log is:

2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Started
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Connecting
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Connected
2021-06-05 11:11:20 INFO (SyncWorker_0) [homeassistant.components.lutron] Connected to main repeater at 192.168.1.60
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Unknown cmd MONITORING (~MONITORING,12,2)
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Unknown cmd MONITORING (~MONITORING,255,2)
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Unknown cmd MONITORING (~MONITORING,3,1)
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Unknown cmd MONITORING (~MONITORING,4,1)
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Unknown cmd MONITORING (~MONITORING,5,1)
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Unknown cmd MONITORING (~MONITORING,6,1)
2021-06-05 11:11:20 INFO (Thread-4) [pylutron] Unknown cmd MONITORING (~MONITORING,8,1)

Anyone can give me some ideas about this?