@joseph_1979 I checked at the doorbell and it's getting 18.7v

I'm looking for anyone that has a Reolink WiFi Doorbell and is using it with an NVR that is accessing the stream 24/7.

I have the doorbell, and several other Reolink cameras, that I use with my Frigate/go2rtc/Coral NVR setup. I also use Uptime Kuma to check the health of my devices by accessing the web interface.

What I have discovered is that 5+ times per day the doorbell becomes unresponsive for several minutes and eventually reboots itself. I've been watching the stream a couple of times when this happens and went downstairs to check the doorbell and it was completely unresponsive. No light, button does nothing, completely dead. I like my Reolink devices and want to help resolve this issue in case others are experiencing it.

If you're not monitoring the health of your devices you might not even notice this is happening. Also, if you are not accessing a stream 24/7 you likely won't have this issue as I've turned off the 24/7 pull of the stream and didn't see the device reboot during that time.

If someone is using a setup like this and would like to at least validate that I'm not alone please let me know.

Thanks,

Tony

@joseph_1979 I spend much of my day at my home office. I have a triple monitor setup that includes a monitor with all of my cameras displayed. I notice when a camera fails and often go to the Reolink app to access the camera. I am assuming it has locked up because the times that I've gone down to the front door and checked it the device was non responsive. No light, no doorbell ring when pressed, etc. The uptime monitoring app checks the web access URL every 30 seconds and indicates when there is no response. Those indications correspond with the times I've seen the video freeze or garble.

I am assuming at this point that when the video stops and the web interface is inaccessible, as well as access via the app, that the doorbell has locked up and some watchdog process eventually reboots it. Fortunately it DOES reboot and come back online. This is the second unit I've had that exhibits this behavior so I don't have high hopes that a 3rd unit will solve my issue but I suppose it doesn't hurt to try. Other than the unreliable Reolink implementation of RTSP ( I use the http method of capturing video ), I'm quite pleased with the other 5 Reolink cameras .

A recent development with my 510WA camera. The web interface and http video feed for frigate stop working but the windows client can still connect and display the video feed fine. Anyone else have this issue?

@derek-breydin_696784043594396 I'm about ready to start looking at other brands, at least for a doorbell camera. I've been happy with Reolink overall but the doorbell has been a real disappointment, at least when it comes to frigate. Not sure what the story would be if I didn't use frigate but that's not an option.

@user_705200027504800_705200027504800 Interesting. I didn't even think about the heat being an issue. It did seem more stable when I brought it into the house and tested. But, It hasn't been that hot here during the time I've been experiencing the issue. It's been in the 70f-85f or so here. Still makes me wonder if you might be onto something. BTW, I don't typically use RTSP as I've read that Reolink's implementation is not very good. So I use the http stream instead. I do this with all of my Reolink cameras.

I should also not that this is the only reolink camera I have issues with. I have 5 other cameras ( 2 diff models ) running 24/7 with zero issues. I do wish there was a way to grab some diagnostic data when these things crash. Would make it WAY easier to troubleshoot.

@joseph_1979 I posed this in a new thread, but thought I'd let you know.

A simple way to determine if you would have the same issue I'm seeing.

Open the stream in VLC and leave it running. When I did this it locked up fairly quickly and the VLC player stopped at the time of lock up. So possibly no need for a separate uptime tool.

I used fmt: http://192.168.50.60/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=***&password=***

Ok, got an update. No need to install frigate, nvr, etc.

Just open the stream with VLC and leave it running. You may not even need an uptime monitor to detect if this is happening. My doorbell locked up within 30 minutes and the stream on VLC was frozen at the time it locked up.

I used this format, but I've had similar issues with RTSP as well.

http://192.168.50.60/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=xxx

I'm looking for anyone that has a Reolink WiFi Doorbell and is using it with an NVR that is accessing the stream 24/7.

I have the doorbell, and several other Reolink cameras, that I use with my Frigate/go2rtc/Coral NVR setup. I also use Uptime Kuma to check the health of my devices by accessing the web interface.

What I have discovered is that 5+ times per day the doorbell becomes unresponsive for several minutes and eventually reboots itself. I've been watching the stream a couple of times when this happens and went downstairs to check the doorbell and it was completely unresponsive. No light, button does nothing, completely dead. I like my Reolink devices and want to help resolve this issue in case others are experiencing it.

If you're not monitoring the health of your devices you might not even notice this is happening. Also, if you are not accessing a stream 24/7 you likely won't have this issue as I've turned off the 24/7 pull of the stream and didn't see the device reboot during that time.

If someone is using a setup like this and would like to at least validate that I'm not alone please let me know.

Thanks,

Tony

I've seen comments about this issue on a couple of youtube videos like this one. https://youtu.be/XXoTH1-78iA?t=880

Darn, wish this would have been avail a few weeks ago when I made my switch to Reolink.

@perkins-tony_647500713214819 Support said they were unable to recreate the issue. I'm surprised at this because I was able to recreate the issue 3 times with 3 different doorbells. I'm not sure they actually set one up as I have it.

If you have time and would like to help resolve this, could you set up a frigate/go2rtc instance and configure it to pull a stream from the doorbell 24/7. Also, set up a monitoring tool to detect when the web interface becomes unavailable. This will indicate when the device has locked up. I would bet you a cup of coffee if you do this you will see the device reboot at least 5 times per day. I would be curious to see if this happens with the reolink nvr pulling the stream as well.

Thanks,

Tony

@perkins-tony_647500713214819 I've engaged support. I did try one other experiment and I believe I've found what contributes to the issue and why many others aren't seeing this problem. IF I remove the doorbell from my frigate/go2rtc setup so that I'm not streaming from the device 24/7, it doesn't appear to lock up and reboot. Well, at least for the last 21 hours it hasn't. And since it was rebooting about 5 times per day I'm guess this is the issue. The device is incapable of providing a reliable 24/7 video/audio stream. I've passed that info along to support and hopefully we can resolve this. My setup is designed to be completely local and leverages google coral for detection, so I need the 24/7 stream, which the 5 other Reolink cameras are doing without issue.