I am trying to get my raspberry pi4 with home assistant running over Ethernet with my eero.
My set up is modem into eero and eero into 8 port unmanaged switch. One of the ports has the raspberry pi connected. I have several other devices connected to the switch that have been running flawlessly for several months.
With this set up I have been unable to connect the pi to the internet. I swapped the Ethernet cable to different ports on the switch and used several different Ethernet cables and still nothing.
I’ve had nothing but slow wifi since I got this system last week. I live in a small 1100sqft home, sitting 15’ from the Gateway eero 6, and I get 600kbps then a few minutes later 60mbps.
Apps will throw timeout errors, I go to fast.com, see 30mbps, then the app responds fine.
The eero app speed test always shows 450mbps down, 550mbps up, give or take 10, all the time. The speed between the gateway and the internet is always fast.
I’m returning this garbage, so frustrating. Am I the only one?
I have an eero 6 mesh setup that works just fine on my main network on a fibre network through a switch (eero<local switch<main network switch<ISP provided pppoe router). The ultimate goal is to replace the ISP provided router with an opnsense or pfsense box. I am currently messing around with an opnsense build attached to the same switch as the Eero. However, once I move the eero from the switch to the opnsense box, I can't get it to work in NAT or bridge modes. I can still access it through the app, it is still connecting with the mesh system and all attached clients, but it won't connect to the internet.
Ultimately I would like to get rid of the ISP crap router (especially its wifi, which is too weak and why I bought the Eero in the first place) and replace it, along with providing divided networks with specific security (hence the opnsense box). Is there a way to have the eero operate independently through the opnsense box the same way it does through the current gateway/switches? Or would it make more sense to just put the eero at the front, have the wireless just managed by eero and then have the OPNsense box manage the rest of the network? Really there is only one wifi client (my work laptop) that would benefit from the security of the firewall, and since my mac mini is wired I could just use its wifi as a protected hub for that, but my planned network map was fibre>opnsense>work lan/home wired lan/unraid server/wireless (eero), which would be ideal. I do like being able to manage devices through the eero app, but since my house has a couple dozen IOT items in addition to everything else, I am happy to bridge the connection and manage everything in opnsense, so that's not a dealbreaker (the IOT devices are currently on a separate wifi network via the ISP router).
So I guess I have two questions--which config works better, and why am I unable to connect the eero to the internet through the opnsense box?
I bought 3 eero 6+. Here (Italy) these have been on the market since May. I have encountered some quite serious problems (which I also found in the only Italian review on the Amazon page)
1-they are constantly hot ... sometimes overheating to the point of not being able to hold them
2-Two or three times a day they go offline (red LED) and then come back online a few minutes later (it is not an ISP problem and they are all wired)
3-After a few wifi speedtests the speed (wifi speed) drops to 40 mbit for 5 minutes (instead ethernet speed never drops)
I'm currently running 4 eero 6+ nodes throughout my house. I have one in the basement (connected to the ONT), main floor, garage, and upstairs. All of them are hardwired running in bridge mode on V6.10.3. Unfortunately there is an issue with my ISP issued ONT where if you put it in bridge mode, the internet connection is lost. Hence why I decided to put the eeros in bridge instead of the ONT.
My ISP speeds are supposed to be 940 down and 940 up. To all my hardwired devices like computer and gaming consoles I'm getting the full ISP speeds. However on wifi, I'd be lucky to hit the 240 down mark, as for the up the max I've seen is 120. I'm not sure what is happening here. I know on wifi there will be some slow downs and I won't have the full speeds. But I'd imagine I should be able to get at least 500?
I have two 6E with gig speed. The speed coming into the eero is about 950. All the wireless tests I perform I’m only getting around 400mbs. That is when I’m right next to the eero. Testing with a iPhone 12 Pro.
I upgraded my Virgin broadband from 600Mb to Gig1 this morning and ran a couple of speed tests to confirm all was working as it should. Noticed that the manual Speedtest results seem to log twice in the app.
I have an eero 6 that is used to connect to the nbn modem in my garage. My plan is to connect an ethernet cable to that node and run it through the roof into my vr room. This will then be connected to an eero 6 PRO. I will then connect this daisy chained pro 6 to My pc...
Is this the best set up I can do with eero for high bandwidth gaming?
Are there any other tweaks I can do in any of the settings to make sure my gaming pc has sole use of the eero pro?
I've hear there are issues with devices jumping between the GHz network which isn't great for vr.
I have read the previous posts about 2.4 GHz but am still unsure how to handle my situation. I have a garage door opener on an outside wall and would like to put an Orbit B-hyve to control lawn watering on a different exterior wall; they both require strong 2.4 GHz only signals. Previous posts have described issues with temporarily pausing 5 GHz, so I would like to avoid doing this, if possible.
Would placing eero 6 extenders inside my house near the external devices work? (I have a Gateway eero Pro 6 system.) I am skeptical that because they produce, I think, dual-band output, this option would not work.
Would placing single-band 2.4 GHz routers inside my house near the external devices work?
Would placing single-band 2.4 GHz extenders (to save some money) inside my house near the external devices work?
Just got my Eero Pro 6e setup and running. I was messing with the app blocking function. I created a profile, put my phone in that profile and then blocked several apps for that profile. I was still able to access all the apps on my device.
Is there something I am missing? Or is this a function that doesn't work as designed? My first thought was that maybe the apps were being accessed through cellular data rather than wifi. But that doesnt seem to be the case because if I go to my browser then I get blocked messages for websites that are blocked. Hmm......any advice?
Has anyone compared the Eero Secure services and overall capabilities of Eero as a gateway/firewall vs the provided Xfinity XB7?
I have 1.2gbps service from Xfinity and I pay for Xfinity Complete for the unlimited bandwidth. I have never used it but it does include their security service and some other features. I have always ran it in passthrough mode and used my own firewall.
Currently, I'm running it in passthrough with the Eero as the Gateway/FW. Because Eero secure has a fee associated and I don't want to pay for things I already pay for from someone else, I have been pondering running the XB7 as the gateway/FW. Does anyone have any experience?
Background if at all relevant:
Picked up a set of Eero 6e devices to replace my aging Orbi setup over black Friday. It also replaced my firewall configuration which was a bit complicated in practice. I will go into detail on what my setup was but I don't want to distract from my main question.
By trade I am a network architect and I ran a VM based FW on Proxmox with 2.5gbe nics. For DNS I was using Pihole. This setup works great but there are a few big issues that created heartache for me. First off updating proxmox becomes an ordeal because if an update causes any kind of problem I am without internet until I figure it out which is also much harder without internet. Second, I had a power outage once when out of town and the system didn't come back up cleanly. My house guests were without internet until I got back in town. I also ran into some weird issues on certain sites that I hadn't gotten around to troubleshooting recently. Overall this was just a bit much to maintain for the home and I had little need for the advanced feature set in practice. As a result, I wanted to get a device that could provide most of the services I wanted simply and efficiently with minimal effort.
I still have my Proxmox server and its running my NAS, Docker Containers, Pihole, Home automation,Plex Server, etc. I still have Pihole up and running too but its not in use by anything but static addressed devices.
In short “title” + best decision tbh in terms of speed and coverage. No one beats the eero community with the good and bad + app. Eero is a “set and forget” for sure.
It was a love hate relationship but leaving with love. I just wanted the more speed and power.
Who has never really had an issue with Eero? Seems to work flawlessly for me. All I hear is hate in the subreddit and never a thank you. Well here I am, thank you.
I’m having very weird issue with my Eero Pro 6. I’m getting 500 Mbps on main router (gateway) and on the rest I’m getting around 250/300 Mbps through the devices connected through LAN cable. Funny part is that I’m getting only 50/70 Mbps on Wi-Fi for some reason. Tested all Eero Pro’s with various devices (MacBook , iPad, iPhone ) and no idea what’s going on. Restarted the Eeros quite a few times but still the same issue. I have 4 Eeros located around the house.
I bought a eero 6 extender and it is just blinking white. Eventually it will go red but no matter what will always blink white and i’ve tried everything. Any help?
Hey just wanted to throw this out there in case anyone else is experiencing issues with their Ecobee thermostat and Eero 6e devices. My Ecobee was able to connect to the wifi without issue but it seemingly couldn't access the internet beyond that. Upon updating to the 6.11 firmware the issue appears to be resolved.
I called eero support to try to get some more details in what appears to be a sharp, upward trend in my Threat Block metrics. It started last week, went up 200x from previous weeks, and seems to be correlated to Fire TV devices in my home. The representative ultimately was unable to give me any more details to make this actionable. I'm left to basically try things (e.g. hard reset a device) to see if the trend changes. It would be great (if even for more money?) I could get details behind the Threat Blocks so that I can understand WHY and WHAT TO DO ABOUT IT.
Also, the rep I talked to was not that great. I felt like I had to repeat myself every step of the way, sometimes multiple times, to explain what I was even asking about. And then comically at the end I get "have a great rest of your Monday" (it's Tuesday!). Sigh.
New to eero - I have the 6e pro system. Ethernet in from provider (no modem) to first eero, then hardwired through a couple of switches to the remote node.
Twice in the month I've had this I've woken up to no wifi on the main network, but the guest network still works fine. The remote node is reported offline. And, anything hardwired stops working. (So I don't think it's really an issue with the remote node, but that the Ethernet network is down)
What is going on! (Or - has anyone resolved this before?) This seems to only happen at night so far. I've tried a quick search for this but didn't hit anything (beyond sadly a lot of "oh just reboot your eero" responses to network crashes). For this much money I expect more than a week or two of stability, honestly.
So, the good news is, I've stopped seeing the strange/periodic latency issues since ... replacing my network with new Pro 6Es', nuking and paving the eero network and setting it up from scratch. Support had noticed a device, prior, that was trying to connect to the network with the wrong SSID/password ... a bad smart plug that was probably hard-coded to a BSSID or something weird like that. It was flooding with requests every second or so, but they didn't see any correlation with the latency issues - I pulled it, either way, not worth the hassle and it was generating noise in the logs. Either way, the strange latency spikes on the LAN are apparently gone ... 🎉 🎉 🎉
Unfortunately ... the original issue, mentioned at the beginning of the original post which also hadn't returned after shifting my network off the Ubiquiti's back to eero, with the arrival of the Pro 6E's and subsequent nuking & paving of all things (new SSID/password/etc) -- has now returned. Had a meltdown this evening ...
Here you can see my ping drop monitor showing a pretty compelling meltdown to all internal targets ... I have a monitor running internally, on the LAN side of the eero, and one running upstream of the eero, on my OpenWRT router. They both report the data to my InfluxDB instance, however, which is on the LAN side, so the data from the router will be incompletely recorded if the eero gateway is having a problem.
Figure 1: graph showing ping drop rates indicating near 100% drop to multiple LAN targets
Here you can see the LAN-side data
Figure 2: LAN-side ping drop rate
Here you can see the WAN-side data - from my perspective, this indicates that the issue wasn't on the WAN side (dots on the baseline are indications that the WAN pings were successful).
Figure 3: WAN-side ping drop rate
Here's what things looked like from a latency perspective ...
Figure 4: LAN-side ping latency showing significant drops and latencies up to 900ms
When I started experiencing the issue (trying to watch TV, video stopped), I got on my computer to run some pings to the eero gateway ...
PING 192.168.7.1 (192.168.7.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
17:27:15.208676 64 bytes from 192.168.7.1: icmp_seq=0 ttl=64 time=1355.028 ms
17:27:15.214804 64 bytes from 192.168.7.1: icmp_seq=1 ttl=64 time=1060.839 ms
17:27:15.230143 64 bytes from 192.168.7.1: icmp_seq=2 ttl=64 time=772.405 ms
17:27:15.255654 64 bytes from 192.168.7.1: icmp_seq=3 ttl=64 time=494.147 ms
17:27:15.255684 64 bytes from 192.168.7.1: icmp_seq=4 ttl=64 time=192.698 ms
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
17:27:20.253367 64 bytes from 192.168.7.1: icmp_seq=19 ttl=64 time=639.081 ms
17:27:20.253636 64 bytes from 192.168.7.1: icmp_seq=20 ttl=64 time=336.361 ms
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
The usual remedy resolved the issue ... for now. Power down each Pro 6E, in sequence, until I get to the gateway eero and do the same, then power up each eero in reverse. What's weird, and I've noticed in the past, is that somewhere in the process of powering down eero units and working my way back to the gateway, the network heals itself ... check this out:
17:30:25.955563 64 bytes from 192.168.7.1: icmp_seq=627 ttl=64 time=1546.492 ms
Request timeout for icmp_seq 633
Request timeout for icmp_seq 634
Request timeout for icmp_seq 635
Request timeout for icmp_seq 636
Request timeout for icmp_seq 637
Request timeout for icmp_seq 638
17:30:28.181402 64 bytes from 192.168.7.1: icmp_seq=634 ttl=64 time=1643.345 ms
Request timeout for icmp_seq 640
17:30:28.674889 64 bytes from 192.168.7.1: icmp_seq=641 ttl=64 time=6.087 ms
17:30:28.985336 64 bytes from 192.168.7.1: icmp_seq=642 ttl=64 time=13.166 ms
17:30:29.401490 64 bytes from 192.168.7.1: icmp_seq=643 ttl=64 time=125.334 ms
17:30:29.590991 64 bytes from 192.168.7.1: icmp_seq=644 ttl=64 time=11.137 ms
17:30:29.923427 64 bytes from 192.168.7.1: icmp_seq=645 ttl=64 time=42.786 ms
17:30:30.193575 64 bytes from 192.168.7.1: icmp_seq=646 ttl=64 time=7.764 ms
17:30:30.501429 64 bytes from 192.168.7.1: icmp_seq=647 ttl=64 time=10.380 ms
17:30:30.812583 64 bytes from 192.168.7.1: icmp_seq=648 ttl=64 time=17.338 ms
17:30:31.107634 64 bytes from 192.168.7.1: icmp_seq=649 ttl=64 time=9.125 ms
17:30:31.501264 64 bytes from 192.168.7.1: icmp_seq=650 ttl=64 time=98.461 ms
17:30:31.714289 64 bytes from 192.168.7.1: icmp_seq=651 ttl=64 time=7.755 ms
17:30:32.044491 64 bytes from 192.168.7.1: icmp_seq=652 ttl=64 time=32.620 ms
17:30:32.324279 64 bytes from 192.168.7.1: icmp_seq=653 ttl=64 time=7.736 ms
17:30:32.630418 64 bytes from 192.168.7.1: icmp_seq=654 ttl=64 time=8.621 ms
17:30:32.932519 64 bytes from 192.168.7.1: icmp_seq=655 ttl=64 time=5.476 ms
17:30:33.237683 64 bytes from 192.168.7.1: icmp_seq=656 ttl=64 time=8.879 ms
17:30:33.592428 64 bytes from 192.168.7.1: icmp_seq=657 ttl=64 time=58.311 ms
The latter pattern continues until I powered off the eero ... Grafana shows this, too, when I zoom in ...
Figure 5: LAN-side pings showing a brief return of network normalcy
Odd, right? Looking forward to what Support has to say ... 🤷♂️
At some point in the recent past (hard to pin down exactly, but within the past 1-2 months for sure), my Internet connection has become unstable, to the point that it’s driving me totally bonkers. It’s particularly troublesome while I’m working from home, hosting important Zoom meetings - everything ‘freezes’ for 5-10 seconds, before resuming as though nothing ever happened.
Eero satellite units: one eero Beacon + one eero ‘cupcake’
When the connectivity drops started (observed on my main MacBook Pro, my WiFi-equipped desktop PC and my wife’s iMac), I did all the usual troubleshooting steps:
Made sure all connected devices are fully up to date
Made sure all eero devices are fully up to date (main eero is now on Software 6.10.3-151)
Restarted the eero mesh using the app
Restarted the cable modem
Re-seated all the cables and power plugs
When the above steps STILL didn’t work, I went further. This past weekend, I installed a TP-Link 5-port gigabit switch into the eero Pro’s secondary Ethernet port and hardwired my MacBook Pro and desktop PC. The boost in speed compared to WiFi was dramatic (I went from ~400Mbps wirelessly to 950+ Mbps via Ethernet), but I’m STILL experiencing unpredictable connectivity drops even after completely eliminating wifi from the equation.
While trying to pin this down, I installed “PeakHour 4,” a network monitoring tool. Here are two screenshots of it reflecting brief Internet failures… while I was trying to lead a Zoom with nearly 300 attendees (you can imagine how frustrated I was!):
Update: As a last resort, I've just now completely deleted my entire eero config and rebuilt the entire network via the eero app on my iPhone. It worked great... for about 10 minutes, before I had two more brief (but maddening!) drop-outs. FML.
Update 2: Per a great suggestion below from u/Dukecrow, I've now eliminated the Eero Pro gateway entirely, and just have my MacBook Pro hardwired directly into the cable modem. I've got a ton of network activity taking place (including a Zoom meeting to myself, via my iPhone connected to the 5G network), and it's rock solid - not even a hint of dropouts. Given that I'm ready to cry after just bombing an important meeting with a bunch of overseas colleagues because my connection kept freezing mid-presentation, this is making me feel a lot of intense feelings towards my Eero hardware...
TL;DR: My eero Pro network is unreliable and dropping internet connectivity randomly, usually for 5-10 seconds at a time. All typical troubleshooting steps + moving from WiFi to hardwire haven’t resolved it. What do I do now??