r/amazoneero

Bit of a weird one and I’m wondering if anyone else has come across this.

I have a 1 Gbps ISP connection. My old ISP-supplied router was only dual-band, 2.4 and 5 GHz, and I never had this issue with it.

I then moved to an eero Pro 7 and started getting a really strange problem with devices using 6 GHz (e.g. my iPhone, laptop etc.)

The device will stay connected to Wi-Fi and everything looks completely normal, but the actual internet connection will suddenly stop working. It can sometimes recover after a minute or two, sometimes toggling Wi-Fi off and back on fixes it, and sometimes it hangs around for longer.

At first I assumed the eero itself was faulty, so my first Pro 7 was replaced by customer support. But the replacement Pro 7 does exactly the same thing.

The clearest example is my iPhone 17 Pro Max. It can be connected to the eero on 6 GHz / WPA3 and the eero app still shows the network as healthy, but the phone suddenly stops loading anything. It normally completely stops working until I disabled Wi-Fi 6e in the settings on my phone.

I’ve also noticed it can sometimes be triggered when another device starts doing something bandwidth-heavy. For example, starting a 4K Netflix stream on my TV can make the iPhone lose internet, even though the TV is only using around 30 Mbps and my broadband is 1 Gbps. My TV is Wi-Fi 5, so can’t use 6Ghz.

I originally thought MLO might be the issue, so I disabled MLO. Weirdly, that actually made things worse. The dropouts became more frequent and sometimes reconnecting to Wi-Fi didn’t even fix it.

When the iPhone is stuck connected to Wi-Fi with no internet, I can go into the Wi-Fi settings, disable Wi-Fi 6E for that network, and the internet starts working again immediately. No router restart, no waiting around, it just works right away.

The eero+ radio analytics also show 6 GHz behaving quite differently from 5 GHz. At one point I was seeing roughly:
- 5 GHz: 7% total busyness, 2% other-device interference
- 6 GHz: 23% total busyness, 22% other-device interference
- 6 GHz noise floor around -95 dBm
5 GHz seems completely stable.
So the pattern I have now is:
- 5 GHz: stable
- 6 GHz: connected but internet randomly dies
- Disable Wi-Fi 6E on the iPhone (or any other 6Ghz device): internet comes back immediately

At this point I’m wondering whether this is an eero Pro 7 6 GHz firmware/interoperability issue, or something about the local 6 GHz RF environment.

Has anyone else experienced anything similar, especially with an eero Pro 7, iPhones or other Wi-Fi 6E/7 devices where 6 GHz is showing as connected but has no usable internet, and then disabling Wi-Fi 6E immediately fixes it. Or potentially experiencing high “other device interference” on 6 GHz.

For now I’ve left Wi-Fi 6E disabled on the iPhone because 5 GHz is rock solid, but I’d really like to understand what is actually causing it rather than just avoiding 6 GHz completely, as that was the key buying point for the Pro 7.

I currently own the eero pro 6e. I just recently purchased a pc that I’d like to plug in via Ethernet cable. The problem is my pc is no where near the router so I recently looked into buying the eero 7 to replace the 6e.

I would use then use the 6e to act as an extension so I can hook up my pc directly to it with an Ethernet. So my question is would this actually help my WiFi speed on pc or would that be a waste of money?

I've been running with a Eero Pro 7 for a couple months now, and ever since changing, I've been experiencing drops (especially during MS Teams calls), and high ping spikes. Any advice to help this situation would be massively appreciated.

• I've tried turning off IPv6, didn't solve.
• DHCP & NAT is automatic
• Local DNS caching is on
• UPnP is on
• SQM is off
• MLO is off
• Client steering is on
• thread is off
• eeroOS 7.16.2

Ping results:

13:03:45 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:46 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:47 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:48 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:49 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:50 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:51 - Reply from 192.168.4.1: bytes=32 time=3ms TTL=64

13:03:52 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:53 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:54 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:03:55 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:04:00 - Request timed out.

13:04:01 - Reply from 192.168.4.1: bytes=32 time=7ms TTL=64

13:04:02 - Reply from 192.168.4.1: bytes=32 time=3ms TTL=64

13:04:03 - Reply from 192.168.4.1: bytes=32 time=70ms TTL=64

13:04:04 - Reply from 192.168.4.1: bytes=32 time=87ms TTL=64

