Posts made by Chopstix

@marian-siczek_715086104985814 can you Live View the camera fine? Playback features working? Did you reboot your iPhone after uninstall but before reinstall? As odd as it sounds, iPhones do need a reboot from time time.

If all else fails, open a ticket with Reolink Support. Have some patience as there may be a time difference depending where you are on the marble. Cheers.

@janser-dienstleistungen-gmbh_257000373518575 I am unable to reproduce this issue on client v8.17.6 on Windows 11. Are you certain that you manually deleted the camera from the app prior to adding the new camera that received the same DHCP address as the previous camera?

@reolink-system_824158258282663 That is a VERY broad question. Your installation specifics will dictate what screws to use. Camera to D20? Which camera? D20 to wall? If the ones that came with it are simply too long, take one to a hardware store and ask them if they carry a shorter one.

@marian-siczek_715086104985814 what version iOS? I am running the same version app on the same phone (13 Pro) iOS 18.3. Zero issues however I use a Home Hub Pro, not the RLN. I am scheduled to get iOS 18.3.1 this evening but not sure if that's your issue.

@ram_799163019051222 my Alexa/Google Home integration (I use Google) performance is dismal. The doorbell (and cameras) do not stream directly to the Alexa/Google device. Instead, the video feed streams to the Reolink P2P servers, which in turn streams to the Alex/Google servers, which then streams to your Alexa/Google device. In my case, that lends to approx 8 seconds of audio/video latency if it even connects at all. Needless to say, smart home integration is useless for me. According to support, the functionality is operating normally and the problem is with the connection performance with the Google servers.

Make sure that you have the Record Audio switch turned on. If that is already on (I assume it is) try turning the doorbell volume up... the doorbell's built-in mic should pickup your voice (as it is being played at the doorbell) and record it. That's is another problem I am having with mine... the doorbell mic picks up my voice and it gets played back during the conversation. So annoying. So what happens is, my voice gets recorded twice... once by me speaking into the app and a second time when it plays at the doorbell and get's picked up by the mic. This bug might actually help you. Give it a try.

@user_620089981972582_620089981972582 while not inconceivable, it is not likely that you received two bad doorbells. Can you elaborate it disconnects from your network? How exactly are you being notified/determining this? Have you check the Netgear forums to see if there is known firmware issue with Orbi? If feasible, can you temporality connect the doorbell directly to your main router?

@user_620089981972582_620089981972582 I am sure you have, but I will ask... did you make sure to turn ON the daisy chain setting?

@techgirl_849769519804666 thank you! Cheers!

@joseph_1979 Please let me know what they say. Cheers.

@joseph_1979 I did not make any changes to the band preference setting up until I attempted to switch to 2.4 GHz. I do recall it listing 5 GHz not Auto when I opened the page in the app. Definitely a bug then as it should not matter what option is selected. If you switch the setting, the camera should switch.

@Techgirl_849769519804666 what's up with the down vote on my comment above? If there is something about it that concerns you, please allow me the opportunity to address it. Thanks!

@joseph_1979 haha. Yeah, that's pretty much how it went.

@joseph_1979 let me clarify...

When I initially setup the doorbell months ago, I had the choice of 2.4 or 5 during the setup. Naturally, I chose 5 GHz. After deployment I noticed the signal meter (you and I already discussed how lacking this is) displayed 1-2 bars signal. I left it alone to see if there were performance issues. It was fine for several weeks then began to sporadically disconnect several times a day, but not every day.

Fast forward to this week, I decided to use the app and switch the preferred band to 2.4GHz because as we know, 2.4GHz has better wall penetration. Yes, the HHP should have automatically given the doorbell the 2.4GHz SSID/password during the switch. I don't know what exactly went wrong as the doorbell was not able to reconnect to the HHP after the switch. Without adequate network management tools in the HHP, I was unable to troubleshoot other than a reboot of both the doorbell and the HHP. I had to factory reset the doorbell and run the setup again, this time choosing the 2.4GHz SSID.

I have not tried switching back to 5 GHz as a test as I really do not want to factory reset again if the switch fails. I do not know if this was an isolated incident or a persistent bug but I thought it worth documenting.

@joseph_1979 IIRC, he spoke to support about this already and got nowhere with them. It reminds me of a doorbell issue I had with 2-ways comms... support was able to reproduce it but did not see a problem with it even though it made 2-way comms via the doorbell almost unusable.

@user_901203979997352_901203979997352 I agree. A doorbell 'ring' event and motion events need to have the ability to have separate schedules for BOTH Home Hub notifications and push notifications. I also would like to have 'ring' notifications 24x7 with only motion events triggering in the evening hours.

The more people that add comments to this thread showing interest, the better the chances that Reolink will implement the change.

@user_901203979997352_901203979997352 agreed, ring and motion notifications should have separate schedules for both Home Hub alerting as well as push notifications. While this won't help for push notifications, you can get a Reolink Chime that can serve as your 24/7 'ring' sound and then set the schedule based on monition events for the Home Hub. However, this only works if Reolink has updated the battery doorbell firmware to support simultaneous connections to a chime and a Home Hub. Currently (unless FW has been released) the battery doorbell can only connect to a chime -OR- to a Home Hub, not both.

EDIT: I removed your post from the Wish List as it comes across looking like a duplicate to this post. If you'd like a Wish List post, please post a new one that is simplified and direct with what you are asking for and then cross-reference to this post for more information. This will help avoid cluttering Wish List posts with community help responses. Thank you.

Even though my Wi-Fi doorbell is literally 1 wall/floor away from my Home Hub Pro, it only gets 2-bars on the 5 GHz signal meter. With sporadic disconnects several times a day, I finally decided to switch it to 2.4 GHz.

I went into the app, to the camera's Wi-Fi settings and switched it to 2.4 GHz. The app did not ask me for a network name or password. I assume because the camera is connected to the Home Hub Pro's 5 GHz radio, it SHOULD know to switch it to the HHP's 2.4 GHz radio.

Well, the camera did not want to reconnect. Rebooted the camera and the HHP, no dice. So I ultimately had to factory reset the doorbell and connect it to the HHP's 2.4 GHz during the initial setup. Good new is, it's showing 4 bars on the signal now.

So it makes me wonder if there is a firmware bug since it did not automatically switch from the HHP's 5 GHz to 2.4 GHz nor did it ask me for new network SSID/password when switching. Hmmm.

@fireflynj_236912991023352 the camera that does not have it, do you have another of the same model that does?

@user_917140252860649_917140252860649 can you shoot a video of what is happening and post it here? Maybe I am not wrapping my head around what you have going on. Either way, Reolink support is going to likely ask you for a video anyhow. You reach them by summitting a trouble ticket via their support page.

@kevinkss give as an update when you can. Cheers.

@joseph_1979 I have run into this as well, fortunately we get a good amount of wildlife running across the far edge of the FOV so it has not been an issue. I was actually surprised when I saw the scheduled reboot option... why? Why does it need to reboot? Memory leak? Reminds me of Windows NT 3.51 Server back in the day.

Anyhow, I can't imagine that Reolink is not aware of this. It would be nice if they gave an option NOT to reboot the Wi-Fi processor.