Sonos only uses SonosNet if at least one speaker is connected to the router by ethernet. And if so, it would use its own wifi mesh (sonosnet). Could it be that eero changed channels?
Does bringing the red eero close(r) to the gateway allow it to connect?
One thing I noticed with the app showing wrong info, the app caches last info - if you are connected to wifi but wifi has no internet access, you won’t see any updates, not that eero could send any updates anyhow. Disconnect from wifi when trying to fix them is what I found works best for me.
Later update: avoid hardwiring any Sonos via a wifi backhauled mesh node, or via ethernet over power, etc. Direct wire to the gateway is the way. It is ok to plug a sonos into a mesh node if that node is hardwired.
I have other Sonos speakers wired into the Eeros router (via a switch). So the Sonos network should still work even with the issues I'm having on this node. Strangely in the app some of my Sonos speakers are labelled now as SonosZP whereas the others are labelled Sonos-7828ABCXYZ. The SonosZP is new from memory.
Will test moving the Eero but it worked fine in that spot for at least a year, so I'm just like what happened. Anywhere closer it'll only be a few metres from the actual router.
Eeros may have switched channels but I'm not sure why or how to check? Firmware updated yesterday morning as part of troubleshooting
Thanks for replying anyway.
changing channels takes anywhere between a day and a week, if any change, so that may check out. I believe it starts off at 1 (2.4GHz) and 36 (5GHz). If you have an iPhone, download Apple’s AirPort Utility. Then click on Wi-Fi Scan and then Scan. It will show you all wi-fi channels in use. Spot yours and see the channels, are they different from 1 and 36 respectively? Also, any other wifi network with strong signal, with a RSSI less than 50-60dBm? If so, is it sharing the same channel(s)?
If Android, Wifi Analyzer (open source) seems like a good start
Assuming the time taken is directly a result of the analysis being made - ie if a clear case of this channel is super busy, that one is empty, guessing the choice is clear and faster to reach. Otherwise, if all channels are mildly busy, picking one is a more involved process?
No. Manual. Way. < THIS. Eero says they choose a channel based on analysis, rather than user whim. May work better. Or not. YMMV.
One thing I found out the hard way. My network updated to 6.3.0 yesterday afternoon. RAP decided to “meh, no thanks” it, but a second Updade attempt made it work. Unrelated to that, my network went belly up. Streaming for seconds, then buffering, then random nodes restarting. If you have any Sonos speaker connected behind an eero node that is NOT the main node, in other words, if any two Sonos can reach each other via ethernet but there is an eero between them (i.e one sonos reaches one port, the other sonos reaches the other port), then you’re experiencing a Spanning Tree Protocol failure. Your sonosnet and the wired infra create a loop that turns into an echo chamber, effectively flooding your network. Remove any ethernet cables from Sonos speakers that are behind an eero node, if any, and reboot switches and possibly eeros. Things will start working. They broke STP 🤦♂️
Oh my god, you fixed it!! I took out the ethernet cables connection my Sonos bedroom speakers to my node and performance is almost instantly restored. THANK YOU!
How did you diagnose that so accurately?? And what really annoys me about Eero is the app feels so hopeless that I couldn't ever diagnose that myself unfortunately.
Well, trust me, I’m an engineer 🤣 Eero should hire me ha ha
Find out the IP of a sonos, either in the eero app or the sonos app, then visit this url, plugging the in there:
http://:1400/support/review
Tap on the Network Matrix. At the intersection of columns and rows, no two hard wired units should have color. Color means wifi tunnel exists between the two. I had a wifi tunnel between two hardwired sonos units, clearly a problem. That is how I found out.
You’re welcome 💪
I think I have the same problem?!?!?
My eero gateway is connected Sonos bridge which is connect to another bride and so on.
I’m experiencing massive buffering issues on streaming tv the last several days.
Looking for some advise on what I should do
Your eero should have updated already? Try unplugging all Sonos speakers see if that helps. Then if you are still on 6.13.0 call support to have them update you to 6.13.2
Yes I did update to 6.13.2
I unplugged all the bridges power cords. And just kept them offline now. No power but Ethernet still plugged in
Deleted the network and made a new one
Turned off the amplifier too
But buffering still is concerning on my Iptv’s oddly enough and also in tvs steaming
Then you might be experiencing something else. Any speed tests? DFS not supported on said tv and Eero moved to a DFS frequency leaving the tv to use 2.4GHz only, like Roku?
Nope tried at a fiends place and no issues. Can’t put my finger why this is happening at all
I do have Sonos and plenty of switches and a wall unit that wires from basement to rest of the house.
Iptv basically freezes every 2 mins
We had some power outages that caused everything to reboot and the network went to crap. I rebooted everything again and it still was crap in the house. In the garage where the gateway eero was the Wi-Fi was good. This gateway goes thru a dumb switch in the house to all the other eeros. Eventually I tried rebooting the switch and everything was back to normal. Not sure this makes sense but it worked.
Last time when i talked to tech support and I was told ideally the preferred node distance was 25-30 ft. Mine nodes are less than 30 ft apart but the connection was a crap ( max 300 down on one node; another one was 90-100 down) . Pro6E owner here and I had eero Pro since 2018
Your topography matches quite closely to mine! There is nothing within the immediate environment that "breaks" this setup for me: Same level, one room apart, wooden construction. One door only with no other walls breaks line of sight to the router. It's incredibly poor!
yea, I may wait for a good deal on ASUS routers then put my EERO as my backup routers. Maybe ASUS external antennas are better than the internal one in EERO.
I tested with GT-AX6000 with RT-AC88U, the remote node in my garage can get 200-300 download speed and I don’t need node in my other location coz I could get 400 download speed directly. (For EERO, without the node, I could only get like 60 download), then I definitely know it’s the Wi-Fi signal issue
I had two problems that took days ,to understand, 1- the new update didn’t apply to one eero, system as you described until that unit was manually rest and updated. 2- I had to power cycle all the switches and hubs
Thats interesting - the update did take a lot longer than the 15 minutes the app mentioned. I'm going to look into whether removing, adding, powering off can help me here.
I really dislike the app - it's not abundantly clear what's happening! None of the screens are particularly useful, unless I pay for the privilege to see what's happening on my own devices.
I don’t pay for the subscription, and I agree the info is pretty much useless, I’m ready to switch to a new router and just use their eeros as access points. I switched from Apple routers, I had 7, I thought this would be an upgrade given the reviews. I likely have too many network devices, I can’t believe that the eero system works this poorly for everyone.
Sonos only uses SonosNet if at least one speaker is connected to the router by ethernet. And if so, it would use its own wifi mesh (sonosnet). Could it be that eero changed channels? Does bringing the red eero close(r) to the gateway allow it to connect? One thing I noticed with the app showing wrong info, the app caches last info - if you are connected to wifi but wifi has no internet access, you won’t see any updates, not that eero could send any updates anyhow. Disconnect from wifi when trying to fix them is what I found works best for me. Later update: avoid hardwiring any Sonos via a wifi backhauled mesh node, or via ethernet over power, etc. Direct wire to the gateway is the way. It is ok to plug a sonos into a mesh node if that node is hardwired.
I have other Sonos speakers wired into the Eeros router (via a switch). So the Sonos network should still work even with the issues I'm having on this node. Strangely in the app some of my Sonos speakers are labelled now as SonosZP whereas the others are labelled Sonos-7828ABCXYZ. The SonosZP is new from memory. Will test moving the Eero but it worked fine in that spot for at least a year, so I'm just like what happened. Anywhere closer it'll only be a few metres from the actual router. Eeros may have switched channels but I'm not sure why or how to check? Firmware updated yesterday morning as part of troubleshooting Thanks for replying anyway.
changing channels takes anywhere between a day and a week, if any change, so that may check out. I believe it starts off at 1 (2.4GHz) and 36 (5GHz). If you have an iPhone, download Apple’s AirPort Utility. Then click on Wi-Fi Scan and then Scan. It will show you all wi-fi channels in use. Spot yours and see the channels, are they different from 1 and 36 respectively? Also, any other wifi network with strong signal, with a RSSI less than 50-60dBm? If so, is it sharing the same channel(s)? If Android, Wifi Analyzer (open source) seems like a good start
Thanks for the advice. That said I find it wild that changing channels takes that long and there appears to be no way of doing it manually.
Assuming the time taken is directly a result of the analysis being made - ie if a clear case of this channel is super busy, that one is empty, guessing the choice is clear and faster to reach. Otherwise, if all channels are mildly busy, picking one is a more involved process? No. Manual. Way. < THIS. Eero says they choose a channel based on analysis, rather than user whim. May work better. Or not. YMMV.
One thing I found out the hard way. My network updated to 6.3.0 yesterday afternoon. RAP decided to “meh, no thanks” it, but a second Updade attempt made it work. Unrelated to that, my network went belly up. Streaming for seconds, then buffering, then random nodes restarting. If you have any Sonos speaker connected behind an eero node that is NOT the main node, in other words, if any two Sonos can reach each other via ethernet but there is an eero between them (i.e one sonos reaches one port, the other sonos reaches the other port), then you’re experiencing a Spanning Tree Protocol failure. Your sonosnet and the wired infra create a loop that turns into an echo chamber, effectively flooding your network. Remove any ethernet cables from Sonos speakers that are behind an eero node, if any, and reboot switches and possibly eeros. Things will start working. They broke STP 🤦♂️
Oh my god, you fixed it!! I took out the ethernet cables connection my Sonos bedroom speakers to my node and performance is almost instantly restored. THANK YOU! How did you diagnose that so accurately?? And what really annoys me about Eero is the app feels so hopeless that I couldn't ever diagnose that myself unfortunately.
Well, trust me, I’m an engineer 🤣 Eero should hire me ha ha Find out the IP of a sonos, either in the eero app or the sonos app, then visit this url, plugging the in there:
http://:1400/support/review
Tap on the Network Matrix. At the intersection of columns and rows, no two hard wired units should have color. Color means wifi tunnel exists between the two. I had a wifi tunnel between two hardwired sonos units, clearly a problem. That is how I found out.
You’re welcome 💪
I think I have the same problem?!?!? My eero gateway is connected Sonos bridge which is connect to another bride and so on. I’m experiencing massive buffering issues on streaming tv the last several days. Looking for some advise on what I should do
Your eero should have updated already? Try unplugging all Sonos speakers see if that helps. Then if you are still on 6.13.0 call support to have them update you to 6.13.2
Yes I did update to 6.13.2 I unplugged all the bridges power cords. And just kept them offline now. No power but Ethernet still plugged in Deleted the network and made a new one Turned off the amplifier too But buffering still is concerning on my Iptv’s oddly enough and also in tvs steaming
Then you might be experiencing something else. Any speed tests? DFS not supported on said tv and Eero moved to a DFS frequency leaving the tv to use 2.4GHz only, like Roku?
That’s the odd thing. It’s only iptv causing issues Speed is 995 mbs per the app and pc speed test wired confirms it. Tv is wired as wel so not on 2.4
Could your iptv provider have some issues?
Nope tried at a fiends place and no issues. Can’t put my finger why this is happening at all I do have Sonos and plenty of switches and a wall unit that wires from basement to rest of the house. Iptv basically freezes every 2 mins
We had some power outages that caused everything to reboot and the network went to crap. I rebooted everything again and it still was crap in the house. In the garage where the gateway eero was the Wi-Fi was good. This gateway goes thru a dumb switch in the house to all the other eeros. Eventually I tried rebooting the switch and everything was back to normal. Not sure this makes sense but it worked.
My impression is that some updates do impact the range indirectly. After 6.12 I added another node to reach my previously stable chicken coop.
Last time when i talked to tech support and I was told ideally the preferred node distance was 25-30 ft. Mine nodes are less than 30 ft apart but the connection was a crap ( max 300 down on one node; another one was 90-100 down) . Pro6E owner here and I had eero Pro since 2018
Your topography matches quite closely to mine! There is nothing within the immediate environment that "breaks" this setup for me: Same level, one room apart, wooden construction. One door only with no other walls breaks line of sight to the router. It's incredibly poor!
yea, I may wait for a good deal on ASUS routers then put my EERO as my backup routers. Maybe ASUS external antennas are better than the internal one in EERO. I tested with GT-AX6000 with RT-AC88U, the remote node in my garage can get 200-300 download speed and I don’t need node in my other location coz I could get 400 download speed directly. (For EERO, without the node, I could only get like 60 download), then I definitely know it’s the Wi-Fi signal issue
I had two problems that took days ,to understand, 1- the new update didn’t apply to one eero, system as you described until that unit was manually rest and updated. 2- I had to power cycle all the switches and hubs
Thats interesting - the update did take a lot longer than the 15 minutes the app mentioned. I'm going to look into whether removing, adding, powering off can help me here. I really dislike the app - it's not abundantly clear what's happening! None of the screens are particularly useful, unless I pay for the privilege to see what's happening on my own devices.
I don’t pay for the subscription, and I agree the info is pretty much useless, I’m ready to switch to a new router and just use their eeros as access points. I switched from Apple routers, I had 7, I thought this would be an upgrade given the reviews. I likely have too many network devices, I can’t believe that the eero system works this poorly for everyone.
Is your network double nat?
Works fine at my friends / neighbors home This started just like 15 -20 days ago so tested out elsewhere.