13:04:05 - Reply from 192.168.4.1: bytes=32 time=91ms TTL=64

13:04:06 - Reply from 192.168.4.1: bytes=32 time=58ms TTL=64

13:04:07 - Reply from 192.168.4.1: bytes=32 time=70ms TTL=64

13:04:08 - Reply from 192.168.4.1: bytes=32 time=23ms TTL=64

13:04:09 - Reply from 192.168.4.1: bytes=32 time=74ms TTL=64

13:04:10 - Reply from 192.168.4.1: bytes=32 time=52ms TTL=64

13:04:11 - Reply from 192.168.4.1: bytes=32 time=33ms TTL=64

13:04:12 - Reply from 192.168.4.1: bytes=32 time=60ms TTL=64

13:04:13 - Reply from 192.168.4.1: bytes=32 time=77ms TTL=64

13:04:14 - Reply from 192.168.4.1: bytes=32 time=46ms TTL=64

13:04:15 - Reply from 192.168.4.1: bytes=32 time=56ms TTL=64

13:04:16 - Reply from 192.168.4.1: bytes=32 time=17ms TTL=64

13:04:17 - Reply from 192.168.4.1: bytes=32 time=24ms TTL=64

13:04:18 - Reply from 192.168.4.1: bytes=32 time=31ms TTL=64

13:04:19 - Reply from 192.168.4.1: bytes=32 time=11ms TTL=64

13:04:20 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:04:21 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:04:22 - Reply from 192.168.4.1: bytes=32 time=3ms TTL=64

13:04:23 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

13:04:24 - Reply from 192.168.4.1: bytes=32 time=2ms TTL=64

According to Claude this is too expensive and since I use iPhone and Apple TV it’s not necessary. We do have a very old PC so what protection should I buy. I mean the Airport is so old I have probably lost all my data to hackers 🤷‍♂️

I currently have 2 Pro 6E units and have purchased a 7 Pro, with the goal of getting an additional 7 Pro in the near future. Currently where my ISP(1Gb) comes into my house, there are not many WiFi clients, so around 70% of the devices end up connecting to the second gateway(wired backhaul 2.5Gb).

Until I purchase my other 7 Pro, would there be any disadvantages of using the 7 Pro as my secondary node and keeping my 6E as the gateway? I currently run the ISP into the 1Gb port on the 6E as that’s what package I’m limited to anyway, and then utilize the 2.5 port to 2.5 switches for local traffic due to local steam transfers/NAS traffic.

I very recently switched from Google mesh equipment to eero. I'm very pleased I did it and got much wider and stronger coverage with eero.

But under the Google system, you would get a text notification if one of the mesh network modems went offline for a certain period of time.

I had an eero modem go offline and did not receive any notifications. Is that not part of the system? Or do I not have a setting turned on? I don't see any reference to that capability.

The offline incident was a bad power outlet limited to that particular modem was plugged in.

Thanks in advance.

I have eero 6+ and eero app version 26.9.1. Each device shows 0% data usage. Is this a subscription-based? Thank you

I just noticed a recent change to the app removed the entry under a device that showed the last time it was online. If a device turned off or lost connection, you could click on the specific device and it would show the exact time when it was turned off or went offline. (ANDROID). UPDATE - GOOGLE PLAY STORE NOW HAS MULTIPLE COMPLAINTS ABOUT THIS VERY ISSUE SINCE LATEST UPDATE

I’m astonished that I am seeing 200-213 MB/sec (yes Megabytes - I have 2.5gbit connection) to a laptop connected to my second Pro 7 node via Ethernet while connected to a work server downloading 100gb of files this morning for my workday.

The eero nodes are not connected via Ethernet.

I’ve had the pro 7s for about 6 months and while I’ve had great speeds, typically 120-180 MB/sec) this is easily the fastest I’ve seen sustained to this machine.

Now if only there was a way to not have them update so it would always work this well…

There are two people that live in my house, both of us have IPhones. I had an android device connect to my eero device and stayed connected for 15 days. I asked my now ex partner if he knew anything about it and I’m being told that I’m crazy for accusing him of things he’d never do. Anyone know of how an unknown Android device could connect to my eero without me giving my password out and stay connected for fifteen days when there were only two people here?

