Posts made by joseph_1979

@ste-dh_231699053183135 Kindly add your suggestions at https://community.reolink.com/topic/6233/survey-on-reolink-app-scene-mode?post_id=23852&_=1692783408907

@ste-dh_231699053183135 Kindly add your suggestions at https://community.reolink.com/topic/6233/survey-on-reolink-app-scene-mode?post_id=23852&_=1692783408907

@user_728982352179385_728982352179385 For this type of CMOS sensor, it needs a low light sensitivity of 0.0005lux to produce colour vision.

@derek-breydin_696784043594396 It might be that the CPU is getting overheated and shuts down. Just for testing. Do you have A/C? Can you put the doorbell in a cooled area?

@denis_403776597323975 The issue is not the network but rather the ftp server. Camera cannot create the directory or the directory specified doesn't exist. Make sure you grant write permission. Which ftp server are you using? Are you using ftp or ftps? Try to install the freeware cerberus ftp server to test it out. In the logs you can see where is the issue.

Ensure you give the create directory, write, etc rights. Hereunder is an excerpt from the logs. Note that despite that you use FTP, the camera requests FTPS (Explicit - through command AUTH TLS) and if the FTP server accepts it (enable a parameter in Cerberus) then the camera requests to continue using FTPS (TLSv1.2). Ensure ftp server supports the cipher ECDHE-RSA-AES256-GCM-SHA384 as cited below.

@riprengineer Do you have a POE switch? If so connect the camera to the POE switch and connect the swicth LAN port to the BB router. Use the Reolink client to add it using the UID of the camera. Then check that the HTTPS/HTTP are enabled.

@user_727999352516787_727999352516787 If you are on UMTS and HSPA you will encounter issues. You shall be fine if you are on HSPA+ and having a strong signal. You may reach the 25Mbps.

Irrespective where the client is located, it sends a DNS query to get the IPs of the P2P servers which are provided by Amazon and Microsoft. The client will then request the P2P servers to provide the local IP of the camera and a public IP on the P2P relay servers (Profile is identified by the UID). Note that you cannot connect directly between the camera and the client when the client is on an external network ( a number of ISPs refrain this data flow). So to avoid this Reolink will provide a public IP on the P2P relay server. The P2P server already knows the public IP/port of the BB router to which the camera is connected to. So a connection is setup between the P2P server and the camera. This is leg A. Leg B is the connection established between the client and the Public IP of the P2P relay server. So data flows from camera to P2P Relay server and from P2P relay server to the client. Conversely, from the client to P2P server and from P2P server to the camera.

And if you are technical, you can see this by capturing a trace using Wireshark on the PC running the client.

@user_727999352516787_727999352516787 I did explained in my articles the data flow between the client and the cameras when both entities are both on the same and different networks. When the AWS/Azure P2P relay servers are used, Reolink pays for the service and bandwidth allocated and subsequently whenever you start a live view from any camera which is external to the client, the stream is always FLUENT. You can change it to CLEAR but as soon as you click on the Playback and click again on the Live view, the stream starts again in FLUENT. Typically a 5MP camera requires a nominal bandwidth of 10Mbps.

So nothing is free and nothing is unlimited :).

@lillian-kurtsen_546083915727078 Are you using gmail account?

@derek-breydin_696784043594396 Another test would be to use the substream. I guess you are on the latest firmware.

I told support to implement logging and core dumps export to assist you in troubleshooting. This is what I used to do when deploying applications to customers.

@issom Then you need to open a ticket with support.

@riprengineer Go to Networks/Advanced/server settings. Check that HTTPS is enabled. If you want to use HTTP then enable HTTP too. Refused...means that you are reaching the camera but the service is not enabled.

Another test is to let the router assign the IP through DHCP. Remove any policy associated with its MAC address.

@cthreepoh_636415470858361 I have the Reolink TrackMix WIFI and I am able to connected through Chrome. The general rule is that battery operated cameras cannot be connected through a Web Browser.

@derek-breydin_696784043594396 I suggest you to re-open a ticket with Reolink support. Try to get the doorbell inside and repeat the scenario.

@neptune_654294262100039 Make sure that your version of pcm and wav files have the same characteristics as the ones generated by the Android reolink client. Install a professional sound editor like Gold wave and check the sampling frequency, A law or u law, the bit rate, signed or unsigned, bits, etc.

@bostjan-voje_495356353904818 Apply to be one of the testers. As for the WIFI issue try to use WIFI extenders with strong signals such as TP RE650.

@user_727999352516787_727999352516787 Read my comments at https://community.reolink.com/topic/87/how-does-the-reolink-uid-actually-work/3?post_id=22657&_=1692644814908 and https://community.reolink.com/topic/6240/software-windows-resolution-start-up?post_id=23966&_=1692644814917 respectively.

If there will be a limit which I have never tested out then it shall be per connection. I had never used 1GB per session on my Android smartphone to watch a single camera. So even if there will be 1GB then it will be more than adequate to watch through the smartphone.

Note that you will have issues to watch high def streams on HSPA (3G). You need at least 4G.

You can check this out. Run reolink Win client and connect to the camera from an external network (to use the P2P relay servers) and from the cmd prompt enter netstat -s -p udp and take note of the datagrams received. Leave the stream in high definition. The data included in each packet sent by the P2P server is 1350 bytes..........so you need to receive 1G/1350 datagrams :)...... say 4 to 5 days assuming 100 packets/sec

@grga-komadina_356799291056358 You're welcome.

@reolink-lorenz This is good news. Can you please provide the specs of the NVR? Thanks.

@das-dos_208145718501556 According the API v8 the following parameters are mandatory in command SetEnc.




And so the curl command should be as follows.

curl -s -k -X POST -H "Content-Type : application/json" -d "[{\"cmd": \"SetEnc\",\"action\": 0,\"param\": {\"Enc\": {\"channel\": 0,\"audio\": 1,\"mainStream\": {\"size\": \"2560*1920\",\"frameRate\": 20,\"bitRate\": 4096,\"profile\": \"High\"},\"subStream\": {\"size\": \"640*480\",\"frameRate\": 10,\"bitRate\": 256,\"profile\": \"High\"}}}" "https://#IP#/cgi-bin/api.cgi?cmd=SetEnc&user=#username#&password=#passwd#"

Please replace the IP with the cam IP and the username and passwd with your credentials.

And if it doesn't reboot you can reboot it using

curl -s -k -X POST -H "Content-Type : application/json" -d "[{\"cmd\":\"Reboot\",\"action\":0,\"param\":{}}]" "https://#IP#/cgi-bin/api.cgi?cmd=Reboot&user=#username#&password=#passwd#"