Posts made by joseph_1979

@dukekernEither a DHCP problem or the UID is not enabled. Check the UID first in the INFO menu.

Check also Sync NTP to see if it’s successful. On the NVR monitor, go to Network>Advanced, then click NTP Settings. Click Synchronize to sync the NVR date and time to a remote NTP server immediately (hope you didn't change the default one....if not there use pool(dot)ntp(dot)org and port 123). If it’s unsuccessful, that means the NVR isn’t connected to the internet.

Replace (dot) with .

@dan-stefani_360688865751271 Which plan you have purchased? The free plan allows only one camera to be bound to the cloud.

@smipoint_474817079943397 I agree but as you can see there is a new firmware. So the previous one might have had a bug. At the parliament they say....take it as read...or read point 8 of the description file..ha ha

@user_658824716533794_658824716533794 It seems so. Maybe they have discovered a major bug when using specific function. I have upgraded mine too and haven't encountered any issue. Do you have the previous version (1459)? If so try to apply it. I normally keep all the firmware on my notebook.

If you don't then I suggest you to restore it. Press the reset button (only for Doorbell WiFi) to restore your camera to factory default settings. You should reinitialize the doorbell.

@anelson_650167144510283 Check that your NVR is on the latest firmware and ensure that the file has been closed. Did you try to backup the file to the USB? Would you consider to restart the NVR and try again? Maybe the filehandle is still seized by the OS or not properly closed. Try to use the CUT rather than download and try to connect to the same network.

Have you ever reported it to the support? I think I saw this issue somewhere and I thought this has been resolved. I do not know whether this is a firmware or client issue.

@smipoint_474817079943397 But this was there a few days ago. Maybe they discovered a bug and they removed it. Try to email support.

@roars_516256824365201 A Lithium-ion battery cannot be overcharged because the charger includes overcharge protection. Charging will automatically stop when the battery reaches 100% capacity. But if the battery is left charging constantly, this can cause damage that will reduce the performance and service life of the battery. So the best option is to have a socket Programmable Switch Timer (less than 20 bucks) and program it to switch on say twice a week depending on how much the battery drains. 

@reolink-fiona It will be highly appreciated if we are informed about any planned maintenance which in one way or another will impact the functionality of the security system. I can understand that it is not always possible to provide redundancy to mitigate service intervention. You have our email address and therefore you can notify us.

@user_679874117488786_679874117488786 Check that HTTP (80)/HTTPS(443) ports are enabled. Go to Network, Advanced and setup.

@user_681684260421764_681684260421764 Yes, the POE cable should be run trough a hole at the back of the camera. This is the normal practice with all doorbells. However, you may use the 15 degrees wedge provided (to avoid damaging the camera). With a drill and appropriate drill bit do a hole at the bottom of the wedge. Try to use a grommet to avoid moisture entering inside if this is installed outside.

@user_659075606552663_659075606552663 I suggest you to email Reolink support so that they will check your profile.

@Fiona. Yesterday I noticed that at around 15:30 CET all the cameras stopped sending push message notifications but was able to view both live and playback clips without any issue. So my conclusion was either Google's FCM servers or Reolink application servers which receive the alarm from the cameras and push the message notification to the FCM. However, when I arrived home I did some tracing and found out that the client was registering with FCM and forwarded the token to your Appl servers........but client was not receiving the message through FCM.

If the maintenance work is planned then I would suggest you to either send an email to the customers or else to put it on your website. This shall mitigate people from wasting time trying to troubleshoot an issue which is not at their end.

Note also that the token from FCM is no longer being displayed under the SYSTEM menu. Can they fix it up please?

@tsparks428_436084292944004 Should be under specs of the cam.

@md Yes they seem to have an issue on the message handling servers at their site. We manage to log on our cameras because the P2P servers are provided by AWS and Azure. Outage started at 15:30 CET time.

Thanks for the clarification. I am not on site as otherwise I would have traced the message flow and would see what is happening.

Update at 06:45 CET. Push message notification has resumed normal operation on all cams. This was attributed to maintenance work on the application server handling the push notification towards FCM/APNS.

@joelanders85_541485231984826 Normally they reply within 24 hours.

@joelanders85_541485231984826 This is a firmware functionality. So if the client will not detect it then it will not display it. Unfortunately I never had an RLC510.

Did you email Reolink support?

@user_597493679579258_597493679579258 This could have been implemented if they continued to produce the smart plug and add more ifttt functionality.

@br0kk_364437421093061 Better. Keep reminding on daily basis.

@tsparks428_436084292944004 If I recall correctly the C1 Pro can support up to 64G. Try to get a 64G or 32G and try again.

@joelanders85_541485231984826 The Reolink cameras will automatically drop the frame rate to 12 fps during the nighttime to ensure enough exposure time. However, that might result in an overexposed image or "ghost image" sometimes. To solve this problem, you can set a fixed frame rate for your camera to make the image clearer at night.