Edit to add that I’m rural and there’s no houses within range of my device.

I have 3 eero 7 Max units in a 2 story home all hardwired to each other. I needed some advice on what options I have. Essentially it seems like the 3 eero 7 max units are a slight overkill in my setup and causes frequent disconnections and reconnecting with many devices. The problem is my gateway unit. It is located centrally in the home (has to be because that is where all other ethernet connections and primary internet run goes to). I've already tried moving the satellite units or even unplugging one of them to see how the network responds. The best solution is when the gateway unit is essentially "removed" from the wifi access points equation, then signal to all devices is good to great and no more disconnecting/reconnecting problems. However, eero doesn't have an easy way to simply "turn off" wifi offering on the gateway at least that I know of (unless it's in the plus subscription since I don't have that).

Any thoughts or advice? Should I come up with some sort of Faraday cage, lol to put around my gateway unit!?! Hopefully there is a simpler suggestion or solution. Thanks in advance for your replies!

I have a system with three eero Pros plus one eero Beacon. Has been very stable for years.

This morning two things happened: I updated all units to 7.16.2, and Xfinity turned my service off (there was about an hour between events). My internet service is back on, and a gateway (for a weather station) that is plugged into the second port of the eero gateway is happily uploading data. All of the other eeros are reporting connected. If I run a connectivity test from WiFi, it fails to connect to internet. If I run the connectivity test from cellular, it passes. None of the devices on the WiFi network have internet access.

I’ve tried unplugging the modem for five minutes, and I’m convinced the internet service is working. I’ve power cycled the eero gateway, but haven’t left it unplugged for very long. I did see a couple of periods where all of the eeros were showing down in the app, though they are currently all showing online. It’s curious that an Ethernet connected device on the eero gateway has internet access, but the WiFi devices don’t.

I’m pretty stressed on this, also have run out of ideas. I suppose I could leave the eero gateway power off for 5, 10, however many minutes. Or swap another eero into the gateway position.

Any ideas?

UPDATE: Thanks to everyone for the suggestions. Doing the soft reset on the gateway revealed a flashing blue light, meaning no upstream internet. I went through several rounds with Xfinity trying to onboard my modem without success, so I pulled out my backup modem and got that provisioned. It took a while for the mesh to sort itself out, but it’s ok now, and I’ll modem shop tomorrow.

Very time consuming and stressful, but eliminating the eero system as a problem made it much easier to troubleshoot.

So I had a setup with my ISP of 1 gig internet in 2022. They provided two eero pro 6s. I ended up adding an eero 6 extender on my own since it was cheap on prime day so I can get decent speeds in my living room. I upgraded to a 2 gig speed plan because it was cheaper than the 1 gig plan when I looked yesterday so they came out today and swapped my eero pro 6s for eero pro 7s which is great. However, I read that if I reconnect my eero 6 extender it will nuke the performance of my eero pro 7s. Is this true? Do I really need to get an eero 7 to use as an extender?

For reference, with the two eero pro 7s without the extender added, I get 1.5G down near the modem (second floor). 260 or so in the basement with the second eero pro 7. But without an extender, I’m only getting 145 down on the living room. With the eero 6 extender on my old setup I was getting 350 down in the living room which still isn’t great but it was tolerable.

I had a setup that worked well for a long time. One eero Max 7 was connected by ethernet to a Google Fiber Fiber Jack and a 5 Gig plan, and two more eero Max 7 units in other rooms formed the mesh:

Google Fiber Jack → ethernet → eero Max 7 ("Hallway") → wifi → eero Max 7 ("Bedroom") and eero Max 7 ("Media Room")

In my pursuit of even better performance, I recently added a UniFi Dream Machine Pro between the Fiber Jack and the eeros, with a direct wired ethernet run to the Hallway unit. Everything broke immediately. After a week of debugging, I put the eeros in bridge mode, which restored the Hallway unit completely. The other two units now work for roughly 30 seconds, stop, then come back for another 30 seconds, apparently at random.

The failure pattern is drop-and-recover. Devices behind the two satellites fail on wifi and on ethernet

What I believe testing established:

