DMSS and no notifications

FLGator

Getting the hang of it
Aug 26, 2022
95
74
Tennessee
Hi.

I have setup my NVR with 5 cameras 5442 and a 180. I have enabled PnP on the NVR (for testing purposes only as I want to be able to test that I can get notifications before I tackle the VPN project) and added that NVR to DMSS and I can see my 5 cameras video.

I followed all instructions on setting up DMSS and the alerts\notifications on my Android phone (Allow notifications in the App). I went into DMSS app and went to Multi Channel Alarm Subscription and Enabled, went into Motion Detection and added the 5 cameras, did the same for Tripwire Alarm and saved.

No other settings have been touched.

I went into my NVR and into the AI, Parameters, IVS and created a Tripwire rule for all 5 cameras but when I move around, I get no notifications at all.

Where do I go from here? I cannot find any other information on the web as to why I am not getting notifications.

Thank you all
 
You want to set up the AI in the cameras, not the NVR. Using NVR AI seriously throttles the NVR.

Next post screenshots of a field of view showing the tripwires. Do you have and SD card in the camera or from the NVR can you confirm the camera actually triggered?
 
  • Like
Reactions: JDreaming
You want to set up the AI in the cameras, not the NVR. Using NVR AI seriously throttles the NVR.

Next post screenshots of a field of view showing the tripwires. Do you have and SD card in the camera or from the NVR can you confirm the camera actually triggered?
No SD cards. These cameras are not mounted yet and just on my desk. Here are some screen shots. This is from the camera itself. So I should delete the rules I made in the NVR itself?
 

Attachments

  • 20230819_105705.jpg
    20230819_105705.jpg
    3.1 MB · Views: 14
  • 20230819_105728.jpg
    20230819_105728.jpg
    2.9 MB · Views: 13
Yes, only do the IVS rules in the camera. Basically everything that can be set up in the camera should be done there. Think of the NVR as simply the recording device and alert device and that is all you setup in the NVR.

The camera will feed the IVS rules into the NVR. In theory it would work going from the NVR to the camera, but experience shows that isn't the case and when it conflicts then crazy things happen.

You need to try it in a realistic setting - sitting on the desk or floor pointing up isn't going to do it - that field of view is too tight and close - waiving a hand won't trigger it and only seeing your upper body won't trigger it (at least reliably) because that is not the field of view the AI was trained on.

Set it up looking down a hall or across the room where your whole body can be seen in the field of view.

For best results IVS needs to see the whole body and half of the body needs to cross an IVS line. Seeing a body too much from ground up or too high looking down causing problems.
 
  • Like
Reactions: JDreaming
Yes, only do the IVS rules in the camera. Basically everything that can be set up in the camera should be done there. Think of the NVR as simply the recording device and alert device and that is all you setup in the NVR.

You need to try it in a realistic setting - sitting on the desk or floor pointing up isn't going to do it - that field of view is too tight and close - waiving a hand won't trigger it and only seeing your upper body won't trigger it (at least reliably) because that is not the field of view the AI was trained on.

Set it up looking down a hall or across the room where your whole body can be seen in the field of view.

For best results IVS needs to see the whole body and half of the body needs to cross an IVS line. Seeing a body too much from ground up or too high looking down causing problems.
Okay, I will do that now. Thank you!!
 
Ok, so I just did that and still no events. Any other ideas? Here is the test I did.
 

Attachments

  • Screenshot_20230819_112725.jpg
    Screenshot_20230819_112725.jpg
    442.8 KB · Views: 18
  • Screenshot_20230819_112732.jpg
    Screenshot_20230819_112732.jpg
    458.8 KB · Views: 18
  • Screenshot_20230819_112734.jpg
    Screenshot_20230819_112734.jpg
    502 KB · Views: 14
  • Screenshot_20230819_112735.jpg
    Screenshot_20230819_112735.jpg
    510 KB · Views: 15
Are the cameras on default settings? Although we can tell that is motion, it all is too similar of a grey shade.

In terms of getting the most out of the camera, here is my "standard" post that many use as a start for dialing in day and night that helps get the clean captures and help the camera recognize people and cars.

Start with:

H264
8192 bitrate
CBR
15FPS
15 iframes

Every field of view is different, but I have found you need contrast to usually be 6-8 higher than the brightness number at night.

We want the ability to freeze frame capture a clean image from the video at night, and that is only done with a shutter of 1/60 or faster. At night, default/auto may be on 1/12s shutter or worse to make the image bright.

In my opinion, shutter (exposure) and gain are the two most important parameters and then base the others off of it. Shutter is more important than FPS. It is the shutter speed that prevents motion blur, not FPS. 15 FPS is more than enough for surveillance cameras as we are not producing Hollywood movies. Match iframes to FPS. 15FPS is all that is usually needed.

Many people do not realize there is manual shutter that lets you adjust shutter and gain and a shutter priority that only lets you adjust shutter speed but not gain. The higher the gain, the bigger the noise and see-through ghosting start to appear because the noise is amplified. Most people select shutter priority and run a faster shutter than they should because it is likely being done at 100 gain, so it is actually defeating their purpose of a faster shutter.

