Assign a device to a specific eero
I was recently going through my connected device list and noticed I have some of my devices connected to an eero which isn't the closest one to it. Wouldn't it make more sense to bind a device to a specific eero? For example, my Ring doorbell is maybe 10 - 15 feet from the closest eero but it is connected to one upstairs and further away. Not sure if that would cause a QoS kind of issue but for stationary devices I don't see them moving from one eero to another (Nest products, Amazon Echo, Ring doorbell, etc.)
Well, I figured out how to make the ring camera work correctly. Stupid solution, but for now it seems to work. I moved the bedroom eero to a plug on the other side of the ring doorbell. it's 5 feet from the main hub, so it's obviously not the best setup, but it now is the closest hub to doorbell, AND it's the hub the damn doorbell seems to want to connect to. the ring doorbell is happy now, me not so much. hopefully some day EERO will get it's act together and let you choose which hub you want devices that do not move around to actually connect to.
Similar to your situation tfederov and stormyweather I have a different brand of doorbell camera (Skybell) that requires at least 90% signal strength according to the manufacturer, but just because I put a new Eero node just 5 feet away from it doesn't mean it will seek it out. The doorbell's network stack seems perfectly complacent to stay connected to the node that's 50 feet away on another floor at 71%, and then not stream video on demand because the connection isn't strong enough.
I get what Eero is saying... having devices constantly checking for a stronger signal and hopping around doesn't make sense when the Eero it's already connected to is "fine" (especially since sometimes there's a brief interruption in service during the transfer) but I wish I could go into the app and ask a specific Eero node to take over the connection. Sometimes these devices do need to be micromanaged to work properly.
I have a potential solution to this issue that is kinda lame to be honest. I have hated this forever, like most of you. It seems that eero can not solve this issue, but I think I have come up with something -- hear me out. I have several old routhers sitting around as most of you probably do. Most of the IOT stuff requires a 2.4GHz signal which is older and much of my older gear works on the 2.4GHz spectrum. So here is my weak solution -- I turn off DHCP on and old router and name the SSID to "mySSID-IOT" I plug the upstream connection into the eero to provide DHCP services. I then connect the IOT stuff to this IOT SSID. In my case, I have two of these setup, "IOT1" and "IOT2". This way the stupid IOT stuff like cameras and doorbells has no choice but to connect to the node that we tell them to. Like I said, its lame and may cost you some $$ (wrt54gs on ebay are like free now), but it does solve the problem.
I love eero but this is one that seriously bugs me. How many years later and this feature still isn't added? This could be a firmware update. A 'smart check' if the user enables that allows eero to do a connection check at say 3am or whatever time the user sets. Or the user assigns the MAC address to a certain node. It can be done.