• The internet connection is healthy. A laptop wired to the UDM Pro gets 914 down, 936 up, 2 ms idle latency rising only to 15 ms under load.
• The Hallway eero is healthy. A laptop wired to that unit gets 934 down, 933 up. Its ethernet, bridging, and upstream path are all fine.
• The fault is localized to the link between the satellites and the rest of the network. Simultaneous continuous pings from a wired desktop in the Media Room showed local and internet targets failing and recovering together. When packets do get through they are perfect: 1 ms to the UDM Pro, 9 to 11 ms to Google. Recovery packets arrived at 786, 2452, 2705, 2878, and 3268 ms, which I think is queued traffic flushing when a link comes back (?)
• I removed, factory reset, and re-added the Media Room unit. It worked perfectly for about two minutes, then failed and stayed offline for a long time again before coming back for 5-60 seconds at up to 300 Mbps or so and failing again for minutes, repeatedly. It's basically unusable because it keeps disconnecting so often and for so long.

What I believe I have already ruled out:

• Eero Bridge mode not applied (confirmed applied)
• Distance, building materials, and band steering (it fails on ethernet too, and nothing was moved and this Eero mesh system setup worked before)
• A mesh loop from three units (I unplugged the Bedroom unit with no change)
• IGMP Snooping (already off), Spanning Tree Protocol (set to disabled, no change), security posture (already Allow All)

My question for this sub: has anyone run 3+ eero Max 7 units in bridge mode behind a UDM Pro and seen wireless satellites drop on an interval like this? If so, was the fix on the UniFi side? Pretty much out of ideas

The tech tinkerer/software developer guy/wannabe network guy WANTS Unifi gear. I cannot allow myself to do that.

I’ve had an eero 6E from about when it was just released. This is the first wifi I forget exists. I don’t even have to update when vulnerabilities come out.

I’ve installed Eero gear for my whole extended family and have yet to have ANY tech support calls apart from helping someone type in a password for a new device. It’s been about 4 years now since the last call.

I have never owned Unifi gear but it honestly cannot get simpler and better than eero. I work from home and it’s nice legitimately forgetting WiFi issues exist for people. It’s nice not having to go to friends and families homes to diagnose issues with WiFi at 11pm on a work night.

Everyone leaving Eero, a good portion of you will miss it. Home WiFi should just work especially those of us dealing with networking at work.

As long as it remains set it and forget it - I’ll keep using it.

Like the title says I’m pretty sure my Xbox series x or iPad is knocking my router offline. Whenever I use these devices for the first time in a day my router goes red and I have to unplug it. Then things work fine until the next day when the same thing happens again. Anybody know how to fix this issue?

I have a 3-node eero Max 7 mesh using wireless backhaul, running in bridge mode. The main node in Living room is wired to my ISP router, while the other 2 nodes use wireless backhaul. My devices are all Apple decides, M3 MacBook Pro and iPhone 17 Pro etc.

For quite a while I noticed somewhat strange band-selection behavior: when my MacBook was close to the main eero, it would initially connect to 6 GHz, but shortly afterwards switch to 5 GHz.

At first this looked wrong, since the 6 GHz signal was as strong as or stronger than 5 GHz. However, after macOS added support for 160 MHz channel width on 5 GHz, the result was actually pretty good. The Mac would connect to 5 GHz @ 160 MHz and throughput (14xx Mbps) was as good as, and sometimes better than, 6 GHz @ 160 MHz (13xx Mbps).

In hindsight, this actually made some sense in my setup.

Because the 2 leaf eeros use wireless backhaul, the main node is the aggregation point for that traffic. Its 6 GHz radio naturally tends to show higher utilization than the leaf nodes. So even though the Mac had an excellent 6 GHz signal near the main node, 5 GHz @ 160 MHz could sometimes provide better real-world throughput simply because that band had more available airtime.

With eeroOS 7.15.1, this was basically the behavior I was seeing. The band selection looked a little strange, but performance was excellent, so I didn't really consider it a problem.

After the next 2 eero firmware upgrades, however, the behavior completely changed.

The Mac no longer switches to 5 GHz. It now stays on 6 GHz, but has developed a very strong preference for one particular leaf node, regardless of where the Mac physically is.

For example, when the MacBook is literally right in front of the main eero, Wi-Fi Explorer shows roughly:

• main 6 GHz: 95% signal, 60 dB SNR, ~32% channel utilization
• leaf 6 GHz: 67% signal, 33 dB SNR, ~9% channel utilization

Yet the Mac associates with the leaf node.

