Assign a device to a specific eero

Does Powering Off Secondary Eeros work... and has the Direct Device Assignment issue been corrected?

Apologies to any and all for tolerating my neophyte comments. In switching to a new TV/Internet/Phone company last week the new service provider installed eero mesh equipment.  This was my first introduction to the mesh network concept; never heard of it before.  Speeds are now super fast (75 TO 90 Mbps now versus 3Mbps) and the eero gives me full signal in the whole house.  But I am unable to connect my Ambient Weather Station to the system.  It appears that I need to "power off" all the secondary hubs and connect to the primary eeri.    Bought a new Ring doorbell too and need to install tonight, but based on other comments above it looks like it might require the same "power off" process and it may not stay connected.  By following this process, has anyone had success in 1) getting the device (Ring, or weather station etc) to connect, and 2) have the device stay connected?  Technically I don't understand why the power down procedure should be needed, but does it actually work.  If its one mesh that has only one network name and wifi password why would these types of devices not connect? The lengthy comments regarding the inability to assign a device to the nearest eero hub seem to indiciate that this is still an issue.  Frustrated that all this super-duper new tech doesn't work as advertised, but not surprised.  Eero, has this been addressed yet and if not who do customers get you to care? 

a thousand times yes!

Couldn't agree more. Maybe now that Amazon owns them they'll have more resources to work with...? 

I'm afraid I agree with wonderdadto4's comment that as much as I love my eeros I couldn't possibly recommend them to anyone I know because of the fact that my devices/machines continue to connect to the wrong node.  My desktop, xbox and TV are getting 8Mbs from the eero across the house, when they get 50Mbs when I shutdown that node and they connect to the node in the same room.

I'm wondering if this isn't a feature request so much as a bug that Eero needs to fix.

Great to see this request in here too! My Chromecast stubbornly connects to an eero that is one floor up, some 30 feet away, instead of the one sitting literally 3 feet from it. Would love the ability to "pin" devices to specific eeros!

Also glad to see the suggestion here - I'm constantly battling with devices connecting to the wrong Eero in my house.   Because of this issue, I'm less inclined to enthusiastically recommend this product to friends when asked.  My car routinely connects with the furthest away eero, with the car and the eero app both showing poor signal connectivity as a result.  This is crazy, since I installed an eero in the garage specifically to ensure strong WiFi connectivity to the car.  At this point, I'm thinking this was a poor product choice.

@jeff_c dood give us some love 

Definitely a requirement.  I've found two of my WiFi cameras roaming to pods that are on the other side of the house.  This should be easy enough to allow the user to assign the device MAC address to the closest pod keeping from jumping around.

I STILL have the same issue.  The connections has gotten a lot better over the years but it is STILL an issue.  I have a Fire TV stick that is less than 10 Ft away from an eero and it wants to connect to a eero that's 30 Ft away.  I had to buy an ethernet adapter to plug it in to fix this issue.  Also, when on FaceTime and you move around, it has to "reconnect" or "poor connection" so I have to hang up and call back.  There isn't a GREAT handoff between eeros on the "mobile" devices.  It is very frustrating and I am thinking about going with a different router if this is the type of customer service / services we are getting.

Maybe I skimmed and missed this detail in the thread above, but is anyone having this problem on an eero network with NO Beacon access points (i.e. all Ethernet connected eero units)?

I have 4 Ethernet connected eeros and devices (mostly Apple laptops, iPhones and iPads) seem to roam to the most logical eero (closest proximity, least amount of building material to penetrate, etc.).

I do notice a lag in the data in the eero app, so I wonder if part of what people are seeing is incorrect/stale information about which eero a particular device is connected to?

One tweak I'd like to see in the eero app is in the list of devices you see when you tap the "nn connected devices" button in the Home screen. Is there a reason the eero to which each device is connected couldn't be shown in that list? For example, see image below:

So, I'm gonna throw a bit of information here that most users are not gonna like.

Eeros are limited by their backhaul usually - yes, that even means those eero Pros that are connected by ethernet backhaul (who "supposedly" use ethernet AND their dedicated WiFi backhaul when ethernet is employed). Backhaul that is NOT wired CAN suffer from placement issues - just as the devices you have in the home can't get good signal.

