[SOLVED] Camera Motion Detection Will Not Stay Disabled

[wittaj]

I have not investigated Dahua camera logs much. Would that leave a hint?

Not sure since it is logging in to the camera under the credentials. I will have to look and see if the log includes that kind of detail like SMD being turned on or off.

All I know is many of us have seen some wonky stuff with BI and DS - some have seen their motion zones for A and B get switched, some cameras wouldn't trigger but rollback and they would again, ONVIF triggers would quit working but rolling back and they would work again, so it isn't too far of a stretch to think that unintentionally it could be sending a command to the camera.

 

[Holbs]

Not sure since it is logging in to the camera under the credentials. I will have to look and see if the log includes that kind of detail like SMD being turned on or off.

All I know is many of us have seen some wonky stuff with BI and DS - some have seen their motion zones for A and B get switched, some cameras wouldn't trigger but rollback and they would again, ONVIF triggers would quit working but rolling back and they would work again, so it isn't too far of a stretch to think that unintentionally it could be sending a command to the camera.

wait a second. As I learned recently (unless I got my tech words messed up)... BI uses "external" and not "onvif" for check marked boxes such as in the ALERT tab. Now that gots me thinking. Dahua HAS to send ONVIF to BI. But if BI uses external.... hmm...ok...my head hurts now

 

[wittaj]

wait a second. As I learned recently (unless I got my tech words messed up)... BI uses "external" and not "onvif" for check marked boxes such as in the ALERT tab. Now that gots me thinking. Dahua HAS to send ONVIF to BI. But if BI uses external.... hmm...ok...my head hurts now

That is correct, my ONVIF triggers worked until a certain update and then I had to reconfigure for external. If I rollback to 5.4.6.3 then the ONVIF triggers work, but above that version I have to use external. I basically had to go to each camera and confirm or adjust the triggers based on a recent BI update.

Here is another strange one I have experienced. On my active deterrence camera on the back of the house, I would use a spotter camera on the side of the house to send audio to that back camera as someone approached the side of the house heading towards the back to try to scare them away before they make it to the backyard. With one of the updates it quit working. I rollback and it works again. Turns out when I was troubleshooting and deleted the camera and added it back in that update, the long main/substream configuration when you hit find/inspect would change in the newer update. If I did a rollback and it used this new configuration (Whatever that is called LOL), it wouldn't work. Go figure.

 

[Holbs]

That is correct, my ONVIF triggers worked until a certain update and then I had to reconfigure for external. If I rollback to 5.4.6.3 then the ONVIF triggers work, but above that version I have to use external. I basically had to go to each camera and confirm or adjust the triggers based on a recent BI update.

Here is another strange one I have experienced. On my active deterrence camera on the back of the house, I would use a spotter camera on the side of the house to send audio to that back camera as someone approached the side of the house heading towards the back to try to scare them away before they make it to the backyard. With one of the updates it quit working. I rollback and it works again. Turns out when I was troubleshooting and deleted the camera and added it back in that update, the long main/substream configuration when you hit find/inspect would change in the newer update. If I did a rollback and it used this new configuration (Whatever that is called LOL), it wouldn't work. Go figure.

my 6th sense gut says the BI changes of late... ONVIF to External...Dahua suspended from ONVIF (not sure what that all entails but it could be related).... hmmm. This is out of my wheel house

 

[wittaj]

my 6th sense gut says the BI changes of late... ONVIF to External...Dahua suspended from ONVIF (not sure what that all entails but it could be related).... hmmm. This is out of my wheel house

LOL - but yeah my cameras that are isolated from the internet would still think they are ONVIF lol, so unless BI coding changed to not accept ONVIF from Dahua (doubt BI did that), then it is some weird phenomena that has creeped in recent updates.

 

[Holbs]

LOL - but yeah my cameras that are isolated from the internet would still think they are ONVIF lol, so unless BI coding changed to not accept ONVIF from Dahua (doubt BI did that), then it is some weird phenomena that has creeped in recent updates.

