As mention in my last post, I knocked the FPS down to 18 and left a newly fomatted 2GB gb SD card in it. This morning the lag was still there, display video at least 20 seconds behind the action. Granted the 2GB card is pretty old so today I dug through my stash and found one of these so I stuck it in. (seems pretty bad if a currently released DB camera requires a SD seems to function properly) but if it works I'll be happy. I even did a DB reset (reset button on the back of the camera) and redid the configuration again. Granted its not designed to run on a off brand NVR... but still. Did a little research and in addition to resoution and data rate it seems brightness settings can also have an effect on video lag. Thinking I might take the DB off auto and try adjusting brightness manually. Until then I'll give the system a day to see if the newer SD card does the trick. Will check back tomorrow... up to my ears in the bathroom remodel.
The SD Card is not required. Only reason I mentioned it incase it was somehow putting a strain on the CPU of the DB. We had one guy in our DB1 Thread who used his SD Card to record 24/7 which he had a problem viewing too.As mention in my last post, I knocked the FPS down to 18 and left a newly fomatted 2GB gb SD card in it. This morning the lag was still there, display video at least 20 seconds behind the action. Granted the 2GB card is pretty old so today I dug through my stash and found one of these so I stuck it in. (seems pretty bad if a currently released DB camera requires a SD seems to function properly) but if it works I'll be happy. I even did a DB reset (reset button on the back of the camera) and redid the configuration again. Granted its not designed to run on a off brand NVR... but still. Did a little research and in addition to resoution and data rate it seems brightness settings can also have an effect on video lag. Thinking I might take the DB off auto and try adjusting brightness manually. Until then I'll give the system a day to see if the newer SD card does the trick. Will check back tomorrow... up to my ears in the bathroom remodel.
These would of saved you a bunch of time, they just became available:
"reolink doorbell mount" 3D Models to Print - yeggi
10000+ "reolink doorbell mount" printable 3D Models. Every Day new 3D Models from all over the World. Click to find the best Results for reolink doorbell mount Models for your 3D Printer.www.yeggi.com
So I have purchased two Tablet mounts from Joseph here:Hmmm yep that would have been a time saver for sure. And I took the doorbell off and held it against the included wedge. I definitely want to put that piece in my install now that I have seen the view it produces. I have seen 3D prints before and the plastic is rather rough surfaced. At least the ones I saw. Can they be printed smooth to somewhat match the plastic of the DB housing? There are a few print places for me locally, so I'll be asking them the same thing. Just wondering if anyone has any experience.
I would assume yes, there are small post sticking up to align them. My two wedges fit good.Do you know if the included wedge mount could be used in addition to one of those printed mounts? (Printables)
thinking of :
either "Reolink Doorbell Straight Wedge With Integrated Cover" or "Reolink Doorbell Straight Wedge With Integrated Oval Cover" directly against my wall (so that the concrete sealant can be hidden)
then the included 15 deg wedge
and then the doorbell itself
Or should a single piece just be printed consisting of the straight with cover and the 15 deg wedge.
Sounds like you are on top of your issue. I would say this is the right Thread, your post will help others and we know this is a growing Thread due to the popularity of the ReoLink DB but IMO one Thread is better than searching many.I was debating starting a new thread for the Wifi version but I read this whole thread (it is REALLY long) and it seems as though this has become a place for both.
For reference here is my DB info:
Was setup using the MobileApp (scanned the QR code). DB has access to the internet since I was using Reolink's mobile app for alerts for now. It is on an isolated VLAN from the rest of my network. BI does have access to the DB VLAN.
- ModelReolink Video Doorbell WiFi
- Build No.build 22102806
- Hardware No.DB_566128M5MP_W
- Config Versionv3.0.0.0
- Firmware Versionv3.0.0.1459_22102806
- DetailsDB_566128M5MP_WS10E1W7110000000
Currently the DB is in my office 8 ft away from the AP so there should be no Wifi issues. Using Unifi equipment and I can stream to multiple TVs many rooms away from my AP with no problems so should not be a wifi issue (but never know). I am also troubleshooting during the day when no other traffic just in case.
I have been struggling with many "NoSignal". I tried both the RTSP and RTMP settings that were recommended and neither helped.
Here are some other things I noticed to see if others are having similar issues:
1. The web UI (browser window connected directly to the camera) was very slow connecting at times (not consistent). Even bringing up the login page could take a minute.
2. Reolink Mobile app (on the phone) was better but could lag at times as well.
3, Trying to replay video from SD card would almost always cause the camera to disconnect (NoSignal in Blue Iris).
4. Many times the web UI would actually crash (not respond) while actively navigating through the menus.
Since the topic of SD cards came up I do have one in there and decided to pull it for now and see if that helps. SD card I had in there is this one which I used in other cameras with no problems. At first I thought it helped but it did not.
I only open the Web UI when I catch BI dropped the connection to the DB to see if I can still access it. Was trying to see if it was BI or DB. Mobile app was rarely used and only if I wanted to quickly look at a motion clip from my phone (originally had DB at my front door from when I ordered it).
It "seems" as most of the drops are during or after motion but can't say that with certainty. It's almost seems like the camera can't handle/process things. I wish I could monitor the DB stats (cpu/memory/etc.).
I just ordered a new SD card based on David's recommendation in a previous post and it should be coming tomorrow. I already ordered before I saw that the SD card isn't the issue.
Anyone else having issues with Wifi version? I can start a new post if it makes sense. Unfortunately my return window closed otherwise I'd just exchange it thinking I may have a defective one. Will try the ethernet port next to see if any difference but I can't run a cable to my front door so that won't be a solution just a temporary troubleshooting measure.
Thanks
So there are several more things you can do/check. Sorry but I went the TP-Link Enterprise route, I could not afford Unifi My AP is the EAP660 but found I cannot ping from it like I can from my switches so I was not sure if you can from your AP. Not sure why they don't have ping on their APs, sure helped me with my switches, not bandwidth wise but VLAN and Routing wise.Forgot to mention that I also have the same BI settings as you and was also thinking it was NOT BI. However, I am new to BI so didn't want to rule out any user errors I may be doing in BI.
And as I came back here to type the previous line, sure enough, there was a NoSignal and I was able to capture the ping at that time.
So the average responses for a few minutes were always 2 or 3 ms. Then here is when it I got the NoSignal in BI:
5/4/2023 12:05:32 PM - Reply from 192.168.10.105: bytes=32 time=3ms TTL=63
5/4/2023 12:05:33 PM - Reply from 192.168.10.105: bytes=32 time=2ms TTL=63
5/4/2023 12:05:38 PM - Request timed out.
5/4/2023 12:05:43 PM - Request timed out.
5/4/2023 12:05:48 PM - Request timed out.
5/4/2023 12:05:53 PM - Request timed out.
5/4/2023 12:05:58 PM - Request timed out.
5/4/2023 12:06:03 PM - Request timed out.
5/4/2023 12:06:04 PM - Reply from 192.168.10.105: bytes=32 time=4ms TTL=63
5/4/2023 12:06:05 PM - Reply from 192.168.10.105: bytes=32 time=2ms TTL=63
5/4/2023 12:06:06 PM - Reply from 192.168.10.105: bytes=32 time=2ms TTL=63
5/4/2023 12:06:07 PM - Reply from 192.168.10.105: bytes=32 time=2ms TTL=63
So it was not responsive for about 30 seconds and then came back and was quick again.
I am currently setting up two more Wifi cameras I just bought. I hate Wifi but they were only $25 and I just wanted to play around plus put one pointing at my woodstove to monitor the temperature when in the office. LOL
Anyway, I'm thinking I'll set them up and then do ping captures on all 3 devices and see if it is a network issue or device issue.
I'm open to other suggestions as well if anyone has any.
Oh one last thing, the pings were from the BI box to the DB. I never did a ping capture from an AP to a device so I'll have to look that up when I have a chance. I have Unifi AP's in case anyone knows or has a link to instructions.
Thanks again in advance.