IVS rule not functioning

K

Keizer

Getting comfortable
Jan 3, 2023
321
588
Wa
I have two cameras that don't detect motion using IVS. One is an Empiretech 4KT and the other is the T-180. All my other 4K T cams function just fine using IVS. I have everything set up with these two cameras exactly the same way as the others that work just fine. Settings are identical in both the camera GUI as well as in Blue Iris. I am using the Pushover app and use the basic email function to get alerts. I can right on the cameras in both Blue Iris as well as UI3 and select "trigger now" and I get the Pushover alert just fine. But, if I walk in front of these two cameras I get nothing. In the camera status it shows zero triggers and zero motion. I have tried doing a factory reset as well as deleting the camera from Blue Iris and having BI re-discover the cameras. Nothing has worked.

I wanted to add that I have tried regular motion detection in Blue Iris (No IVS) and it works just fine.

Any ideas?
 
Last edited:
For anyone finding this in the future I figured out the issue. I had to set the second "ONVIF source" text box to "00000" in the Blue Iris camera settings. My working cameras already had this populated.
 
  • Like
Reactions: Oneup
Just out of curiosity, I just checked both "ONVIF source" text boxes for all of my Dahua cameras (6 total: two 5442T-ZE, two 2231R-ZS, one SD12203T-GN, one 5231R-ZE).

All had a value of '00000' in the boxes, EXCEPT the two 2231R-ZS cameras which had '000' (see screenshot).
They've been working just fine.

1760291382916.png

Does anyone know (or have you found) that the number of zeros in this "ONVIF source" text box field matters?

As an experiment, I've just changed the setting both 2231R-ZS cameras to '00000'.
 
jaydeel said:
Just out of curiosity, I just checked both "ONVIF source" text boxes for all of my Dahua cameras (6 total: two 5442T-ZE, two 2231R-ZS, one SD12203T-GN, one 5231R-ZE).

All had a value of '00000' in the boxes, EXCEPT the two 2231R-ZS cameras which had '000' (see screenshot).
They've been working just fine.

View attachment 229760

Does anyone know (or have you found) that the number of zeros in this "ONVIF source" text box field matters?

As an experiment, I've just changed the setting both 2231R-ZS cameras to '00000'.
Click to expand...
The only camera (out of the 13 that I have deployed) that has three zero's is my PTZ cam. My 2nd PTZ cam (different model) has the five zero's. As long as both boxes are populated everything seems to work fine.
 
jaydeel said:
Does anyone know (or have you found) that the number of zeros in this "ONVIF source" text box field matters?
Click to expand...
Testing complete. Quoting myself to say ... IT MATTERS

DETAILS: I changed the '000' entries to '00000', then tested the two cameras. Results: No ONVIF alerts.
Then I repeated the Find/Inspect, which restored the values to '000'. Result: ONVIF alerts.
 
Last edited:
  • Like
Reactions: Oneup
jaydeel said:
Testing complete. Quoting myself to say ... IT MATTERS

DETAILS: I changed the '000' entries to '00000', then tested the two cameras. Results: No ONVIF alerts.
Then I repeated the Find/Inspect, which restored the values to '000'. Result: ONVIF alerts.
Click to expand...
What's interesting is when I hit Find/Inspect on the two cameras I was having issues with, only one of the "ONVIF source" text boxes will have 5 zeros. The other box is blank and I get no ONVIF alerts. I have to maually set the zero's in the 2nd box and save to get the ONVIF alerts. On all my other cameras both "ONVIF source" text boxes were populated with the zero's after hitting Find/Inspect.
 
Keizer said:
What's interesting is when I hit Find/Inspect on the two cameras I was having issues with, only one of the "ONVIF source" text boxes will have 5 zeros. The other box is blank and I get no ONVIF alerts. I have to maually set the zero's in the 2nd box and save to get the ONVIF alerts. On all my other cameras both "ONVIF source" text boxes were populated with the zero's after hitting Find/Inspect.
Click to expand...
Looks like yet another quirk for certain Dahua model/FW combos.

You might want to check if your manual setting is retained both when the camera is reset AND when it is rebooted.

EDIT: I say this because I have a subset of cameras that Blue Iris insists on enabling the camera-level Motion detection setting each.and.every.time it resets them. To circumvent this, I run a Task Scheduler task every 5 minutes to check for this condition. If necessary, it toggles OFF the motion detection setting using a Dahua API command.
 
Last edited:
  • Like
Reactions: Keizer
We have seen this issue reported here with the new GUI.

For some reason, the newer GUI cams respond better to BI if a factory reset is done first on the camera.

That is my standard practice for any new camera, so I haven't experienced this issue, but when people that reported IVS wasn't working and I suggested a factory reset, BI then recognized it properly.
 
  • Like
Reactions: jaydeel
wittaj said:
We have seen this issue reported here with the new GUI.

For some reason, the newer GUI cams respond better to BI if a factory reset is done first on the camera.

That is my standard practice for any new camera, so I haven't experienced this issue, but when people that reported IVS wasn't working and I suggested a factory reset, BI then recognized it properly.
Click to expand...
I'm setting up Blue Iris from scratch on a new PC. Maybe I should have factory reset all my cameras first. But, I only had the issue with the two.
 
You must log in or register to reply here.
Top Bottom