📲 New Sonos App & Player updates for early-March are now available! 🔊

Stuck in this loop every three seconds.

That is odd, unless your firewall is blocking something DHCP, but that seems unlikely.

As none of your other devices seem troubled I’d not put lease time high on my suspect list but it is worth checking. Both the Default Lease Time of 7200 seconds and the Maximum Lease Time of 86400 seconds.

Might be worth trying one more network refresh where you power down all Sonos, reboot the router and once it is up and stable power up the Sonos. Start with the problem one to make log-reading easier.

 Does the Play 1 show it is connected to the network?

No, the LED flashes white. The DHCP server does not show it connected.

Flashing white is stuck in booting phase.

Either something is very odd with your setup or the speaker is having issues. Maybe borrow a friend’s network and see if it works there before calling into support?

 Does it connect wirelessly?

Yes, wireless is no issue. Same DHCP server assigning addresses connects without issue on wifi.

Two speakers with Ethernet both exhibiting this problem only after March software updates.

​@Jerry A, There’s a patch for this issue. You’ll need to update your units once more.

Update your Sonos speakers | Sonos

I did apply both March patches and it did not fix my issue.

 Is the IP Address for the Play 1 reserved?  If it is maybe change it to an IP Address outside the DHCP range.  My XFinity gateway does not allow this, but some routers do.

 Did you first try a different Ethernet cable?

I also am using an Xfinity router and have tried that as well. No change. Reserved Static IP outside the DHCP range.

SONOS “reserved” addresses must be inside the DHCP range.

Ougside the DHCP window, is that a requirement for that router?

My (different router) won't reserve addresses within the range allocated to dynamic assignments.

No not a requirement, but I was trying to isolate the dynamic versus static IP assignment based on community posts I’ve read.

Dynamic IP doesn’t work on Ethernet but works on wifi

static IP inside reserved range doesn’t work on Ethernet but works on wifi 

static IP outside of reserved range doesn’t work on Ethernet, but works on Wifi

tried different cables

tried directly to router

tried via unmanaged switch to router

tried via another unmanaged switch to router

Ethernet fails in all scenarios 

call has been escalated to L3 🫤

Tried both static IPs inside and outside of range. Neither works with Ethernet, both work immediately with wifi

 Which Xfinity Gateway do you have?  Mine is the Technicolor XB8.  I do have a Port that is Ethernet connected, but it is connected to a Xfinity Pod.  Works OK.

 Did read something about Ethernet issues after the 1st March update.  Don’t recall the OP who created that topic.

Is your router on this list?

https://support.sonos.com/en-us/article/incompatible-network-hardware

I have the XB7.

second update supposedly fixed upnp issues but I tried both upnp on and off without helping the issue 

No, my router is not on that list

Appears to be an issue with 18.2 (build 94.1-75110) on Sonos Roam v1 where it won’t connect to WiFi networks with certain special characters in the password : https://www.reddit.com/r/sonos/s/CDzjG4U2aQ

This can cause Sonos Roam to no longer connect as soon as it has updated.

 I think the UPnP setting in the Sonos app is only used to enable Sonos device discovery using other UPnP/DLNA control point apps.

L3 is claiming Pihole DHCP is not supported by Sonos.

I had to assign static IP in the router, instead of the Pihole DHCP server to get the speakers to work via Ethernet cable.

For several years before the March update, pihole DHCP was working 100% with my speakers. They fail to admit the March update has broken something.

Jerry, you may be seeing a conflict between the two DHCP servers. Dual or redundant DHCP servers are possible but that is a complexity I have avoided here.

The update may have altered the Sonos DHCP checking process and exposed an issue that wasn't one with the previous firmware. Sonos doesn't discuss changes made to the open-source code used by the system, just lumps them under fixes and updates.

I don't use the Pi-Hole DHCP here so I can't check the compatibility.

Disable one or the other DHCP server and see if things work better.

Sonos Support were able to reproduce and the engineers are looking into it.

I've fiddled some more and it appears on recent firmware you cannot have a WiFi password start or end with a double quote ( " ) on Sonos Roam and potentially some other speakers (Arc maybe?).

One (Hardware 1.26.1.7-2.1 = Gen2), Beam (Hardware 1.35.1.6-2.2 = Gen2) and Sub (Hardware 1.32.1.5-2.2 = Gen 3) are fine with quotes anywhere in the passwords.

That’s absolutely fascinating. Thanks for providing data to Sonos to look at.

Not that I’m a coder, but how does that happen as a bug? ;)