Amcrest Forum

I have setup my camera with the correct time zone (Central; -0600) and the time is correctly shown on the live video, however, when email alerts are sent for alarms, the time shows "13 hours ago". The body of the email shows the correct time of the alarm, but the email header is incorrect. If I set the timezone to +0700, then the email time is correct, but the alarm/video time is off.

I assume this is a bug and it would be great if it would get fixed.

Thanks.

Hello wyattf ,

Thank you for bringing this up and we did have a few other customers complains about this. We will report this to the R&D team.

ATTENTION AMCREST: You guys have the Date header in the email hard-coded to always be +0800. THAT is the problem. Simply read in the saved time zone string, format it correctly (remove GMT and : from the string leaving just the sign & 4 digits) then use that for the offset in Date header.
Example for Eastern time zone where I'm at.
Date: Wed, 19 Oct 2016 05:09:07 +0800
GMT-04:00 -> -0400 then Date header becomes:
Date: Wed, 19 Oct 2016 05:09:07 -0400
VOILA!

FYI I posted a python proxy script that works as a temp fix until the firmware is updated:
https://amcrest.com/forum/technical-dis ... t1713.html

Is this ever going to be addressed or is learning python a requirement for Amcrest 841 camera ownership?

This user was kind enough to give Amcrest the fix when will Amcrest actually code it?

Only opened one box of six cams as a tester missing an email motion alert because the time is off is NOT acceptable.

Mine does this too. I was getting correct time information for the first 10 e-mails or so, then after that it started sending me e-mails with incorrect time "16 hours ago"

@amcrest: how is it possible that such an issue reported 8 months ago is still not fixed?
I just bought an IP2M-841B and my mails are 7hrs backdated. Support is unable fix. Unbelivable...

I was have the same problem with the time stamp. I was using Thunderbird as my email client, so I tried another email client (Windows 10 Mail) and the problem was resolved. So it must be a compatibility issue with Thunderbird.

Not to beat a dead horse, but the date is always formated in an email as Alarm Start Time: DD/MM/YYYY regardless of how it's configured in the setups.

I am having the same problem with my new IP3M-941. I am frustrated to say the least.