Fibaro Motion Sensor no longer sending motion

Hello,

I have had a Fibaro Motion Sensor (FGMS-001) in my basement workshop for some time. It has always reliably turned on the main workshop lights when I enter. Recently (within the past week), it has not. I initially thought it was a low battery (it was low), so I changed it to a new one (now reading 100%). That did not fix the problem. Looking at my logs, I am only seeing luminance and temperature events. No motion events. I enabled debug logging and it also shows no motion. In the log below, I can tell when I went downstairs after enabling logging and turned on other basement lights (luminance increased from single digits to around 100. It increased again to around 140 when I manually turned on the main workshop light. When I passed in front of the sensor, it's LED flashed RED, as it should when it sees motion. However, no events in my logs. Is my sensor going bad, or is it something else?

C8-Pro hub, 2.5.1.147

Driver: FIbaro Motion Sensor ZW5 (Hubitat driver)

Rather than looking in logs, what do you see in the devices page > Events tab? That stores the last 'x' events of each type (motion, luminance, temperature) where 'x' is the number of events set in the Device Info > Event History Size (mine is set to 11). So in there you should see the last 11 events timestamped to indicate when motion was working.

Thank you. Last motion event on the device Events page was early afternoon 8/11. That evening, I see where I changed the battery (noticed at that time motion was not working when I walked in the room and saw the battery was low). No motion events since before the battery change. I see lots of other events (temp, luminance, 3-axis), but no motion.

Strange. I have about 5 of them in my system and have never had one fail. I wonder whether it might be worth excluding and reincluding it? A bit of a pain but worth a try.

I've installed an old Zooz ZSE09 to cover the workshop for now (my old ZSE09's tend to often give a false "active" after an "inactive", but when they do, it is always < 300ms after the "inactive" so I just use a virtual motion detector and filter out any actives <350ms after an inactive).

When I have some time this week, I'll look at the Fibraro more. I'm hoping (but not expecting) it fixes itself with some time!