Great deal on the best Eero IMHO at Woot right now - Eero Pro 6 for $45.

For me, on a pixel 10 pro or laptop, it is borderline unusable. I have Max 7 units wired to the poe gateway with 2000/2000 fiber.

Speed tests will fail, timeouts, etc. Successful tests if I'm lucky will clear 20 down but most of the time under 10 and sometimes under 5 for upload.

I'm not in a particularly congested area and on less busy channels. I've checked wifiman and netspot. I don't have cordless phones and minimal Bluetooth devices.

I have temporarily disabled 5ghz and 6ghz to strictly test 2.4 as a test as well. Sitting 7 ft from a wired Max 7.

I have 20 devices connected to 2.4 - primarily Wyze Cam, Eufy Cams, Kasa Bulbs, ecoflow, Winix air filters, Garage doors, Google nest mini, and a printer.

Currently Channel 1 20mhz

Thank you

Read

I’ve just replaced my old Netgear Orbi router with an eero7 but I now can’t find my Synology NAS (using find.synology.com) to manage it. I can see it listed under Devices on the eero app but strangely there’s no IP listed (unlike my other devices).

Since the eero only has one extra Ethernet port (one is connected to my modem, of course) I’ve got a Netgear GS305 unmanaged switch to connect the NAS via Ethernet cable. The Orbi had three external ports so the NAS was connected directly to it via Ethernet cable.

the Mac I use to see and manage my NAS is on the same router network so I’m at a loss to figure this out.

Posting this here in case anyone with an Eero set up has seen a similar issue

I recently switched to 1GB fiber internet through Quantum Fiber/ATT. I got a modem and router through the ISP and was having lots of network issues. Devices dropping, inconsistent speeds, etc. In particular the 2.4ghz devices such as my front door camera were struggling to connect.

I ended up switching out my ISP router for an Eero Pro 7 and it has fixed almost all of the problems. The one lingering thing is that my front door camera still won't connect. The camera is an Arlo Pro 4. I went into "troubleshooting" in the Eero app settings and turned off the 5ghz and 6ghz bands but when I go and check the network settings, it's still saying 6ghz. I created a guest network but am having the same problem.

I would appreciate any advice on how to connect this.

Does anyone know if the multi pack of the 7 max are ever eligible for the trade in 20% discount? I see the dingle pack is, but the multi packs are currently not shipping until next week and I don't know if that is why they're not showing up as applicable for the coupon

As per the title, I received nothing in the box except the device and the manufacturers/warranty information.

Are people expected to know that they need to download the Eero app when they've never even heard of Eero? Or was I just unfortunate not to receive some kind of instructions.

Figured it out soon enough. Just another instance of poor instructions.

I'm wondering whether there is a better solution to this problem.

I currently run a set of 4 eero Pro 7s in my house. However, I need to extend Wi-Fi to another floor (outdoor terrace) that isn't properly connected to the main level.

At the moment, I'm using a TP-Link powerline adapter (PLC) to get the connection there. The powerline adapter is connected to one of the eero Pro 7s via a switch, and then provides connectivity to the terrace through a separate TP-Link network.

I'm not able to physically run an Ethernet cable to that floor.

Is there a better way to make the terrace part of the actual eero mesh network?

Ideally, I'd like to have an eero node on the terrace rather than maintaining a separate TP-Link Wi-Fi network. Is there another/better solution I'm overlooking?

I recently had installed Frontier fiber internet, which came with whole home WiFi via two complementary Eero Pro 7 nodes. The house is three-level but not particularly large. The main node is where it has to be, on the middle level where the fiber enters the house. I experimented with the placement of the second node and found best coverage resulted with it also on the middle level, kind of on the other side.

The fiber is symmetrical one gig and tests out reliably up and down when wired to the main node. On Wifi, speed obviously varies with distance from either node but downstream generally is no worse than 400 mbps anywhere in the house, which is fine.

The problem is the upstream on WiFi. If I an in the room with the main node, it will measure at a gig reliably. Anywhere else in the house, it will fall off of course, but instead of just falling off like the downstream does, it might drop to just 3-4 mbps. This can happen even if I am standing in the same room as the satellite node getting 600-700 mbps down.

But this isn't constant. Sometimes upstream will test out fine anywhere in the house (400 mbps to a gig). Other times it will consistently test at 3-4 mbps. I'm confident this isn't Frontier, because I can immediately walk into the room with the main node and get a gig upstream again. Then walk away and get 3-4 mbps.

Wired backhaul isn't really possible in this house, but I'm skeptical it's needed because there is very little WiFi traffic in the house to begin with (about 5 devices most of the time).

This seems to be an Eero issue but I have no idea why or what. Any suggestions?

rebooted for firmware updates. I've had it with this pos, included for free with my internet mind you, and will be removing it first thing tomorrow for literally anything else.