doesn't hurt to investigate. right now, all my cameras only have 'external' check marked. I'll check mark both onvif & external both to see if my one troublesome 5442 re-enables motion. I mean...if it's not BI related, then it's Dahua camera firmware issue which is well beyond me.

 

[runraid]

If you wanted to integrate your cam with home assistant then I’ve made an integration and it’ll allow you to monitor the State of motion detection and turn it back on with an automation among other things.

GitHub - rroller/dahua: Dahua Camera and Doorbell Home Assistant Integration

Dahua Camera and Doorbell Home Assistant Integration - rroller/dahua

github.com

 

[MikeLud1]

That is correct, my ONVIF triggers worked until a certain update and then I had to reconfigure for external. If I rollback to 5.4.6.3 then the ONVIF triggers work, but above that version I have to use external. I basically had to go to each camera and confirm or adjust the triggers based on a recent BI update.

Here is another strange one I have experienced. On my active deterrence camera on the back of the house, I would use a spotter camera on the side of the house to send audio to that back camera as someone approached the side of the house heading towards the back to try to scare them away before they make it to the backyard. With one of the updates it quit working. I rollback and it works again. Turns out when I was troubleshooting and deleted the camera and added it back in that update, the long main/substream configuration when you hit find/inspect would change in the newer update. If I did a rollback and it used this new configuration (Whatever that is called LOL), it wouldn't work. Go figure.

Wittaj,

What I was able figure out is sofar that ONVIF tigger stop working with version 5.4.9.11 and greater. Below is an email that I am getting ready to send to Ken, i just want confirm the version it stop working before I send the email.

Ken,

In version 5.0.7 and up to version 5.4.9.10 if you use the camera to trigger via ONVIF you can alert on the ONVIF trigger. Now with version 5.4.9.11 and greater it will alert if external is checked.
Before version 5.4.9.11 I was able to use the cameras (all Dahua) to do all the triggering and distinguish between if I have motion detection enabled BI will see it as an ONVIF trigger and if I have an IVS Rule set BI will see it as an External trigger. Now everything is triggering as external.

I am not sure if this is a bug that got introduced with all the great Deep Stack work you have been doing

 

[Holbs]

If you wanted to integrate your cam with home assistant then I’ve made an integration and it’ll allow you to monitor the State of motion detection and turn it back on with an automation among other things.

GitHub - rroller/dahua: Dahua Camera and Doorbell Home Assistant Integration

Dahua Camera and Doorbell Home Assistant Integration - rroller/dahua

github.com

that little fantastic integration can also turn on/off motion sensor on the Dahua GUI? If so...neat! This is one of the best integrations I have on my HA! (next to my DSC alarm integration)

 

[runraid]

that little fantastic integration can also turn on/off motion sensor on the Dahua GUI? If so...neat! This is one of the best integrations I have on my HA! (next to my DSC alarm integration)

Yup! It’s a switch on that ha ui.

 

[Holbs]

doesn't hurt to investigate. right now, all my cameras only have 'external' check marked. I'll check mark both onvif & external both to see if my one troublesome 5442 re-enables motion. I mean...if it's not BI related, then it's Dahua camera firmware issue which is well beyond me.

I was in error. I had all my AI cameras having both ONVIF and External checke (as I was unsure what did what). I have now un-checked ONVIF leaving only External checked, in the BI triggers. Just to see what happens in the next coming days.

 

[tigerwillow1]

A new thread about motion detection being enabled with BI comes up from time to time. Check out this one:

Remind me again...why is BI causing motion detect to enable when you click "OK" in cam settings?

I concluded it's caused by a dahua camera bug (see post #7 and #11) only because it's easily reproduced with onvif device manager and BI totally out of the loop. This was over a year ago, so the raw data is a bit stale.

 

[Holbs]

A new thread about motion detection being enabled with BI comes up from time to time. Check out this one:

Remind me again...why is BI causing motion detect to enable when you click "OK" in cam settings?

I concluded it's caused by a dahua camera bug (see post #7 and #11) only because it's easily reproduced with onvif device manager and BI totally out of the loop. This was over a year ago, so the raw data is a bit stale.

that explains that! bugs

 

[Wildcat_1]

