I posted elsewhere about this same topic before finding this thread.
I worked as a software developer in a former life and so can speak from a position of having significant experience in this area.
Software is MUCH easier to change than firmware is to change so, clearly, the quick and easy fix is to implement a sensitivity setting schedule. Zone settings are going to be difficult to back engineer into the cameras and, even if implemented, would likely severely impact battery life.
Reading through this lengthy thread there appear to be 2 DIY solutions, one involving electrical tape over the sensor and the other involving manually changing sensitivity settings according to the time of day (or using an ITTT mash-up).
The scheduling issue should be INCREDIBLY easy to implement and it is beyond me as to why this hasn’t been accomplished in 5 months. I mean, how hard can it be? There is a schedule built into the app already - just add sensitivity settings for each camera to the schedule and DONE! That on its own would likely solve 80% or more of the issues users are reporting.
A firmware solution to the electrical tape fix is not so easy to resolve, unfortunately. I am not even sure it is possible to do if the cameras were not designed with it in mind. It’s not a huge issue for me personally and I’ve been able to resolve most of the issues with careful re-positioning of the cameras although I recognize that is not always possible for other users. So, electrical tape it is then.
Instead of putting resources into bringing a siren (and presumably the alarm system) to market, I respectfully suggest that the team at Blink gets onboard with resolving this very irritating issue. As another user here said, continuing to sell a flawed product will do nothing for your new customers willingness to further invest in the Blink infrastucture.
Just fix it already.