Calion I have exactly the same problem. Have 3 x Eero 6 Plus and was looking forward to improved latency for all devices around the house. I've noticed that my latency increases considerably when I enable the feature, so I've basically turned it off. I'm now using my Eeros as AP's and reconnected my Ubiquiti Edgerouter X to do the SQM for me.  I'm sure something is wrong with the firmware as it has such good reviews historically. 

Can I get an official response on this? The basic reason I was excited about getting an Eero simply isn’t working.

Calion If you have a 6 model, the feature is really bad. It's VERY good on the 2nd gen model though (non wi-fi 6).

eerofan Harumph. Yes, I have a 6. 

My fear is that this feature isn’t designed for downloading at all. Here’s the description:

>Optimize for Conferencing and Gaming makes the most difference with wifi activities that require high bandwidth and low latency. For example, when you’re streaming 4K video while also browsing the web or playing a video game. While Optimize for Conferencing and Gaming ensures every device still has bandwidth access, you may see slower performance on certain devices. 

Nothing about downloading, just streaming. So perhaps the Eero doesn’t know to deprioritize downloads.

td76 never happened to me in the past 8 years.  My devices always reconnect with no intervention.   I would call eero directly to troubleshoot further.

HTH

Sdworman they reconnect but not always to the same eero. Devices will reconnect to the first available eero. I have 4 total eeros so it's really working as designed

td76 correct.  Devices will connect to the best available eero based on the best path to get back out to the internet.  This is how mesh works.

Sdworman eero is supposed to maintain the best connection across the network and it's devices. Eventually, most devices switch back to the eero it was previously connected to and identified as it's best connection. Reboots don't retain this connection information. It's a request many others have made. We all know how mesh works. The system also knows what device was previously connected, when, and to which eero. There are even Alexa integration features that depend on locating a device based on the eero is connected or nearest. A system reboot should reconnect the devices as previously done. 

td76 this is not how mesh is designed.  A device connects to the best possible eero in this case for the fastest route.  The wifi network is never constant.  It will always be dynamic.

Yes, eero knows what was connected previously.  Eero also checks the SNR and decides what the best eero will be for the device.  Every vendor does this.

Now chosing between 2.4 and 5.0 is something eero should work to change.  Turning off 2.4  completely will get rid of most if not all the network congestion.

Sdworman you're just insistent on repeating your same statements. On a reboot, they do not connect to the best device they reconnect to the first. They later correct in most cases. Please stop replying when you don't understand I'm not saying it isn't working as designed but how it could be working since each eero device logs its connected devices and connection history.  

Sdworman this has actually been a long discussion over many years with the eero team and community. https://community.eero.com/t/80zzmb/choosing-specific-nodes-for-devices

td76 and https://community.eero.com/t/m2m9k2

td76 I'm reiterating what has been discussed over and over.  Not even sure why you posted this to start.  It is working by design.

Sdworman no, you're just being obstinate. If you read the other long threads, this is a long standing request. eeros know the difference between roaming and static device types such as mobile phones vs appliances that will never move between nodes. Having static devices paired to certain nodes would not be difficult programming. This forum also by design is to request features to improve issues or performance. There are many threads discussing issues that are 'working as designed' as this is a forum to discuss and give feedback of features at the request of eero. Many features in labs and other software updates have been 'redesigned' due to such feedback. In the tech world, 'Working as designed' often doesn't mean 'Working as intended' or 'Working as it could' Again, if you read the thread, eero has acknowledged the request.

Sdworman additionally, eero has already acknowledged in other threads regarding this the static devices should never roam. They should always reconnect to the closest node vs the first available. Several suggestions to ensure this actually happens have included assigning static fixed devices to specifc nodes, wait for all nodes to come online before processing connection requests, periodically check if static devices are indeed connected to the closest node as there are already intended to connect to.

td76 Obstinate - wow big words...  This is not how roaming works.  There is no such thing as a static device.  This is not even a network term.  

Sdworman OMG. Static device vs roaming. Device types are assignable in the app such as 'appliances categories' 'Garage doors ' etc. These means they are non roaming devices\they will never move in the location and will maintain distance to\ from nodes. Again, eeror's own replies mention static devices should only reconnect to their closest nodes.

danoutlaw3 especially since the app knows the device types that will never if rarely move. Why would 'washer\dryer' or any other fixed devices including those you mentioned be assigned to a further node on a reboot\etc? Room for improvement.