09-24-2022 12:43 AM
I'm glad I finally found the new Google nest connectivity functions of the home app.
As suspected, due to poor connectivity issues, I now have proof my ring doorbell is connecting through a mesh point really far away. The nest main hub is 10 feet away from the doorbell but it is choosing a device over 100ft away to connect to and getting poor results. Is there any way to force the ring doorbell onto the correct network device? Should I disconnect the mesh device while reinstalling the ring doorbell? Does ring understand there are two networks and choose the further one? Is there a better doorbell device to use with nest? I have multiple points that need Camera coverage.
Please help so I can enjoy all my devices again.
09-24-2022 08:06 AM
Hello @Conigliaro
WiFi client devices decide which access point to connect to when multiple choices are available on a common SSID (network name). They are supposed to scan for all available access points, measure the signal quality from each, and pick the one with the strongest signal. Unfortunately, some devices just start scanning and connect to the first one they hear from, which results in a random choice. They may even remember which one that was and skip the scanning step next time they are power cycled and just reconnect again. I don't know if that doorbell is doing that or not, but it's entirely possible.
So, all of that said, I would suggest powering off the mesh points other than the one you want that doorbell to connect to. That may cause it to switch to the closer one within a minute or two. If it doesn't, you might need to power cycle the doorbell first. If that still doesn't get it to switch, then I would try doing a reset and reconfiguration (all while the other Nest WiFi points are off). Hopefully, that will get it to start with the one you want and (hopefully) stay there.
However, it's possible the next time it is power cycled, it will end up connecting to a random point. If that happens, I would hope just powering off those other Nest WiFi points briefly would be enough to get it switched again.
In my own network, I have a Nest Hello doorbell, and it seems to at least do a proper scan and selection to get connected to a reasonable access point (I have Google WiFi, but from the client's perspective, it looks the same as Nest WiFi or any other multiple access point WiFi network).
09-26-2022 11:49 AM
Hey folks,
Thanks again for helping here, @MichaelP.
@Conigliaro, I hope you've got the answer you're looking for. If you're still in need of any assistance, feel free to let us know.
Best,
Mel
09-29-2022 12:05 PM
Hey everyone,
We just want to check if you have seen our response posted above. Let us know if you have additional questions, otherwise we'll be locking the thread.
Best,
Princess
09-29-2022 01:39 PM
My ring doorbell doesn't scan for wifi. It is setup upon initial installation. But my ring is not identifying between the mesh network which device is closer and once it's connected it stays that way. Is there anyway on the nest network I can boot a device off and see if it comes back to the proper wifi distributor?
09-30-2022 06:33 AM
Hello @Conigliaro
It is not possible to "boot" a device off of the WiFi network. Did you try the procedure I suggested earlier (unplug all of the access points other than the one you want it to connect to)?
10-01-2022 12:05 PM
Hey folks,
@MichaelP, appreciate your helpful responses.
@Conigliaro, chiming in to ensure everything is good here. Have you had the chance to try the suggestion above? If yes, how is it?
Best,
Mel
10-04-2022 12:24 PM
Hey there,
I wanted to follow up and see if you are still in need of any help. Please let me know if you are still having any concerns or questions from here, as I would be happy to take a closer look and assist you further.
Thanks,
Mel
10-05-2022 12:25 PM
Hi everyone,
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Thanks,
Mel