Posts made by Crimp On_62210811129

I also noticed this issue, and how it should be possible to avoid the camera causing a motion event (itself) by switching between day and night modes. Basing motion detection on changes in the actual picture offers significant capabilities over using a cheap PIR sensor (like the Argus models), but it also leads to irritating issues, like this one and those pesky insects flying close to the infrared LED's.

I'm so glad you posted this, because it opens up entirely new possibilities for me. Can you please describe more about the video files? Like, when the camera is recording constantly, does it send one GIANT file for the whole time? Does it break recordings up into set length? The video files I've seen have REALLY ugly names. How do you know which files have motion (and which do not)?

Thanks

My understanding is that FTP (File Transfer Protocol) implies sending a "file". Since the 410 camera has no internal storage, the only "file" it could FTP would be an image. (Other camera models use memory cards to record motion events, which can be played back or transferred later.) So, it doesn't seem like FTP really applies to the 410 as far as motion recording is concerned.

Traditional POE cameras, like the 410 are intended to stream (either constantly, or when they detect motion) to a server that they are constantly connected to. (Such as one of Reolink's NVR models, a NAS system, or software like Blue Iris.)

I don't have an NVR, so I purchased models with SDCards which store recordings on the camera.

Hope you find a way to do what you want.

I have verified that email from Argus does work. One thing that threw me in the beginning was that the Argus needs to have an email "account" it can access to send the message using SMTP. I set up a GMail account named "myhousename@google.com". The camera logs into Google's SMTP server using this account name and password, and sends messages to the email addresses that I specify. (My regular GMail account, for example.)

Another wrinkle is that you have to know which "port" the SMTP server listens to. "Normal" SMTP listens to port 25. Google, however, listens to port 465.

There are other ways that Reolink could have set this up. For example, they could have a BIG email server that the camera would access using credentials known only to Reolink, and that server could send messages to wherever you specified. They could also have made each camera an SMTP server, which runs into issues with a log of ISP's. But, that's not what they did.

The way it works is probably the best solution. I'm on Time-Warner (now Spectrum), and all my cameras send email as they are supposed to.

Hope that helps.

PIR scheduling is obvious, (

once you understand it

).

For row one:
0-5 on the left means the first box is hour "0", i.e. midnight to 12:59am
second box is 1:00am to 1:59am
third box is 2:00am to 2:59am
forth box is 3:00an to 3:59am
fifth box is 4:00am to 4:59am

For row two:
6-10 on the next row, the first box is 6:00am to 6:59am
box two is 7:00am to 7:59am

etc. etc.