Hi everyone,!--tgqphd|[]-->
I am stuck trying to reconnect my smart home system after having it packed away for a year. I am in the exact same house, but the only variable that has changed is that my ISP (BT) supplied me with a brand-new BT Smart Hub to replace our old one. All my other non-Sonos wireless smart home devices work completely fine.!--tgqphd|[]-->
Hardware:!--tgqphd|[]-->!--tgqphd|[]-->
- 2 x Sonos One!--tgqphd|[]-->!--tgqphd|[]-->
- 1 x Sonos Era 300!--tgqphd|[]-->!--tgqphd|[]-->
- Eero 6+ Mesh System (2 nodes)!--tgqphd|[]-->!--tgqphd|[]-->
- New BT Smart Hub (supplied by ISP, acting as the modem)!--tgqphd|[]-->!--tgqphd|[]-->!--tgqphd|[]-->
Every time I add my Sonos speakers to my system, they display a broken local discovery/status bug. The "Alexa Voice" component works fine on the Sonos speakers—I can talk to them, and they respond. However, the "Speaker" component (the smart home hardware profile for volume sliders/grouping) constantly shows as "Offline" inside the Alexa app, divorcing the microphone profile from the speaker hardware.!--tgqphd|[]-->
Additionally, because we swapped the room names of the Sonos Ones during setup (between a Den and a Bedroom), Alexa seems to have cached the old profile names. Trying to correct the names in Alexa throws a "device already has this name" error, even though it doesn't. When the speakers fall offline, Alexa pulls duplicate "ghost" microphone entries out of its memory and displays them as active options in my Smart Home Groups.!--tgqphd|[]-->
Tried so far:!--tgqphd|[]-->!--tgqphd|[]-->
- Full Cloud Reset:!--tgqphd|[]--> Wiped devices, disabled the Sonos skill, logged out of all Amazon apps, and rebuilt the voice links from a clean slate.!--tgqphd|[]-->!--tgqphd|[]-->
- Sonos Factory Reset:!--tgqphd|[]--> Performed a complete hardware factory reset on all three speakers until they flashed green and added them as brand-new devices.!--tgqphd|[]-->!--tgqphd|[]-->
- BT Hub Wi-Fi:!--tgqphd|[]--> Turned off the Wi-Fi broadcasting frequencies entirely on the BT Hub so it does not compete with the mesh.!--tgqphd|[]-->!--tgqphd|[]-->
- UPnP Firewall:!--tgqphd|[]--> Inside the BT Hub settings, I disabled "Extended UPnP Security" while keeping standard UPnP active. This briefly brought the Era 300 completely online with its Alexa components linked, suggesting that the BT Hub's default security rules are censoring smart home status packets. However, the speakers eventually slipped back to offline.!--tgqphd|[]-->!--tgqphd|[]-->
- IP Reservation:!--tgqphd|[]--> Locked all three Sonos speakers to "Always use this IP address" inside the BT Hub.!--tgqphd|[]-->!--tgqphd|[]-->
- Bridge Mode vs. Automatic Mode:!--tgqphd|[]--> We tested the Eero 6+ system in Bridge Mode (leaving DHCP to the BT Hub) and reverted it back to standard Automatic Mode. Neither configuration has kept the speakers online.!--tgqphd|[]-->!--tgqphd|[]-->
- The SonosNet Cable Test:!--tgqphd|[]--> I temporarily plugged one Sonos One via Ethernet into the Eero node. While it switched over, keeping a speaker permanently hardwired/tethered to the router is not a viable layout solution for our home, so I need a 100% wireless fix.!--tgqphd|[]-->!--tgqphd|[]-->!--tgqphd|[]-->
The issue seems uniquely isolated to how the new BT Hub router firmware maps multicast/mDNS background packets across the Eero mesh network nodes, causing Alexa to lose the persistent "heartbeat" connection.!--tgqphd|[]-->
Has anyone running an Eero mesh on a newer BT Hub encountered this specific Sonos offline bug? Are there hidden multicast, IGMP snooping, or firewall settings in the new BT Hub firmware that need to be adjusted to stabilise Sonos wirelessly?!--tgqphd|[]-->
Thanks in advance,
Tim