If I force it back onto the main node by toggling Wi-Fi/reconnecting, it may initially connect to it, but within mins it moves back to leaf node again.

If I physically take the MacBook next to the leaf eero node, it stays on leaf node, which obviously makes sense there. The strange part is that when I move back next to main node, it continues preferring leaf node even though main node has a dramatically stronger signal.

The utilization difference itself isn't surprising to me. I expect the main node to have higher 6 GHz utilization because it has to handle the wireless mesh/backhaul traffic from the leaf nodes. That's normal for this topology.

What doesn't make sense is if AP selection is now heavily influenced by that utilization number.

A leaf node having only 9% utilization doesn't necessarily make it a better connection for a client sitting right beside the main node. In my example, macOS is apparently willing to give up a 60 dB SNR connection for a 33 dB SNR connection. Whatever airtime advantage the leaf has, that seems like a very strange tradeoff.

In other words, using channel utilization to help choose between 5 GHz and 6 GHz on the same nearby node can make sense — and that's arguably why the old 5 GHz @ 160 MHz behavior worked so well.

But using the lower utilization of a physically distant mesh node to outweigh a vastly better RF connection to the nearby node does not seem sensible.

I have already tried:

• Restarting/power-cycling the entire eero network
• Powering nodes off and bringing them back one at a time
• Forgetting and rejoining the Wi-Fi network on both Mac and iPhone
• Enabling and disabling Client Steering

None of these made any difference.

What's particularly interesting is that this changed after the recent eeroOS updates. The Mac, macOS version, physical eero topology and node locations haven't changed.

So the behavior has basically gone from:

7.15.1:

Main 6 GHz → Main 5 GHz @ 160 MHz

(strange-looking choice, but excellent performance and arguably rational because 5 GHz was less busy)

to:

Current firmware:

Main 6 GHz → distant Leaf 6 GHz

(ignores a much stronger nearby main node and becomes extremely sticky to one particular node)

I'm wondering whether something changed in eero's roaming/BSS-load/steering behavior and Apple devices are now giving the reported AP/channel utilization too much weight when selecting a BSSID.

Has anyone else noticed much stickier or irrational node selection after the recent eeroOS updates, particularly with Apple devices?

I'm especially interested if anyone has been able to confirm this by having eero Support temporarily roll the network back to 7.15.1 or another older firmware.

Bought a 3 pack eero Pro 6E as I need to replace my old TP-Link AC1750 with something a bit better since my ISP has bumped us up to 1gb service.

Planned layout is follows:

Main House: modem---->eero Pro6 E (router)---->switch

At the Main House switch is a CAT6 cable that goes to a casita location, and here's my Q

Casita: incoming CAT6 cable from Main House---->eero Pro 6E---->switch OR incoming CAT6 cable from Main House---->switch---->eero Pro 6E

I'm think the 1st config is the one I should do but need to be certain and that's why I'm posting

Thanks all

I've had the above model since November 2020 and it's always worked perfectly, great coverage, reliable, all the good stuff.

I have my main network setup along with a guest one which has the same name but with Guest added to the end of it.

In the past 6 months or so, I've noticed that a lot of devices have started having trouble connecting to the main network or staying connected to it, but don't have problems with the guest network at all. Devices particularly include Apple devices but also other manufacturers too, like TCL for my television or Denon for my AV receiver.

My iPhone and MacBook give the error of 'weak security' most of the time when I try to connect to the main network, but sometimes they'll connect without issue and stay connected for a period of time, but then drop the connection for no apparent reason.

I update the Eero software with each new release so I'm totally up to date on that side of things.

The security settings are currently set to 2.4ghz using Standard (WPA2) and the 5ghz using Hybrid (WPA2+WPA3) but I've played around with changing these to no avail.

I've done a soft reset on the device but haven't done a full reset as yet to see if that would clear down anything software related that could be going on.

Nothing has changed internally on the network. Still using my ISP's router in modem only mode connected into the Eero.

One thing I have noticed is that I have a second model working as an extender in another room, and if I filter on the app, the bulk of my devices are connecting to that one on the main network with apparently no issue.

Would it be worthwhile to delete the network and do a full reset to try and clear whatever issue could be occurring? I presume if I recreate the networks with the same names and passwords, my devices should just re-connect automatically?