Posts made by Crimp On_62210811129

@melroy I am not confident that Reolink software engineers monitor the user forums. My guess is that the answer is "can't be done". The mobile app works the way it does, and no other way.

As the article referenced explains, a device opening a port to a remote server creates a link that the remote server can use to communicate with the device.
My impression is that when a customer opens the Reolink smartphone app, the app connects to the cloud and uses the customer login credentials to scan the database for UIDs registered to that user who have open links to the server. If the connection is not already open, then the server has no idea which IP address any particular device may be related to.
Only cameras that have connected to the server with their UID can be opened with the app.

Opening a port on a customer router for remote access (i.e. port forwarding), does not restrict access to any particular IP address on the internet. For example, the Reolink RLC cameras include a web server that provides a way to view the camera video. If a user forwarded an external port on their router to port 80 (or 443) on a camera on the local LAN, then they could access that camera remotely. (provided that they can supply the correct user name/password.) This does not scale well, because every camera would need a separate external port linked to their internal IP address.

What a cool idea. If Reolink supported using IFTTT to make cameras start recording, then all sorts of switches could make this happen. Have not seen an IFTTT motion detector, but without the integration there's not much point in looking.

@christian-meneghini_543174703677572 Have tried to post a screen shot. "Undefined" my a***

@christian-meneghini_543174703677572 Windows Client has that feature:

on the General Settings.

@christian-meneghini_543174703677572 Windows Client has that feature:

@user_671416932614237_671416932614237 Oh, geez.

Do we have the same camera?

Model: RLC-1212A
Build No: build 22032880
Hardware: IPC_523B1812MP
Config: v3.1.0.0
Firmware: v3.1.0.902_22032880
Details: IPC_523B1812MPS18E1W011000000001

@bertdebondt_312190272442529 I have no NVR. All cameras are individually accessed by the Windows Client v8.10.4.

My experience is slightly different. When switching from Live view to Playback view, the tiny resolution indicator in the lower left of the screen may display "Low" (Fluent). Once it is changed from Low to High (Clear), it will remain High if the view is switched back and forth between Live view and Playback view. I can switch to another camera. When I come back to the origiinal camera, the resolutions remains "High".

However, if I drag a camera over to the viewing window while the window is in Playback mode, then the Client gets confused. Resolution shows up as "Low" and the Client thinks the live view remains the original camera.

I've spend several minutes working changing cameras back and forth, views back and forth, etc. What appears to be the situation is that changing cameras while the window is in Live view works correctly and not when the window is in Playback view.

@waynewillis88_388564343382234 Windows Client 8.10.4 on my Windows 10 desktop does not exhibit these issues, i.e.

1. The "split" button in the lower right works as usual.
2. The volume control slider works as usual.
3. The camera icons appear along the bottom of the Live View as usual. (I do not have a camera with PTZ.)

None of my cameras are on an NVR. Perhaps that might explain the difference?

@user_671416932614237_671416932614237 I have an RLC-1212A with "Clear" stream set to 4096x2784. The digital zoom works. (Although the newest Wiindows Client 8.10.4 is not pleasant to watch while zooming because of the "black flashes" as it zooms.)

@joseph_1979 Great Response. The Reolink mobile app (Apple or Android) functions because each camera opens a connection through the home network to the Reolink "cloud" and registers the UID of the camera in the cloud. The app connects to the Reolink cloud and uses that connection path that is already open.

The Client (Windows or Mac) typically relies on knowing the IP address of each camera. As a quick "double check", record the IP address of every camera. Are they all in the same "IP Subnet"? i.e., the first three numbers are the same, such as 192.168.1 ?

To enable email notification, the user's email credentials need to be entered into the app:

• The URL of the vendor email server. I use GMail, so it is smtp(dot)gmail(dot)com (sorry, we cannot include URLs in forum responses)
• The SMTP port (Gmail says to use 465)
• A "Friendly Name" for the sender (to appear on the email message)
• The email address that the message will come from.
• The password to that email address. (Google requires an "application password")
• The email address that the message will be sent to.

Yahoo should have information on how to send messages through Yahoo.

The Reolink user ID/password are not part of sending email notifications.

@jfbaro_664228245382261 I think "no". This camera has a single antenna. MIMO requires more than one antenna. For example, the Reolink Duo 4G has two antennas.

@ed_682671253913811 The microphone appears to be on the bottom, aft of the QR code. A tiny hole.
There's an unboxing video on the Amazon product page that mentions the microphone. ( I would include a URL, but of course we are not permitted to post URLs.)

@crimp-on_62210811129 Downloaded Reolink Client 8.10.3 from Reolink(dot)com. (The only version on the web site.) Installed on HP Laptop, Windows 11 Pro. First time it opened, "There is a new version" (sigh. At least now I have two download files and can swap versions any time I want.) Found all my cameras automatically.

The effect is not as pronounced on the laptop. (Still present, but not nearly as extreme.)

The effect seems to vary depending on whether the Client is running "full screen" or partial screen. (that symbol in the upper right corner of the app) Full screen seems to be more prone to the problem than partial screen. Also noticed on the laptop that zooming ALL the way OUT will create black bars on each side of the picture for several cameras (on the laptop). Does not seem to do this on the desktop.

This has got to be a nightmare to program. The user can:

• Run the program "Full Screen" or partial screen.
• The list of cameras on the left can be visible or hidden.
• When not full screen, the client window can be stretched vertically, horizontally, and diagonally. OMG!

@joseph_1979 Thanks for attempting to duplicate this effect. It most pronounced with Clear resulution, especially on the 12MB camera. After your report, I experimented some more.

• The effect is especially visible when scrolling the mouse wheel quickly.
• When the mouse wheel is clicked slowly, one deliberate click at a time, it almost never happens.
• This happens even with the Argus 3 Pro and the (very first original) Argus battery cameras.
• 
  

Thus, is appears to be related to "timing", i.e. when the mouse wheel moves in relation to the video feed. The Argus 3 Pro takes about 22 'clicks' to zoom from normal to maximum zoom. One or two of those clicks will produce a very quick "black blip". The 12MB camera is very much the same. Going from normal picture to maximum zoom is about 22-23 mouse clicks. Done very s-l-o-w-l-y, the picture is very stable. Zoom quickly, and it will happen a 2-3 times. Puzzling that it will happen "at the extreme", when the picture is completely zoomed in (or out). Scrolling the mouse wheel should not do anything, except it does.

I will also try Windows 11.

Thanks for posting about 8.10.4 The update went smoothly and kept all cameras. However, the "black blink" remains when zooming a Live View.

In Live View, the mouse scroll wheel can be used to digitally zoom the picture. Once the magnification has changed, the mouse can be used to select different parts of the picture. With 8.10.2, 3, and 4, these activities cause the picture to "blink" with totally black screens. Very distracting. Even if the Live View is at the maximum zoom (in or out. either extreme), using the mouse wheel continues to make the screen "blink".

Windows 10, 64-bit.

So true. That Reolink multi-cable is truly unique. It is "part of" the camera in the sense of "hanging out the back side of the camera.". Battery powered cameras usually have a "Reset" capability built into the main case.

Most of my Reolink RLC cameras have a physical "Reset" button on the camera itself.

This morning 8.10.2 announced, "New Software Available" (8.10.3). Did the update, program restarted and again said, "New Software Available"

The spot light feature appears when mousing over a Live Feed. (Have no cameras with Zoom feature.)

My first thought it to wind it into a loop pressed against the back of the panel and secure it with duct tape that matches the color of the back of the solar panel.