Posts made by joseph_1979

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

@neptune_654294262100039 Take note of the last created file and replace it with yours. Then click on Save from the appl. to upload the file.

@neptune_654294262100039 After you recorded the announcement test it but do not save it so that it will not be uploaded to the doorbell. Check under folder /picures/reolink/ or the cache at /android/data/com.mcu.reolink

@das-dos_208145718501556 I wholly agree in the absence of MQTT, matter and IFTTT. This is quite simple to implement.

@issom Check that you have the most updated firmware. From the camera read the fw version under info menu. Then go to Reolink Download Center and check the latest fw for your model. If this is newer download it and use the Windows client to upgrade the fw.

@user_727993210269845_727993210269845 Well RTSP entails for a constant stream and so producing one from a wireless camera requires the feed 24/7. The solar panel don't produce enough power to run a continuously transmitting camera. But even though the solar panel did produce enough power to run during the day, then you need a high capacity battery to having run during the night. And this comes at a cost.

@ddbezz_471681375514826 Which client version are you running?

@koach_401182455079094 It seems to be a known issue and shall be solved in the next upgrade.

@user_728057623986395_728057623986395 Both are applications, one refers to Reolink PC Client application (Reolink Client) and the other to Reolink Smartphone Client application (Reolink appl).

In computing terms the difference between application and client is that application is a computer program or the set of software that the end user perceives as a single entity as a tool for a well-defined purpose (also called: application program; application software) while client is the role of a computer application or system that requests and/or consumes the services provided by another having the role of server.

@chengteo123_695830319439873 Have a look at https://reolink.com/blog/connect-raspberry-pi-to-ip-cameras/

@user_720596590145789_720596590145789 This is coming in the scene mode feature. Reolink shall be adding a scheduler to the scene mode. We have been asking for quite some time.

@matt-bruman_695767958503581 Use this link https://home-cdn.reolink.us/files/client/electron-release/reolink_setup_8.11.0.exe

I suggest you to email support. I don't have the fish eye and so I can't help you.

@user_727607713124599_727607713124599 Take note of the UID from the info menu. Connect a cat5/6 cable between your camera and the BB router. Now setup a hotspot on your smartphone and get the ssid and password. Now from the camera select the hotspot. Now switch off hotspot and add the camera using the UID you got from the info menu. If you are able to add it and watch live view then your communication is through the LAN port. E1 OD despite it is WIFI cam, it can be connected via the LAN port.

Note that the camera will always try to connect to the last connected SSID.