theflamingonion 

That wouldn't work - that is what it does today. Devices connect to the first Eero node that accepts connections after a reboot - which is almost always not the closest Eero. Once connected, the devices won't connect to a stronger signal until disconnected and allowed to reconnect. I have over 70 iOT devices in my home. Imagine the pain of restarting that many devices after the Eero reboots!

I did solve the problem with my cameras by having them all powered from a smart plug which I can then power off and power back on from my phone. This takes care of 8 out of the 70!

Come on Eeero - it has been a very long time since this high-priority issue was raised. Surely, you guys could have solved this by now using one of the solutions I proposed above? Give me access to your source code <grin> and I will gladly do it for you for free.

PhoenixRevived FYI: I've also had some luck by adding devices to a Family Profile, pausing that profile, then unpausing. Some of my devices seem to reconnect to a different Eero when I go through those steps.

mzman Interesting. I will have to try that next time the network reboots.

kmacsandiego —

Thanks for checking in. Our team is always watching the discussion and gauging interest in potnetial new features. At this time, I don't have any update to share regarding this specific feature, but we will update this thread should there be any update.

dvogt The problem with this suggestion is that many devices need to be on the same SSID to keep functionality. 

diejoh There are many folks on this thread having similar problems.  This may not be the solution to every problem, but I suspect that it would solve the issues that most people face.  For example, streaming video from your apple tv or fire stick just needs a reliable connection (for most people anyways).  If eero isn't willing (or able) to make a change that fixes everything, yet perhaps can put in a much simpler fix that solves 80-90% of day to day issues, isn't that something that has value?  This is of course all academic anyways since none of us controls what eero can/will do ;)

diejoh What devices require the same SSID? As long as they are on the same network (i.e. the same controller is providing DHCP, routing, same IP range, etc) it shouldn't matter. No different from a hardwired connection to an eero vs. wireless connection. Think of a device specific SSID as the same as a hardwired device.

It would solve the problem, at least mine.

ifermon dvogt

You would think it shouldn’t matter but it does, and we get into the limitations of other devices. Philips Hue, for example, needs to be on the same SSID or you’ll have intermittent connectivity from iOS and Amazon Echos. I’m having this issue with my Nest Hello doorbell where it connects to a further Eero at only 2.4GHz, as though there is no band-steering and it ignores the closest eero even though there are no more obstructions and it has connected at 5GHz before to the closest Eero with a decent signal. Eero also suffers from the “sticky client” problem where it won’t release a device to connect to a closer Eero with a stronger signal. Anyway, device limitations shouldn’t matter because they’re designed to be used on a functioning wireless network, and Eero has problems that others have solved long ago. It’s the wireless access points that should handle all of this properly, and as we can all agree, Eero is not doing its job right now. I hope they fix this. Also, creating multiple SSID’s degrades performance because you’re taking the same radios and splitting them, so there’s another reason to stick with a single SSID. 

diejoh I don't understand the mechanism by which a device could distinguish that other devices are on a different SSID. I've never heard of a problem like this before.

As for "splitting radios", I don't believe the radio gets split in any physical sense by adding SSIDs. I believe all that matters is how many frames traverse the radio, not what SSID they connect.

Am I wrong?

mzman I would never say I know everything, but I do manage a large enterprise network and we have 30 Meraki access points. According to Cisco  / Meraki, they advise not broadcasting too many SSID’s because you will degrade performance. The point of having different SSID’s is to route traffic with different settings, like having a Guest network isolated outside of your main network. It makes sense that broadcasting multiple SSID’s cuts signal strength compared to having all radios broadcasting one SSID. Whatever the radios are doing outside of serving the SSID you’re connected to is going to impact performance, but it might not be enough to bother. 

The main issue here is that Eero users want better performance and we shouldn’t need to have workarounds - it should just work. Eero could have double the radios but without using them properly it’s still not going to solve the issues we’re all having. I really hope this is fixable with a firmware update. 

diejoh I have the Nest Hello Doorbell and it is 8' away from the ERRO Pro in my living room....The Nest operates best when connected to the 2.4Ghz band, at least thats what the Nest people tell me....However, my house is 2400sqft.....I was worried that the 3 ERROs would cause conflict and not allow the devices to switch properly because of overlapping signals....they get confused.....My Nest 95% of the time connects to the 5.0gHz band in the living room and shows up orange with 2 of 5 bands.....I still have video and it works fine although I wish I could set a separate IP for it to connect to 2.4Ghz.........it occasionally connects to the 2.4gHz  and has full 5 green bands......so with the overlapping bands, it is probably why the Nest Hello is having problems connecting when it is too close the the eero pro.....I am going to try and move the living room eero pro across the room 18’ away and see if it will connect to the 2.4gHz band......that may be my problem.....they cant be too close to the device..... 

eerosucker While I am very disappointed by Eero's responsiveness, I am still holding out hope that they will do something about this issue. I have suggested technical solutions and even offered to implement them for free. Not sure what else I can do as a customer with 5 Eero nodes.

truman1404 Yeah, that's a drag. It could be the baby monitor though, and is it 5GHz and just chooses to connect to the further one at 2.4GHz? That was the same issue I was having with my Nest Hello doorbell, but lately it's started connecting to the nearest Eero at 5GHz all of the sudden. (Although last night it disconnected - maybe there was an Eero update that I wasn't told about?) 

Happy6069.......I have the Nest Hello Doorbell and it is 8' away from the ERRO Pro in my living room....The Nest operates best when connected to the 2.4Ghz band, at least thats what the Nest people tell me....However, my house is 2400sqft.....I was worried that the 3 ERROs would cause conflict and not allow the devices to switch properly because of overlapping signals....they get confused.....My Nest 95% of the time connects to the 5.0gHz band in the living room and shows up orange with 2 of 5 bands.....I still have video and it works fine although I wish I could set a separate IP for it to connect to 2.4Ghz.........it occasionally connects to the 2.4gHz  and has full 5 green bands......so with the overlapping bands, it is probably why the Nest Hello is having problems connecting when it is too close the the eero pro.....I am going to try and move the living room eero pro across the room 18’ away and see if it will connect to the 2.4gHz band......that may be my problem.....they cant be too close to the device.....