Posts made by joseph_1979

@amenard1958_533307347460326 I have set email alert on all my cameras using gmail and have no issue. Just ensure you use the password generated by the google account as Reolink cams can't do authentication. Go to Reolink site and search for article 360007010613. If I recall correctly error code 483 is erroneous email/password.

@mehterfaraz_321300255867016 Insert a switch between the NVR and the BB router. Then connect your PC to the switch (change the IP of the PC) and try to connect to your NVR. You may use your web browser to connect using the URL http://ip_of_nvr (assuming you left the http port 80 unchanged on the NVR). I assume that you are able to configure the NVR using the mouse connected to its USB and having a VGA monitor connected to its VGA port. You may include the network setting on the NVR to check it out.

@dbeck_417705845436546 For battery operated cameras, only administrator account is available.

@bethib4_368087625150636 Change the credentials of the accounts (users) and do a reboot if you want to disconnect them immediately.

@luis-machado-m_510059597697211 Yes, I read you have 3 GMTs and the government occasionally change the DST and this causes havoc everywhere. So on the Android phone the timezone is correct and on the Reolink application it is wrong? I always thought that this is an OS dependent rather than client.

@mikegray_495486781677795 Can you check whether the device is still bound to the cloud? https://support.reolink.com/hc/en-us/articles/360008584054-How-to-Bind-Reolink-Cameras-to-the-Existing-Cloud-Account

@alvaro2 The official latest client 8.8.4 superseded the beta version 8.10. As stated I have no issue with both E1 OD and E1 Zoom. But recall that there are various hardware versions of E1 OD and this has to be factored in. In fact E1 OD is not included in the download center.

@alvaro2 I have upgraded my E1 OD to 3.1.0.1584 for at least two months. I didn't have any live or playback streaming issue when using both the 8.10beta and the 8.8.4 Windows client. I have the latest E1 Zoom too and didn't encounter the issue you have described. The only issue I have with the E1 OD is the deviation when the camera returns to the guard point. And I know that this is attributed to the non-precision gear mechanism. But I guess that Reolink solved this in the new E1 versions, at least the E1 AI Zoom always returns to the programmed guard point.

Did you try with the latest client 8.8.4? Please note that if you upgrade from 8.10beta all the cameras will be deleted and you need to add them.

@737driver_414781883076736 It merely depends on your requirements. 823a has longer range at night vision, higher resolution, more zooming power, made of Aluminium housing, more powerful spotlight and IR, better tracking, etc. So what are your requirements?

I have the first generation E1 OutDoor (OD) WIFI at the back of my house and it does its function marvelously. But if you opt for E1 OD make sure you purchase the latest POE version.

@rainman Have you done the last test I proposed?

@kristof As stated, the E1 AI Zoom has improved gear mechanism and never had to re-calibrate it or reset the guard point. This implies that they learnt from the first generation.

@kristof I have the new E1 Zoom with auto tracking and so far it always returned to the programmed guard point position. I have the previous E1 OD and yes occasionally it deviates from the original guard point position by 10 degrees or more. This is attributed to the non-precision gear mechanism and cannot be compensated by the firmware.

@d-rock-olive-stop_660487008608295 Follow this link
https://support.reolink.com/hc/en-us/articles/360008584054-How-to-Bind-Reolink-Cameras-to-the-Existing-Cloud-Account

@user_662456555880465_662456555880465 It is not coded to take arguments for sure as otherwise they would have stated.

But there are methods and applications which let you do this. Search for force-program-to-open-on-specific-monitor

@andreabelgrade_64088314033 Argus 2 can only connect to 2.4G Hz band. Ensure that this is readily available at the location where you are communicating with the camera. Red blinking means unable to connect over WIFI.

@rainman Then you are running on Android 13. Try the last test I proposed. Even though the download center shows your firmware, do email them as they might have never firmware which they haven't yet released. Normally they shall reply within 48 hours.

@rainman I am not a Reolink employee but supporting members wherever possible based on my engineering skills. It is clear that this has nothing to do with the detection zone and most probable it is a firmware issue. I do not see any further tests and so I suggest you to email Reolink support and include your hardware version and the tests you have conducted. I have no access to logs and they are limited. One last test please....... Can you install Reolink client on another smartphone and re-create the config from scratch for one of the DUOs and check it out? Are you on Android or IoS? If you are on Android there is a limitation on the number of push notifications per application. If I recall correctly this is limited to 24. In case of Android smartphone, when you click on the push notification of the camera through the client, the client registers with Google FCM (it stores the IP of the client) and the client receives a token. Then client forwards this token (you can see it from the system menu of client) to the Reolink application server receiving the push messages from cams. So when there is a person detection the camera sends a message to Reolink application server. This application server already knows the token (passed by client) and sends a trigger message request to Google FCM. This includes the token the client registered with FCM. FCM then uses this token to fetch the mobile profile (IP) and pushes the message to the smartphone. This is high level. It's complicated but that part we leave it to the troubleshooters :).

@user_654576976203821_654576976203821 So more than one complaint. And you have the same firmware? Try to ask Reolink for a newer firmware.

@user_662324213878856_662324213878856 Never heard of such an issue. This cam is not included in the Reolink download center and so I suggest you to email Reolink support and ask them if there is a newer firmware. Don't forget to include your HW version.

Re: Synching. Possible issues.

1. Is there any issue with mobile reachability where the Cam is installed? Do you have any issue to communicate with it from your smartphone? Will it connect immediately every time you try?
2. I do not see this as a smartphone issue. Can you install the Reolink client on another smartphone (if possible using a different mobile operator) and try again? If it works then swap the SIMs with your smartphone and try again.
3. Issues with the mobile operator serving your GO Plus cam. Can you insert another SIM preferably from another operator and try again? Ensure that you set the correct APN on the camera. Some mobile operators ignore erroneous APN entered by the customer and take the one the operator logs in his HLR/HSS. The operators with whom I worked have implemented this in their MME/SGSN.
4. If none of the above then do a request to Reolink support. Pity that there is no logs on the camera where one can check out.

@user_629911810629744_629911810629744 I see that this is still a bit early and would say that there are more important features to add before implementing this. This is my personal opinion.