Thanks for following up with your findings. I think this is largely going to be due to the differences in how Canary Flex records motion when plugged in versus when on battery.
When plugged in, your Canary Flex uses “computer vision” to determine if motion is happening. It’s basically just looking at changes in the pixels on the screen. Any pixels changing is registered as motion. Our computer vision algorithms then try to filter out repetitive motion from things like ceiling fans, or background motion like lights and shadows. However, inevitably some motion is going to get passed those filters. With night vision in particular, the infrared light bounces off those precipitation particles falling very close to the camera and it’s very difficult for the Canary to distinguish this from important motion.
When used unplugged, your Canary Flex will detect motion using its passive infrared (PIR) sensor. This sensor will blast the area with rays of passive infrared, which will detect heat signatures. When something with a different heat signature than the surrounding environment passes through those rays, it “trips” the sensor and your Canary Flex begins to record. This is going to be less likely to pick up something like precipitation.
You may want to adjust the recording range for your Canary Flex on battery to see if you can get better motion detection at the distance you have it mounted. This would allow you to avoid the constant recording from precipitation without compromising your motion detection for more important things. However, it may be preferable to leave it plugged in with lowered sensitivity to avoid getting alerts and just deal with the extra videos in your Timeline. Ultimately it’s up to you.
We’re definitely always working on improving our computer vision algorithms to try and help with situations like this, and we really appreciate your reports! Please continue noting any unusual motion detection you have with your Canary Flex so we can look into options for improving it