Hi Reolink Team,

I did capture some traces at both the RLC511WA and the Client sides and noticed that the all the packets transmitted by the camera have reached the clients. You have a byte denoting the packet number. When the playback was set to low, the video preview was smooth and the sound was continuous. This means that at low resolution setting the camera was able to transmit the packets at a CBR with no packet loss or delays between packets.

Then I changed the resolution to CLEAR and despite that there were no missing packets, the video can be seen sometimes freezing and the sound chopped. This is apparent when there is movement in both live and previews. There was no issue of bandwidth at all and both the source and the target were on the same subnet. Thence the issue is at source. It could be inefficient H264 encoding (I guess software encoding is used) at high resolution or hardware issue. I also noticed that the max downloading speed for FTP is 1.2Mbps. This is low especially when you are on the same subnet.

I even changed the bit rate for 5Mbps with the recommended value of 1536kbps but didn't observe any improvements.

I checked another model, the Argus 2 and the same issue has been observed at high resolution. Appreciate if the engineering team check and get back to us with their findings.

Regards,
Joseph

Hello,

In this chat there are a lot of fantastic ideas and it would be great that these are somehow collected in a table and Reolink support give a follow up say every week. Customers wish to know what is being done on each proposed suggestion or issue. Informing customers that your suggestion will be forwarded to the engineering team is not enough. Customers have to be constantly updated. And one must give some proposed dates of implementation. Reolink engineering team has to be aggressive in implementing new functions and sorting out bugs. Other suppliers takes this seriously and sort out issues quicker. We are here not just to complain but to improve your products and support.

@reolink-fiona Surely that the team has to prioritize and evaluate their implementation. This is what I do at work. But at least there is the list with the time lines and updates. Listening is not enough. Customers seek action.

@reolink-fiona And kindly let us know the resolution, vit rate and fps when the display mode 'med' is selected.

@reolink-fiona Please include the latest firmware of E1 outdoor in the download centre. Even though there are different hw versions, just add them. How can I know which is the latest version of my E1 outdoor?

@reolink-fiona Well all you need to add the HW version and according the selected HW version you show the associated firmware. I have IPC_523SD8. You are already doing this for other cameras like E1 zoom.

@joseph-chircop_497308027822318 I did purchase one for testing before commiting to buy additional cams. The auto tracking needs refinement and sometimes it fails to follow the person especially if the person hurries a bit. Sometimes it misses the object despite that the sensitivity is high and the smart detection set to medium. Will ask support to investigate though I suspect that such cameras are no longer given the appropriate attention after more than a year on the market.

@reolink-fiona Can you please include the latest firmware for the E1 outdoor? Any reason why this has been left out from the drop down list?

@ra44 thanks a lot for your feedback. Definitely it is plastic as otherwise the price will be much higher and becomes less competitive. But I cannot understand why they left out the IP rating which according to support is IP64. Still I see people complaining that sometimes camera fails to return to the default guard position. Nevertheless I ordered one and will evaluate it before installing others to a number of sites.

@faasio82_480971996033257 wait for next firmware update. They really need to improve in testing both hw and sw before launching the product to the public. I has the sane issues with RLC511WA but now after teo firmware updates miat issues have been fixed. You need to wait for 3 to 6 months....

@reolink-fiona I am aware of this. We need a list so we can check who has accessed the camera. And it should be read only abd cannot be modified or deleted not even by the admin.

Can you ask the appl dev team to try to add the logging of the remote IP together with the timestamp in a list which the customer can check? A list of the last 20 accesses shall suffice.

Customers may be too much hectic in their routine and sometimes forget to check their cameras. There may be instances where the camera fails for one reason or another or it may be stolen and when it is really required then evidence is not available. Can you devise a heart beat mechanism between the camera and your host server and if the camera misses say 5 heart beats then a message/email will be sent to the customer? A lot of equipment employs such mechanism like for example IP PBX which sends the OPTIONS message and the peer server replies with 200 OK or 403 Forbidden. If there is no reply then this means that the SIP trunk is out of order. Think of it.....maybe you will be one of the first to introduce.