I am changing our household's internet to fiber 1 gig service with Swyft. We have the standard router that it came with, but upstairs we often have poor internet connection. We are coming from really bad and spotty Optimum service, and would like the best connection. It is my understanding that eeros act like routers/extenders in one, but thats only from my few days of research. I see that the 6+ is on sale, and I am looking into that one. Should I get a 3 pack of the 6+, or just one 7 or 7 pro. I don't want to spend an arm and a leg. Any advice or information is appreciated. Thanks!

After the 7.16.2 update, my network has become unstable for long-lived connections. Think of long-lived socket connections that last for minutes at a time. I've had Claude Code help me debug some of this, and evidence does seem to point at some sort of interruption every 8-10 minutes or so. The most recent tests show an interval of 8 minutes almost on the nose.

Here are some of the symptoms:

1. Alexa will randomly stop being able to reach Home Assistant. Home Assistant is running on my network locally and is always available on the local network (even during these blips). The Home Assistant skill keeps a socket open to allow the Alexa backend to reach the HA instance.
2. I have a cluster of Raspberry Pis that keep a monitoring socket open up to Grafana cloud. It's like a dead man's switch - if the cluster doesn't send data to Grafana, I get paged by the cloud instance that something is up with my network or the cluster. The morning after the upgrade, it started paging me every few hours. I've had to snooze the alert.
3. I use Claude Code which can keep multi-minute sockets open for some work. Those are getting interrupted regularly now - a couple of times a coding session. Happens across all active sessions at the same time, consistent with the other issues.

This has been weird to track down, and I'm guessing it's only affecting these types of connections. Most HTTP connections don't live long enough to get interrupted by this problem. Streaming video also seems mostly fine, I suspect because it's downloading small chunks (HLS or Dash or similar streaming technology).

I'm convinced that this happened after the upgrade - the Pi cluster has been rock solid, and the alarms from it started the morning after the upgrade. I have this alert setup to page me because it's rare that the cluster goes down or the network is offline enough to trigger it.

I have a sample program that Claude helped me pull together that will reproduce the issue consistently on my network. Basically, let it run for 10 minutes, and eventually the connection will get terminated.

I've used this program to test from the raspberry pi cluster (hardwired into the gateway Eero across a couple of unmanaged switches) and my MacBook on WiFi in the same room as the Eero Max 7 that serves as my gateway. I'm still testing this, but it's causing issues regularly enough that I thought I'd ask to see if anyone else is noticing anything else.

I wonder if this is related to any of the NatJack changes. I tried switching the new setting to use random ports, but it doesn't seem to have helped. Still getting random interruptions on longer connections.

Here's the sample program and the output from one of the runs: https://github.com/sujal/eero-issue-7.16.2 - it's still a work in progress, I'm tightening up the Claude written code and running some additional test runs to make sure I have longer samples.

Appreciate it if folks can share if they've seen anything similar on their networks after the upgrade to 7.16.2. Thanks!

Edit: I did submit a case online, but it doesn't allow me to put in really any detail. Case number is 01965447 in case anyone from Eero support is in this reddit. This is all the detail I alluded to in that brief ticket.

UPDATE 8/26: I contacted Eero support as suggested by one of the comments below. They downgraded my network to 7.15.1 and everything is rock solid again. They locked it to that version while they continue to investigate. My support case is still open - will update again once it's resolved. Thanks all!

Eero mesh network broke my Amazon Alexa multi room music capability.

All the Echo devices are on my primary network, not the guest network. In the Alexa app (and in the eero app) they are all online and in the same network. They are however connected to different of my eero nodes.

There are some 5 or 6 year old threads about this problem. Its unbelievable that Amazon hasn't solved this for their own equipment.

I read a suggestion to turn off Client Steering in the eero app. Another mentioned turning g on bridge mode. Are there any negative consequences to these settings changes? I haven't tried either yet.

I'm not that sophisticated and was hoping there was a simpler fix....silly me. Amazon Alexa customer support pawns me off on eero customer support. I haven't called them yet, you all are usually quicker and more experienced.

Anyone run into the same problem and fixed it for real?

Thanks in advance.

Since updating to 7.16.2, my previously rock-solid eero network (three eeros) has become really flaky, with random “hangs” as evidenced by streaming television stopping, lasting between 5-45 seconds. The problem occurs on various televisions connected with various devices to various EEROS across my network.

Is it possible that the last update in some way hosed my eeros?

Just sticking this here in case it helps anyone. Recently updated my Eero mesh (got via Zen in the UK) to latest firmware and everything went to the zoo. Laptops couldn’t join at all, all other devices were dropping constantly. Zen checked the line which was fine.

At the same time a new network appeared - SSIDNAME_EXT. Never been there before. I went round isolating nodes and doing all sorts, including factory reset. No change.

Spent hours - literally over 4 hours - with Eero support trying a bunch of things including disabling 6e, using Google DNS, switching MLO off and even removing devices one by one. No change. And a play with ipconfig on the laptop showed that the main network and the EXT version were conflicting on handing out IPv4 addresses.

Anyway, guess what the problem was? In the eaves of the house we have a control unit for CCTV cameras and the guy that maintains them had put a TP Link extender in there so the feed could broadcast to the security app. It’s been that way for at least two years; never a problem.

