My Sonos Controllers disagree over how many zones I have

Update: I now see a potential difference - the "Associated ZP", in the "About My Sonos System" diagnostic screen. Each of my controllers lists the IP address of a different Sonos unit as the associated ZP, and different controllers / associated Sonos units are reporting a different network of zones. Doesn't seem to be a way to link a controller to a "preferred" Sonos player, but hopefully another round of re-booting everything will finally fix things.

...and I rebooted. And it might not be the "Associated ZP" setting, as both of my Windows 10 machines link to the same zone player, which then gives each PC a different list of either 3 or 4 zones. Grr...

Hi Alan_6

Looking at your profile you've been around for a while (i.e. this ain't your first rodeo) 🆒. If I were you I 'd move to a Boost setup. JMO :8

Cheers!

If you compare your "About My Sonos" data with your router's DHCP server data are the Sonos and router IP addresses matching?

Do the router logs show the Sonos gear requesting/renewing their IP addresses and being given the assigned ones?

Hi Alan_6

Looking at your profile you've been around for a while (i.e. this ain't your first rodeo) 🆒. If I were you I 'd move to a Boost setup. JMO :8

Cheers!

Thanks, but I'm not sure how a new wireless device will help a PC with a wired connection to an all-wired Sonos network. Unless there is a problem with the kit I have, and I've just been incredibly lucky to have it work flawlessly and survive multiple re-boots for the last few years.

If you compare your "About My Sonos" data with your router's DHCP server data are the Sonos and router IP addresses matching?

Do the router logs show the Sonos gear requesting/renewing their IP addresses and being given the assigned ones?

Yes, the IP addresses match - Sonos controller info and DHCP table agree on the IPs (static IP assignment for all zones). According to the router logs, all the Sonos units got the correct IP assigned, and no other device "stole" the IP of the "missing" (according to one controller app) zone.

The "all wired" is what keeps pointing me back to IP issues. The problem persisting past a reboot of everything is puzzling too, don't think I've seen that in the past.

I'd love to be able to move the Sonos bits and one PC based controller to their own LAN segment (to reduce outside network traffic and events) and bring everything up from a powered-down state, watching just what happens as things wake up. Once up I'd watch the DHCP service (setting a short lifetime would make this faster) and how the Sonos gear is dealing with it.

It is obvious something is going wrong but finding the rat in the wall in situations like this can be less than fun.

From the posts that were made referencing Static IP addresses I made the assumption that you were in Standard Mode (Wi-Fi). I wasn't suggesting investing in a dedicated Boost component but switching to a Boost setup which can be accomplished by wiring one Sonos component via Ethernet to your router. I also missed where you indicated that all your Sonos units are wired :(

As you can see from my signature I have multiple Sonos components using only a single dedicated Boost component. I chose the dedicated boost so not to limit my speaker placement. My router is an Asus AC5300 located on the ground level with one below it and one above it. My coverage IMO (knock on wood) is excellent. My Sonos controllers are on iOS devices (wireless), OSX (wireless) and Windows (wired).

It may be I just have a better location geographically with less interference. Who knows? Obviously, something has changed in your environment and submitting a diagnostic may help. Good Luck to resolve your issues.

Cheers!

Update: I finally solved the issue and got my Sonos network back with a total switch-everything-off-slowly-switch-on re-boot of everything involved in my network - routers, Sonos, PCs, powerline adapters, switches hidden in hard-to-get-to places - everything. I probably missed something important first time.