Posts made by joseph_1979

@keithsrobertson Thanks and appreciated.

@keithsrobertson Excellent. Can you please report it to Reolink support citing your graphic driver version? This seems to be one of the big problems with this client.

@keithsrobertson Did you get the same issue with ver 8.8.2? Can you switch on the hardware decoding first and try to take another snapshot? My Argus 3 Pro is on the same firmware and have no issue. For sure its the interaction between the client and the graphic drivers.

@user_594027275649135_594027275649135 You're welcome. Reolink support notified.

@user_594027275649135_594027275649135 After rebooting the dynamic settings in the camera (ordered by the client to forward stream) are lost and the application is unaware of what happened at source (camera). So there will be no streaming towards the client and the client doesn't check the stream. I think Reolink should monitor the stream and if no more packets are reaching the client, it shall re-activate the recording. So for the moment I suggest you to inhibit the rebooting at the camera side.

@robert-hammond_315369854550200 This is rather the protocol between the client and the camera and has nothing to do with the recordings. It seems that the client was unable to get the play list. Can I suggest you something please? If the issue re-occurs can you please capture a wireshark trace and forward it to Reolink support (you can filter on the IP of the PC and that of the camera). They shall identify and correct the issue. But as stated I have been using 8.10beta for quite some time and nothing similar ever cropped up.

@user_594027275649135_594027275649135 I never encountered this in any client I have used so far including the 8.10beta. However, please note that if the cameras came as a kit....then you won't be able to add them using UID as this is not assigned during production. But you stated that you were able to add them using a very old Windows client. So there shouldn't be any issue with newer clients. Could be something left in the pc while installing and uninstalling. Try to uninstall it and delete the reolink folder under appl data/roaming. Did you try to watch the cam through the browser (cams not battery operated)? You need to activate http and use port forwarding on the router.

@nellywadman_540141701607677 Did you email Reolink support who will direct you to their sales representatives?

@donnarnich_409809414480058 No specific power cord. Just check whether the AC side of the adapter is C7 (figure of eight) or C5.

@daz_58170128017 You have a point here. It plays all clips for the day and thereafter stops even though there are clips in the following days. This happens on Android client too. It should be added. Support notified.

@keithsrobertson The issue has nothing to do with the camera but rather the client and the graphic driver. I guess this will not occur if you take a snapshot using the Windows snipping tool. Can you try it? Did you get the same outcome with version 8.8.2?

@glenn-tracy_460916285792453 You need to install them independently and setting different chimes.

Communication between the doorbell and the chime is achieved through 433GHz channel. Most probably a proprietary protocol.

What I really wish to see is allowing customers to use their existing chime similar to what Ring offers and to use SIP calling to call your smartphone. I see these two features as a must have if Reolink want to compete with its competitors in the doorbell market.

@robert-hammond_315369854550200 I have been using the 8.10beta since it was made available by Fiona and haven't encountered such an issue. Which cameras are connected to the client?

@curls This is what I am hoping too. Should be great if this will be implemented.

@user_594027275649135_594027275649135 uninstall the reolink client you have on the home pc and download the 8.10beta. The link is provided in a topic 8.10beta.

@baltimorehomewholesalers_260895649677480 We have already provided the procedure several times. Please do a search on hardware acceleration and follow it.

@user_638479359111285_638479359111285 There is the 8.10beta version which I am using and so far just a few minor issues. But never tried to download files greater than 700MB. It could be the client stopped acknowledging the data packets (1350 bytes) sent by the camera. In the ack you can see the block number (2 bytes). Can you capture a wireshark trace and sent it to Reolink support so that they will see why the file download failed? Sent the last part as the initial shall contain the credentials (encrypted) :).

I guess you are on the same WIFI network as the cams which shall present less problems. What's the max download speed when the file is being transferred?

@petetas_516117592592546 well it could be a cloud issue if you confirm that there was no issue with viewing videos on the SD. Note that cam stores two files for each recording, one for clear and one for fluent.

@user_638196684865537_638196684865537 if no fibre or copper is available then a 4G router will do the job.

@jim_113753456251131 Good. When I read it I immediately thought of HTTP/S being restricted from cam side.