Posts made by joseph_1979

@das-dos_208145718501556 Oops sorry to hear that it didn't work. Let me check it on my camera.

@railfan-arizona_485965826351268 So the P2P Relay servers (provided by AWS/Azure) are not being updated with the cameras IPs since it is also happening with 8.8.5. Stockton may be using a different P2P server and the camera is constantly sending the HB packets. Can you ask someone to power off/on one of the cameras and check again?

They need to listen to us, the genuine customers. The application is not that massive (like a mobile network which requires a full 12 months of intensive testing :)), just set a test list and voila'.

@das-dos_208145718501556 Only the Initial was enough to know what is missing. So we need to add the I-Frame interval parameter gop.

Check again :).

curl -s -k -X POST -H "Content-Type : application/json" -d "[{\"cmd": \"SetEnc\",\"action\": 0,\"param\": {\"Enc\": {\"channel\": 0,\"audio\": 1,\"mainStream\": {\"size\": \"3840*2160\",\"frameRate\": 25,\"bitRate\": 8192,\"gop\": 2,\"profile\": \"High\"},\"subStream\": {\"size\": \"640*360\",\"frameRate\": 15,\"bitRate\": 512,\"gop\": 4,\"profile\": \"High\"}}}" "https://192.168.X.X/cgi-bin/api.cgi?cmd=SetEnc&user=#username#&password=#passwd#"

BTW what's the model?

@das-dos_208145718501556 It's more simpler and robust. I do have a number of Linux machines G10 in VM/OpenStack.........but no MAC/IOS :).

@das-dos_208145718501556 They should improve the API by adding appropriate error codes and update the API doc if there are changes. The error indicates that we have a missing parameter. So we need to get the printout first. Maybe we need to add gop.

Send this to get what need to be included. You should get the initial (default) and the one set (Value)

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

Don't worry about the private IP 172.16. 0.0 to 172.31. 255.255 (class B)....nobody will be able to access this IP from the Internet side.

@user_685202497601687_685202497601687 All Battery-Powered Cameras (incl. Argus Series, Go Series, Dual-Lens Battery Cameras, and Keen Ranger PT), E1 Series, and Reolink Lumus are supported by the cloud service.

@user_646203682046022_646203682046022 Have you communicated with Reolink support? We don't have the code and so cannot delve further about the buffers reserved and released by the applications. Typical error with programmers.

@issom Appreciate if you keep us updated. Thanks.

@user_729891662233741_729891662233741 Correct. But has to be fixed.

@railfan-arizona_485965826351268 Good. If I have the code I would have fixed it :). After you capture the traces change the password of the cameras as this will be included in the trace (encrypted for you) :).

@das-dos_208145718501556 ha haha I did that purposely for you to fix and I replied when I was having a bottle of fine wine with my friends...........Joking. I missed an escape character \. Try now. Replace the size, frame rate and bitrate with the appropriate values given in the stream menu. just follow the command in the API v8 doc provided by Reolink.

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#"

@riprengineer Agree. So you are an engineer too :).

@user_587919500296214_587919500296214 Win 10 or 11? PC running client is on the same network as cameras? 8.8.5 is a 32 bit client while 8.1X.Y is 64 bit.

@user_728982352179385_728982352179385 Better that you get the answer from Reolink who are the manufacturer of these cams. Send them an email.

@michel_659661158359130 We, European, have different mentality :).

@user_729406293795015_729406293795015 I do agree with your proposals. It will be evaluated by the dev team and will put it in a priority list if they agree to implement. They need to listen more to us, the customers, and implement what the customers want, of course. assuming it's a great suggestion. This is all software and can be easily implemented. I know because I am a developer too.

@michel_659661158359130 It uses the 433MHz receiver and standard protocol. It's pity that Reolink doesn't produce additional chimes.

@user_729461963661506_729461963661506 So before updating the firmware of RLC 520A, the camera was able to ftp the file to Synology, right? Has there been any update on the Synology side which changed the file management part?

@user_728982352179385_728982352179385 Have a look at an independent evaluator. https://www.youtube.com/watch?v=PtQLgdGmpOQ

@railfan-arizona_485965826351268 Definitely. Would you be able to capture a wireshark trace on the client side and forward it to Reolink Support? This will help them identify the issue. I only have 8 cameras and maybe issue crops up when there are more cameras.