Many users (not all, don't @ me please) have the non-Pro versions of eero - which do not have a dedicated backhaul - they share the built-in wifi radio. So, when people like truman1404  is saying his baby monitor is connecting to a far-away eero "station" (as he calls it) he might not realize that the eero in the baby's room has the same flaws his baby monitor does. ie: if the baby monitor cannot get a "great" signal to the "station", then neither can the eero plugged into the wall in the same room. Eeros (including Pros and Beacons) are intended to be placed halfway between the station and the device needing the boost. Indeed the eero beacon plugged into that room will provide about half of the bandwidth even in the best of circumstances because it has to share the wifi radio between sending data to/from the monitor and to/from the eero "station".

For users having these issues with Pros, I totally feel your pain. I have Pros and have basically figured out that while we can all connect to any eero, yes, some devices connect to the farthest and cannot be coaxed to connect to the nearest.

The real issue of many eero networks can be backhaul bandwidth - as I've found out through tons of trial and error! My eero Pro system is separated  - as eero suggests. I happen to be able to put my gateway station in the exact center of the house, and I put one Pro halfway between the gateway and the left outer wall, the other halfway between the gateway and the right outer wall... so the distance between my left outer wall and my "left Pro" is roughly the same as between "left Pro" and the "gateway" - and the "gateway" is the same distance to my "right Pro" and the right outside wall.

This has worked well but has exposed a fatal flaw in ANY mesh network. 😉 Having this kind of coverage then "dares" you to saturate the backhaul since you have a strong signal everywhere. I have 37 devices (mostly IoT devices, but 9 AppleTV's OR Dish WiFi boxes) all over the house. BUT this morning I was watching my Dish Joey (WiFi connected remote TV box) which pulls it's signal from the Dish Hopper (WiFi) in the living room. That means the video signal was going from the Dish Hopper->WiFi to gateway eero->Backhaul to "left Pro"->WiFi to Joey. Since Hopper and Joey are on different Pros I thought I was okay. Then my husband opened up his laptop where the Joey was and started a file copy to the upstairs computer. This is how THAT went: Laptop->WiFi to "left Pro"->Backhaul to "gateway"->Ethernet to server computer. Immediately the Joey's screen began to pixelate and the copy crawled to a minimum. The Eero's WiFi backhaul was saturated!

Unfortunately even placing the Pros where Eero suggested didn't fix the backhaul-being-saturated situation...so I'm gonna have to ceiling mount them and run ethernet via attic for wired backhaul. Before anyone says "hey... what if the "left Pro"'s WiFi was saturated, please understand: I ran long ethernet cables between devices, plugged them in - and voila the tv-watching and file-copying didn't saturate...and no pixelation occurred. So, that's a project for next weekend.

I just want people to know that:

1: Beacons share WiFi bandwidth with your devices on that beacon - and no matter what, they'll reduce backhaul. Beacons are not meant to stretch the speed of the "gateway". They're meant to expand REACH of WiFi at the expense of speed.

2: The placement of all eeros - either Beacon or Pro - should split the difference between farthest WiFi device in your home and the gateway.

and...

3: It's not always the issue where a "bad" connection to a far-away "gateway" or "beacon" that may cause intermittent connections. It could be a saturated - or badly placed - eero, which means mesh won't work.

Please don't @ me to complain about "this isn't me...or you assumed this." I @'d one person because THAT beacon placement is definitely assuming something that eero doesn't want you to assume. ie: If you put a Beacon close to a device will help that device. The beacon has the same connection issues as that device when trying to reach the gateway.

My problem is that Chromecast and Eero seem to be nearly incompatible with each other. Yes, the Chromecast can connect, but when you're trying to stream something, the Chromescast is connected to 5Ghz while my phone connects to 2.4Ghz, and both are right next to the Eero. 

It's ridiculously frustrating not to be able to tell the Eero to anchor a device to that one and tell it to connect 5Ghz or 2.4Ghz. I've had my Eeros for about 2 years, but after 2 years of this issue where I can't get my phone to stream to multiple Chromecasts, I'm at my end with Eero. I love the concept, but I'm finding that the Eero simply isn't smart enough to handle a simple task. 

Am I missing a backstory between Eero and Google, because this seems like a simple thing that would fix a ton of our problems?

Oh, and here's a "fix" I found online. If you cycle from turning on and off your "Guest Access", it will sometimes force the devices on the same node. 

This is one of the last major pain points I have with EERO and have really contemplated switching. We have so many connected devices sprinkled throughout our home it becomes a big pain. When I get a FW update, SO many devices hop onto whatever EERO boots up the fastest and they often stick to it until I manually reboot them. It's such a pain that I've installed otherwise useless WiFi power outlets from Belkin to remedy instead of going around to each device one by one. This isn't possible with my doorbell however without killing utility room power where major appliances are also powered. 

What’s the update on this request Eero?  A little help after 2 year’s would be nice. 

Would love to see this ability too. I have a powerline adapter that I use for backhaul to a remote point, but other connections end up going through jt as well - when I just want my garage to use it

I agree with everyone here.  Why not allow the option?

+1 to needing the ability to assign devices to eeros. Surprised to see people have been asking for this for two years and no action. 

I’d be happy with even the inverse - the ability to temporarily/permanently blacklist devices from specific Eero devices and/or bands.  Some fixed devices (e.g. doorbell cams) I would never want to attempt to latch onto the opposite side, while other devices I would just want to not -stay- latched onto an AP after moving away. 

I have 3 Eero Pro devices (one on every level of the 3 level condo I live in).

This is an extremely important topic for me as well.  I have over 40 devices actively on my home network, between smart plugs, security cameras, echo devices, smart TVs, laptops, phones, tablets, etc.

Most of these devices, I cannot power cycle easily (video doorbells and security cameras), so it would be extremely advantageous to be able to direct them to a specific Eero Pro device as a primary connection point with the ability to failover to another Eero Pro beacon when the primary is either offline or being rebooted, etc.

I've had the Eero Pro Mesh Network for 2 weeks now and have experienced the Video Doorbell and security system devices disconnected from the network 4 times now in 2 weeks and having me to force a full reboot of the mesh network to reattach these devices.  Extremely inconvenient.