Posts made by joseph_1979

@tomyafxone_262709326098680 Disable 'Hardware Decoding First' from 'Settings' in top right. Close appl and re-run appl.

@dylantkline_629871480078705 It has been temporarily pulled out from the download center. Most probably they are finalising the final 'stable' version.

@tsparks428_436084292944004 Which model? Can you try the same SD on a similar model if you have one? You may format it on PC (FAT32) and do a health check with the tool H2testw (freeware). Try to transfer a file on it and see if you can delete it. It may be the slot is somehow damaged.

@fredericneveux_352399457841348 Check here https://support.reolink.com/hc/en-us/articles/900000584903-Which-Cameras-can-Work-with-Reolink-NVR/

@albator_681579469856921A number of members including myself have requested the addition of a schedule to the spot light similar to what is available for siren.

@dale_655815670124636 Good. Which model you have installed?

@timothy_373498679251097 Add it to eSATA port. This is one way of expanding its recording capacity.

@user_679217629425876_679217629425876 Same here. No issues so far.

@user_682672180703446_682672180703446 Better that you stay with the firmware it came with until a stable one is uploaded in the download center. I am on version 2017 which has been removed.

I think not enough time is allocated to testing or there isn't enough of resources.

@quizzical Uh........... again!! Perhaps more issues. Have no idea of what is happening.

@fiona Can you please let us know what is happening on the doorbell firmware? It seems to have been pulled out twice in the last 2 days.

@user_666824588787835_666824588787835 Of course CLEAR should provide the best clarity view but this is at the expense of more bandwidth, efficient transport (radio and physical paths) and processing power at both end points. So for CLEAR set RES to max, fps to max and bit rate to max. Same for the Fluent. However, if you have issues in sound or display then you need to lower these parameters. As for anti-flicker set it as per your mains frequency....if in Europe 50Hz.

And ensure you have a subscription with unlimited packet data if the camera is triggered frequently and the videos are transferred to the cloud.

So if you will be viewing the camera for 30 minutes in clear mode@4M and 1 hour in Fluent@384K per day then you will consume around 1 GB daily.

To ensure you have adequate bandwidth install the Ookla Speedtest from play store (Android) and check the Upload and Download speed at both your location and at the farm. Note that from the camera what is important is the upload speed and from the smartphone the download speed.

@user_666824588787835_666824588787835 To configure it follow this link https://support.reolink.com/hc/en-us/articles/9332229200665-Configuration-Reolink-Go-PT-Plus/

If the sound is choppy then there is an issue at transport layer. This could be the case of low 4G reception at the camera site or client side if this is running on a smartphone. Try to lower the resolution and see if the sound is continuous.

If you are running the Android client, click on the three lines at the top left hand side.......... go to settings and disable password.

@maxm Try Germany at https://reolink.com/de/product/reolink-video-doorbell/

@jedi2020_32727772450952 Good choice :).

@user_679217629425876_679217629425876 New firmware 2017 added. I updated the doorbell and so far no issue.

@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.