Something is triggering the motion detection ...
From the logs - @ 04:10:58.909 PM the device sends Zigbee Occupancy cluster 0x0406 event with value 01 - this is 'motion active' event.
34 milliseconds earlier, the device sends a 'light' event - seems OK at 4PM day time.
@ 04:11:26.373 - (one minute and 28 seconds later) received motion inactive event.
All seems to be processed OK in the driver.
Can you think of any of these 'false detection scenarios' that may apply in your use case?
Water flowing in drainage pipes as an example?
Increase the fadingTime to 30 or 60 seconds - will this help?
You can also try setting the 'detectionDelay' to 1 second - this is a parameter exposed by the device, but not mentioned officially in the Sonoff docs. I didn't notice any difference varying this parameter. With other mmWave radars (Tuya), incresaing the detectionDelay reduces a lot the false triggering - in spite of delayed motion detection, of course.