We know BI does not manage those camera settings, but people have seen issues like that happen. My camera operated fine for two years and then one of the recent BI updates with DS and SMD and MD got turned on. Strange coincidence that people have seen it with these cameras when using BI, but those that do not use BI haven't experienced it...

If I recall correctly, I think @Wildcat_1 recommends people delete the camera from BI when he is troubleshooting a camera in the camera GUI - do I have that correct and have you experienced similar issues when troubleshooting other's systems?

thats right @wittaj delete from BI while you troubleshoot with GUI first. Even leave it that way for a day or 2 to test and help fault isolate and then you can add it back once identified and resolved. @jaydeel feel free to reach out via DM if you need any help.

 

[jaydeel]

A new thread about motion detection being enabled with BI comes up from time to time. Check out this one:

Remind me again...why is BI causing motion detect to enable when you click "OK" in cam settings?

I concluded it's caused by a dahua camera bug (see post #7 and #11) only because it's easily reproduced with onvif device manager and BI totally out of the loop. This was over a year ago, so the raw data is a bit stale.

Thanks for the heads-up on this interesting link. It looks like I didn’t do due diligence before posting.

For anyone else who is catching up (like me!), the above link points to another…

Using IVS rules in BI for PTZ Camera

Hey Guys Looking for advice to see if this is the best approach for my situation. I have a Dahua PTZ that I use to patrol several areas that have little to no coverage. The distances the presets cover are varied from ~5m to around 200m. I'm using Blue Iris for everything, Its quite simply...

ipcamtalk.com

 

[SpacemanSpiff]

... bugs

Coders prefer to call them undocumented "features"

 

[jaydeel]

I'm going to try firmware updates next.

I'm quoting myself to provide a status update...

I finally had some time yesterday to try updating the firmware on one of my more problematic 2231R-ZS cams <link>.
So far, so good... it has not re-enabled motion detection for over 24 hours.

But... (there's always a "but") ...
1. The update would not accept the saved 'DahauDeviceConfig.backup' configuration file, so I needed to manually reconfigure the camera -- include the IVS tripwires.
2. After re-configuring the camera, the tripwires do not seem to be working.

I have IVS enabled...

I've defined tripwires... which BTW I've noticed are now labeled as IVS1, IVS2, etc. instead of Rule1, Rule2.

The tripwires do not appear on the Live feed (as blue lines, arrows, and labels IV1, IVS2) like they do for all my other IVS-enabled Dahua cams.


I've checked and Smart Code is disabled on the main stream's settings.

I've be greatly appreciative If anyone has ideas of what else I can try.

 

[Holbs]

I'm quoting myself to provide a status update...

I finally had some time yesterday to try updating the firmware on one of my more problematic 2231R-ZS cams <link>.
So far, so good... it has not re-enabled motion detection for over 24 hours.

But... (there's always a "but") ...
1. The update would not accept the saved 'DahauDeviceConfig.backup' configuration file, so I needed to manually configure the camera -- include the IVS tripwires.
2. After re-configuring the camera, the tripwires do not seem to be working.

I have IVS enabled...
View attachment 97635
I've defined tripwires... which BTW I've noticed are now labeled as IVS1, IVS2, etc. instead of Rule1, Rule2.
View attachment 97636
The tripwires no longer appear on the Live feed (as blue lines, arrows, and labels IV1, IVS2) like they do for all my other IVS-enabled Dahua cams.
View attachment 97637

I've checked and Smart Code is disabled on the main stream's settings.

I've be greatly appreciative If anyone has ideas of what else I can try.

I attribute not seeing live feed blue lines (ivs1, ivs2) to your browser? Nobody could get that using Chrome or associated browsers. Only through Internet Explorer. If you get no lines via IE....well, well, well....

 

[jaydeel]

Thanks for the tip... So far I'm unable get the configuration displayed in IE, only Firefox and Pale Moon.

Seeing the blue lines would not be a big deal if the camera would actually trigger as configured.

It does trigger, however, if I enable 'Motion Detection'.

 

[jaydeel]

OK, I just got it working in IE. The blue lines are there. Good call!


Now I just need to figure out why they're not triggering.