Many of us are using the IVS features of the Dahua cams so we want the normal Dahua motion disabled then set up our IVS rules. Within BI we make sure that "ONVIF and PullPointSubscription is enabled" and "Camera's digital input or motion alarm" is enabled" so that we can utilized Dahua IVS. I don't know any other way to get Dahua and BI to work together for IVS capability.
There are two workarounds for this issue. @bleepsilver mentioned the easiest one in
post #6, IMO. The other one is to use a
Blue Iris "Run Action" Alert to run a CURL command that connects to the camera and issues the command to disable motion detection. With that, motion detection will fire once after BI reconnects to the camera, then is disabled until the next time BI reconnects.
My vote is that this is a Dahua issue. Like
@tigerwillow1 mentioned, if you run the "ONVIF Device Manager" program, when it connects to a Dahua camera and subscribes to PullPoint, the Dahua camera suddenly has motion detection enabled (just like with Blue Iris). My Hikvision cameras do not wind up with motion detection enable when either the Blue Iris/ONVIF Device Manager apps connect and use PullPointSubscription.
When I emailed Ken about this a little over a year ago, he indicated that the proper way to handle this would be to choose which specific ONVIF/PullPointSubscription alerts to trigger on, but he had some bigger things to work on first. So his solution sounds like it works around the fact that motion detection somehow gets enabled on Dahua cameras when PullPointSubscriptions are used.