Try rebooting the router and phone.

Sonos does not use static IPs, as this is set on the client side and there is no such facility to do this, you have to use DHCP but you can of course reserve IPs (bound to the MAC address) in the DHCP server for your Sonos hardware.

If you have used static IPs on other equipment which allows you to enter the details (on the client side) then do double check that any you have issued are not in the DHCP scope.

The IP’s are set in the router using the MAC address of each device. No device uses a static IP, IP addresses are assigned by DHCP. There is no duplication, so it’s not that.

Done. It’s connected as stated, it’s producing sound from the system, just shows as disconnected in the app?

In your OP you stated you are using static IPs!

Refrain from Factory Reset without further consult.

Likely there is a latency on your network, discovery of the players is too slow, and the controller times out. There are other possibilities.

Give us more detail about your SONOS system, and the network. Model numbers? Network switches? Wireless mesh points? What is wired? Wireless?

I am using static IPs. You said Sonos doesn’t use static IPs. Any device can use a static IP

Any device could use a static IP but only if the manufacturer builds in that capability, Sonos did not. There is nowhere in the Sonos setup where you can assign a device an IP address.

You must use a DHCP assigned IP address for your Sonos. DHCP offers either randomly assigned IP addresses or for specific MAC addresses to always be given the same IP. Call it reserved, and not static.

This is new to us. In the SONOS controller, where have you defined the player’s static IP addresses?

Likely we are having a spat over definitions. If you are setting the address in the router’s DHCP table, this is usually known as a “reservation” and it’s a router option, not a SONOS option. Regardless, the result is the same -- you have control over the player’s IP address.

If the SONOS players are dynamically assigned an IP address, it is common for duplicates to develop during a SONOS firmware update. Reservations prevent this. In my opinion it is pointless to assign blame for this, especially because there is an easy, permanent fix. You’ll discover hundreds of discussions about this.

I think what I originally said was perfectly clear, static addresses set via binding. Nothing strange about it. Every device in our house has a static address this way. 

What in the world is “binding” I’m not finding that.

Could you be meaning to say DHCP assignment?

Binding an IP to a MAC address is the same as DHCP assignment.