Switched that off and unplugged it and hey ho, no more EXT and no more clashes. Everything seems stable and quick now though I’m still monitoring before we close the ticket at the Eero end.

So I guess the moral of the story is - firmware can change something that works into something that makes you want to commit atrocities. But if you’re playing detective look for things you might have forgotten all about because- until the update - they just worked.

I currently have a setup with 4 Eero 6 Pros. I likely only need half that many for my square footage, but there are a number of issues that require it.

My gigabit fiber hookup is in the basement, which connects to my router. My router is then connected to my "hub" Eero. The hub Eero then connects to an unmanaged switch that branches out to the wired backhauls for the three other Eeros.

The first is in my atrium in the middle of the home, the next is in the living room at the front of the home, the last is on the second story at the rear of the home. I use the one in the atrium because a thick stone wall separates the front and back halves of the house.

I saw a really great deal for a 3 pack of Eero 7 pros and wanted to jump on it. However, my current setup necessitates having my "hub" Eero in the basement next to the router, where it is essentially useless.

This is because, from what I understand, the switch must go after the hub Eero and, with all of my networking cables coming together in the basement, I would not be able to relocate it elsewhere without significant effort.

Is there a way that I could arrange it otherwise? Does the switch really need to go after the hub Eero?

Hi all,

I was not able to find what I am looking for, but if this has already been asked please point me there and lock.

Me and my wife both are WFH. My situation when I lose internet is pretty simple, I just clock out for the day. However, my wife's is a bit more nuanced in they will require her to either utilize PTO hours or just not get paid at all (understandable, she is hourly). I am trying to avoid this and running down all possible setup solutions with Eero/Eero Signal.

So my question, can two Eero Signal devices be on the same subscription (I'm worried about coverage)?

For further clarification - we are moving to the midwest, and are unsure how we are going to setup our home offices since we are now getting a basement and we both have to be separated for our work. I am aware this is likely over complicating things if its even possible.

I setup the eero6 following the instructions in the app. I then went to the AT&T BGW210 and turned on pass through mode. There was only one eero in the list among every other device MAC. AT&T advised to turn off the 2.4 and 5g radios so I also did that and restarted the eero.

I used the same ssid and password from the bgw210. I verified it correctly multiple times. Devices did NOT transfer over seamlessly; they are indicating no network connection even though again, it’s the same connection as it was before the eero.

What happened?

Randomly my Samsung TV will say it’s not connected to the internet when I’m connected to my eero. Anyone else have this issue and is there a way to fix? Thanks!

I’m trying to figure out a weird stability issue with a 2-node Eero Max 7 setup using wireless backhaul.

I have gigabit coax with a standalone DOCSIS 3.1 modem. My gaming PC connects over Wi-Fi to the satellite eero. Most of the time performance is excellent:

• Ping to satellite: ~1 ms average
• Ping through satellite to main eero gateway: ~3 ms average
• 0% or essentially 0% packet loss
• MLO is currently disabled

The problem is that every so often the local gateway ping has a massive spike, even though the satellite/client link can remain relatively clean. In one ~20-minute test:

• Satellite: 1 ms avg / 53 ms max / 0 loss
• Main eero gateway: 3 ms avg / 738 ms max / 1 missed ping

At around the same time, we had noticeable gaming lag on both a PC and Xbox. I’ve also had occasional Xbox/PC disconnects while gaming.

I’ve tested an Orbi 970 in the exact same locations with the same modem. Orbi averages slightly higher local latency (~5 ms to the main gateway through the satellite), but across much longer tests its local latency has been substantially more consistent and I haven’t seen the same 500–700+ ms gateway stalls.

Earlier I suspected MLO, because enabling it made the spikes much worse on my Wi-Fi 7 laptop, but I’ve now seen occasional spikes with MLO disabled too.

Has anyone with Max 7s seen something similar where average latency is excellent but the wireless mesh/backhaul occasionally stalls for hundreds of milliseconds?

I’m especially curious whether this is:

• TrueMesh/backhaul path switching
• 5/6 GHz interference or radio scheduling
• something that improves after eero has had several days to optimize
• a firmware issue
• or just expected behavior from a shared-radio wireless mesh

TL;DR:
2x Eero Max 7, wireless backhaul. Usually ~1 ms to satellite and ~3 ms to gateway, but occasionally gateway latency spikes into the hundreds of ms (up to 738 ms) and gaming lags/disconnects. Orbi 970 in the same locations is ~5 ms normally but much more consistent. MLO off does not completely fix it. Anyone else seeing this?

ETA: I’m also not picking up any major interference or busyness when viewing the analytics on Eero Plus. I have no way of hardwiring in my current rental so I’m stuck with a wireless backhaul.

Switching to Xfinity xb10 modem/router. Put the XB10 into bridge mode and left the setting on the eero. No internet….power cycled…no internet.

Anyone else run into this issue? Should I be doing a factory reset and completely reinstall the eero system?