GXV3615WP_HD motion detection sends too many emails


#1

I have 4 cameras with settings to send email when motion is triggered. But it sends 100’s of emails.
I have attached a screen shot of my settings and the inbox of my email
How can we reduce this?motiontakesmanypicturesmotionsettings


#2

bumpity bump bump


#3

if you aim the camera to a point where motion is impossible, do the alarms continue?
if not, then you need to determine the area of detection interest and possibly also alter the times.


#4

Actually, the motion timer is set for off hours, so there is normally NO motion (and no emails). The 100’s of photos are emailed over a small period of time when, for instance, someone comes in early.

As you can see from my screen shot of the settings, the motion is active from 8PM to 7AM, and the pre & after alarm is set to 2 minutes

So if someone comes in before 7 AM, the camera sends emails several times per second for 4 minutes. Crazy !


#5

Perhaps the attached will help as it sounds like the timing of what is considered an alarm by the motion detection needs some adjusting.


#6

Thanks I had a look at the PDF and the video

Still does not account for why the camera sends 100’s of emails over a period of a few minutes :frowning:

Also each email contains a pair of photos (as opposed to one photo which is what I get from other camera brands)


#7

In the attachment I sent, there was a link that showed how to set up the cameras. The issue I saw is that the 3615 is an older model that is no longer supported and is not getting any firmware updates. The video shows a couple of new settings that have apparently been incorporated in the meantime that allows you to define the alarm period on the supported models.

My guess is that the issue is related as to what “is” an alarm from the camera’s perspective and that if you have movement in a region, the alarm event period is too short (for your needs) and is therefore creating new alarms for what in reality may be the same event. This camera has been out of production for some time now (2 or 3 years). Is this something that just now started or did you recently acquire and install? Curious.

The only thing I can suggest is to raise a ticket with GS.


#8

Thanks for the input :slight_smile:
There are 4 cameras with the same behavior, this email behavior occurred from the beginning
I’ll see about a ticket
Thanks


#9

It can be that email is not correctly ended for GS and correct for mail server, so GS repeat process of sending as it believe it was not delivered.
For this you need check mail flow if possible.


#10

Hi Marcin
How do I do that?


#11

Packet capture on router or manageable switch.
You can try syslog from camera but i’m not sure if it shoe desired info.


#12

We have a basic router/modem from Bell, I looked and it does not appear to have this functionality.
And we have a couple of switches but they are not managed.
I can try the syslog, but what is the syslog server setting?Clipboard01


#13

You can set syslogserver on your PC.
Visualsyslog is program for windows.


#14

I installed the Windows app, some example data below.
Since the motion is set to off hours, I’ll see if I can launch the syslog app with the Windows Scheduler

192.168.2.173 May 11 08:42:37 local1 debug avserver gs_sdRecord.c:chn_record_check():483: no record device !
192.168.2.173 May 11 08:42:37 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:37 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:38 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:38 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:39 local1 debug avserver gs_sdRecord.c:chn_record_check():483: no record device !
192.168.2.173 May 11 08:42:39 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:39 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:40 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:40 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:41 local1 debug avserver gs_sdRecord.c:chn_record_check():483: no record device !
192.168.2.173 May 11 08:42:42 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:42 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:42 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:42 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:43 local1 debug avserver gs_sdRecord.c:chn_record_check():483: no record device !
192.168.2.173 May 11 08:42:43 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:43 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:44 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:44 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:45 local1 debug avserver gs_sdRecord.c:chn_record_check():483: no record device !
192.168.2.173 May 11 08:42:45 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:45 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame
192.168.2.173 May 11 08:42:46 local1 debug avserver gs_venc.c:VENC_JpegThrFxn():5224: sending jpeg data to ring buffer thread
192.168.2.173 May 11 08:42:46 local1 debug avserver gs_ringbuf.c:RINGBUF_ThrFxn():891:[Success] : received JPEG frame

#15

Ok, data seem ok, but as i have no knowledge if that is correlated with motion no comment.


#16

The data was just a sample
I have to get the data when the emails are being sent, which is off hours when no one is here.
This is proving difficult, I am trying to get Windows Task Scheduler to start the syslog and stop it a few minutes later


#17

Hi Marcin
As usual got a whole lot of alarm emails this morning
I used Visual Syslog to record the debug output

emails.zip (75.5 KB)


#18

What firmware is in unit ?
Ii can see that camera really sent a lot of emails, so it can fw problem.


#19

Hi Marcin
Thanks for all the help :slight_smile:
firmware


#20

Latest :confused:
Try contact GS via ticket or you can try donwgrade firmware.
helpdesk.grandstream.com