Go into shutter settings and change to manual shutter and start with custom shutter as ms and change to 0-8.3ms and gain 0-50 (night) and 0-4ms exposure and 0-30 gain (day)for starters. Auto could have a shutter speed of 100ms or more with a gain at 100 and shutter priority could result in gain up at 100 which will contribute to significant ghosting and that blinding white you will get from the infrared or white light.

Now what you will notice immediately at night is that your image gets A LOT darker. That faster the shutter, the more light that is needed. But it is a balance. The nice bright night static image results in Casper blur and ghost during motion LOL. What do we want, a nice static image or a clean image when there is motion introduced to the scene?

In the daytime, if it is still too bright, then drop the 4ms down to 3ms then 2ms, etc. You have to play with it for your field of view.

Then at night, if it is too dark, then start adding ms to the time. Go to 10ms, 12ms, etc. until you find what you feel is acceptable as an image. Then have someone walk around and see if you can get a clean shot. Try not to go above 16.67ms (but certainly not above 30ms) as that tends to be the point where blur starts to occur. Conversely, if it is still bright, then drop down in time to get a faster shutter.

You can also adjust brightness and contrast to improve the image. But try not to go above 70 for anything and try to have contrast be at least 7-10 digits higher than brightness.

You can also add some gain to brighten the image - but the higher the gain, the more ghosting you get. Some cameras can go to 70 or so before it is an issue and some can't go over 50.

But adjusting those two settings will have the biggest impact. The next one is noise reduction. Want to keep that as low as possible. Depending on the amount of light you have, you might be able to get down to 40 or so at night (again camera dependent) and 20-30 during the day, but take it as low as you can before it gets too noisy. Again this one is a balance as well. Too smooth and no noise can result in soft images and contribute to blur.

Do not use backlight features until you have exhausted every other parameter setting. And if you do have to use backlight, take it down as low as possible.

After every setting adjustment, have someone walk around outside and see if you can freeze-frame to get a clean image. If not, keep changing until you do. Clean motion pictures are what we are after, not a clean static image.
 
No, they are not. I followed your post and have the cameras set up the way you have suggested. I did this last week.
 
It shouldn't matter what the IPs are of the cameras correct? If I can get to the NVR to see the feeds through DMSS, the notifications should come? Or, there is no Internet access for the cameras, I have them on a subnet with no internet access. 10.1.1.1 and no gateway with access. So if they themselves are supposed to send the alert, they cannot? But if it should come from the NVR, then it should correct?
 
It looks like you have them connected to the NVR POE correct? If so, the NVR acts as a firewall of sorts and blocks the cameras from the internet. But if you have the alerts configured in the NVR and the NVR has internet access, then you should be getting the alerts.

That is why I said consider the NVR simply as the device that stores the video and sends the alerts and setup anything camera related in the camera itself.
 
It looks like you have them connected to the NVR POE correct? If so, the NVR acts as a firewall of sorts and blocks the cameras from the internet. But if you have the alerts configured in the NVR and the NVR has internet access, then you should be getting the alerts.

That is why I said consider the NVR simply as the device that stores the video and sends the alerts.
I do have them connected through the POE on the NVR but the NVR is a different address than the cameras. I have deleted the IVS rules from the NVR itself and left the one created in the camera only.
 
So maybe change the IP address of the cameras to the same as the NVR? If I do this though, wouldn't the cameras have internet access now?
 
I do have them connected through the POE on the NVR but the NVR is a different address than the cameras. I have deleted the IVS rules from the NVR itself and left the one created in the camera only.

That is the way it should be. By default the NVR puts the cameras on the 10.0.0.x subnet.

DO NOT CHANGE THE CAMERAS TO THE SAME IP ADDRESS OF THE NVR - that will create way too many issues. Almost everyone here has it working successfully with the cams on the default 10.0.0.x subnet, so the issue is something else.

Is your NVR on the same IP address subnet as your LAN?

Are you able to see the NVR when not on home wifi?

The issue could maybe be the P2P server is down as well.
 
  • Like
Reactions: JDreaming
^^^^^^^
THIS
 
  • Like
Reactions: JDreaming
Your problem isn’t the IPs of the cameras. Leave that alone

seems we have 2 issues
1- getting IVS alerts to record and
2- getting alerts to DMSS via P2P

so if that’s right we gotta fix #1 before we tackle #2
 
  • Like
Reactions: JDreaming
That is the way it should be. By default the NVR puts the cameras on the 10.0.0.x subnet.

DO NOT CHANGE THE CAMERAS TO THE SAME IP ADDRESS OF THE NVR - that will create way too many issues. Almost everyone here has it working successfully with the cams on the default 10.0.0.x subnet, so the issue is something else.

Is your NVR on the same IP address subnet as your LAN?

Are you able to see the NVR when not on home wifi?

The issue could maybe be the P2P server is down as well.
That is the way it should be. By default the NVR puts the cameras on the 10.0.0.x subnet.

DO NOT CHANGE THE CAMERAS TO THE SAME IP ADDRESS OF THE NVR - that will create way too many issues. Almost everyone here has it working successfully with the cams on the default 10.0.0.x subnet, so the issue is something else.

Is your NVR on the same IP address subnet as your LAN?

Are you able to see the NVR when not on home wifi?

The issue could maybe be the P2P server is down as well.
Yes, the NVR is on the same subnet as my Lan and I am able to see the cameras through the NVR with DMSS with my WIFI turned off on my android phone.