@user_750102319055027_750102319055027 +1 on using larger sensors on reolink cameras. willing to pay the premium for higher quality images.

It would be amazing and much more intuitive and user-friendly if the doorbell push alerts had the option to include an attached image of the actual event captured at that moment, or a short video segment of the motion alert when the doorbell button push/motion video was triggered.

Right now it is very cumbersome and time consuming to bring up the playback/history and have to track down the motion or scroll through to the correct time when the alert happened in order to view it. Especially since the alert pops up on our phones in almost-realtime, but then it takes so much time to track the image/video segment down to see it. Please make this more intuitive.

Making the alerts more user friendly/accessible by giving them context via a linked image/video in real-time just makes sense.

And it will certainly capture more market share for the reolink doorbell than any other feature, since it would be the most useful enhancement that all users would see.

From a performance perspective, the image/video that accompanies the phone alert would not have to be the highest resolution. It could be compressed or resized to optimize transmission.

This trigger option is already available via email....an alert can be emailed with a screenshot attached, for that moment in time. Just asking reolink to implement this same concept via the alert messaging on our phones.

It would be amazing and much more intuitive and user-friendly if the doorbell push alerts had the option to include an attached image of the actual event captured at that moment, or a short video segment of the motion alert when the doorbell button push/motion video was triggered.

Right now it is very cumbersome and time consuming to bring up the playback/history and have to track down the motion or scroll through to the correct time when the alert happened in order to view it. Especially since the alert pops up on our phones in almost-realtime, but then it takes so much time to track the image/video segment down to see it. Please make this more intuitive.

Making the alerts more user friendly/accessible by giving them context via a linked image/video in real-time just makes sense.

And it will certainly capture more market share for the reolink doorbell than any other feature, since it would be the most useful enhancement that all users would see.

From a performance perspective, the image/video that accompanies the phone alert would not have to be the highest resolution. It could be compressed or resized to optimize transmission.

This trigger option is already available via email....an alert can be emailed with a screenshot attached, for that moment in time. Just asking reolink to implement this same concept via the alert messaging on our phones.

@user_750102319055027_750102319055027 +1 on using larger sensors on reolink cameras. willing to pay the premium for higher quality images.

@axdrew_746904040513741 I would reach out directly to support, or maybe a moderator will have the answer...

Would be nice if Reolink added this to their specifications, whether a camera will only work with Reolink NVR's or if it can work independently.

RLC-81PA is one of the newest 8MP camera in the Reolink line up.

Have you confirmed that this camera will work without a Reolink NVR?

Most of the Reolink cameras that are 8MP or above (even if they have a TF slot) will only be accessible through a Reolink NVR which acts as a proprietary hub for these high data-stream cameras. I assume this is done intentionally so they can grow their eco-system and buy-in of their product line From a technical perspective, I am guessing that the NVR is acting as a hardware decoder to stream the h.265 compressed signal, to optimize the experience for users when doing a live view over cellular or wifi (the assumption is that not everyone carries the latest android or iphone that can decode h.265)

The older 5MP or below cameras ARE accessible directly via an IP address, but they typically stream h.264

@mike_201907_662346852388871 what you want to buy is a simple 5 port POE switch with 802.3at/af support. That's pretty much any POE switch on the market today.

There are many many POE switches on amazon, including say a 5 port fast ethernet switch like this one, that supports 10/100 Mbps (you don't need a gigabit POE switch for reolink products, but you can certainly buy one for $10 more if you want to future-proof).



Plug the non-POE ethernet data-only cable into PORT 5, then plug the other two ethernet lines running to the 811A and reolink doorbell into any of the other remaining ports on this same POE switch (you'll be able to plug in 2 more POE or non-POE devices into the remaining 2 open ports in the future).

When you plug the data-only ethernet into your main switch, which should also have the Reolink NVR plugged into it -- then the NVR will pick up the doorbell and 811A and assign them to whatever empty channels you have left on the NVR.

What's implied above, is that reolink cameras do not have to be directly connected to the reolink NVR. As long as the data from the camera can reach the NVR, the NVR will recognize the camera.

Conversely, as long as the camera eventually gets POE to it so it can operate (from either a short distance or from far away), AND the camera is on the same network, the NVR will pickup the camera. The reolink NVR just makes it easier by having a built-in POE switch in it already.

Your issue though is distance of 150m. Max transmission is 100m/328ft for Cat5e/6. So you will need to put some sort of switch (regular or POE) to act as an extender within 100m of the gate. You don't need anything special other than another switch to boost that data signal. (Pro-tip: Use solid core 100% copper cabling for long distances, not CCA (copper-clad aluminum) and definitely not any stranded cable; also Cat6 is better, because the min specs provide for thicker gauge wire than Cat5e)

Depending on distance, you might be able to run long data lines directly from the main switch (if its closer to the gate than the NVR), or run a single data line to another regular 5 port switch, which will act as the extender to the two data-only lines to the 811A and doorbell areas, then have two single-port POE injector wall-warts (about $20 each), nearer to each camera, then simply run a short POE cable to each camera from each of these POE wall-warts.

@big_ted so can the POE version of the doorbell be powered off a 16V AC transformer (like a chime transformer of a regular doorbell), and just have a regular data ethernet cable plugged in, instead of using POE?

@joseph_1979 thank you for the youtube link. excellent idea!

@avperede_213931771191537 Communication between the doorbell and the chime is via radio signals operating at 433MHz. So when the button is pressed a message comprisings of 1s and 0s is modulated either in PWM or PMM and transmitted over radio signal operating at 433.92 MHz. The receiver in the chime decodes the message and sounds its buzzer.

Before using the chime with the doorbell you need to pair them.

Thank you for the clarification! Interesting that a WIFI signal is not used here.

Can I ask what the measured open-air distance is for this 433MHz signal being issued by the doorbell that's being sent to the buzzer/chime? There must be some specs on this listed somewhere.

Is there a 433Mhz repeater (any recommendations?) that can be installed between the doorbell location and the buzzer/chime. I have a distance of 500ft from one end of the building to the other to cover.

My cordless phones work about 1/2 that distance, which is why I was looking for a better solution using a video doorbell.

Appreciated.

Need some clarity on the Doorbell (POE version) and the corresponding buzzer that is plugged into a wall outlet...

Do both have to be on the same (WIFI) network, or can I plug the buzzer into a completely separate building (different network), than the Doorbell portion?

Are the two units (doorbell camera and buzzer) bound together via a QR code?

Or does the buzzer need to be on the same network as the doorbell?

I'd like to report the same issue when we updated to Windows client 8.14.0

The PTZ and other controls that fade-in/fade-out when you hover at the bottom of a screen are not appearing on one of the laptops that I have the Windows 8.14.0 client installed on.

On my main desktop computer, this hover bar displays correctly, just fine.

Running Windows 10 on all the machines.

The laptop where this does not work, has a screen resolution of 1600 x 900.
The computer where this work, has a resolution of 4k.

On a separate note, I think somewhere after version 8.5.2, the "Fluent" (Low) image quality dropped dramatically dropped, and is now quite fuzzy,