Sonos speaker ungrouped and failing after the scheduled reboot of my deco wifi-system

Do you have a specific reason for rebooting the Deco's? Just curious - I own a couple of them myself.

When they restart, how are they configured? Are they still locked to a single wifi channel, or Auto hopping for best signal? Sonos devices don’t like channel hopping environments.

Have you set ip addresses for your devices, or might the restart be causing duplicate ip address conflicts? 

To me, there seems to be a number of reasons why this reboot action causes problems for Sonos devices. Without more information about your setup, we in the user community can only guess. Sonos support might be able to help if you generate a diagnostics report and contact them? 

I too am curious as to why you reboot your network so often? In fact I never reboot my mesh network unless I have a specific reason to do so which isn’t often.

As others have said you run the risk of creating duplicate IP addresses which can be problematic for Sonos even with static IP addresses assigned. As you have discovered the rebooting of your network causes Sonos to take a while to recover.

So as far as your question is concerned you don’t have an issue with Sonos. The time it takes Sonos to recover after rebooting your network is expected behavior. The recovery time will vary depending upon network configuration as well as the number of Sonos units involved and their configuration (ie bonded Subs and/or bonded surrounds). Also, the ungrouping and failed alarms are collateral damage.

The solution for Sonos is to stop the frequent network reboots with or without static IP addresses assigned.

​@106rallye , I reboot the deco’s due to stability issues after a certain while operational. Approx after 2 weeks the performance and stability of the decos begins lowering.

What??

There has to be a reason causing the performance degradation. Have you contacted the manufacturer or maybe even your ISP?

Not to be rude but; if there’s no plausible explanation may be it’s time to get newer network hardware (different brand). 🤔

EDIT:

After looking at your profile I see you have a Play:5 (gen1). Some of your other gear such as the ARC are not compatible with the Play:5 (gen1) Sonos S1 operating system.  The Arc is Sonos App (S2) only. You should be running separate Sonos S1 and S2 systems. I’d advise reading the information in this link.

I don’t know if there’s any correlation with the above and the degradation of your Deco network. You’d have to run a diagnostic and contact Sonos Tech Support and/or your ISP.

​@AjTrek1 The devices are brand new, TP-Link / Deco has this built-in feature “Reboot Schedule”. I guess for a good reason, not for fun ;-). I am researching for the cause since a long time without success.

​@Robert.CapeTown 

Thanks for the response. Take a look at the EDIT to my last post. My Asus AiMesh also has an option for scheduled reboots. However, I don’t have a need to use that option. Just because it’s offered doesn’t mean you should.

Below is an AI generated take on the necessity for rebooting a network on a frequent basis. Read the entire article to decide if you think it’s necessary in your situation. You might even call your ISP and or the manufacturer to get a take on the necessity for scheduled reboots.

A weekly network reboot can improve performance by clearing device memory and refreshing connections, but whether it's necessary depends on your network's complexity and the devices connected. Home networks with many connected devices may benefit from weekly or monthly reboots, while professional IT infrastructure typically schedules reboots only for maintenance or to resolve issues. Many modern routers and access points offer built-in scheduled reboot functions in their management apps or web interfaces. 

Reasons for Weekly Reboots 

• Improved performance: 

  Rebooting devices like routers and modems clears their temporary memory and cache, which can accumulate over time and lead to slower performance or higher latency.

• Connection reset: 

  A reboot refreshes the connection to your Internet Service Provider (ISP) and helps the network find the best WiFi channel, reducing interference.

• Stability: 

  Clearing out temporary settings and renewing connections can make the network run more stably.

When a Weekly Reboot May Not Be Necessary

• Home networks with few devices: 

  Networks with a small number of devices might not experience the same memory buildup and can often be rebooted monthly or even less frequently. 

• Stable and well-configured networks: 

  If your network is performing reliably and you don't experience slow speeds or frequent disconnections, there's no need for regular reboots. 

• Critical infrastructure: 

  In a professional IT setting, critical systems are typically not rebooted routinely; reboots are reserved for planned maintenance windows. 

How to Schedule a Reboot

• Router/Access Point Apps: 

  Many routers and mesh systems, such as TP-Link,ASUS, and Linksys, have scheduled reboot options in their dedicated management apps. 

• Web Interface: 

  You can often access similar scheduling features by logging into your router's web-based administration interface. 

• Device-Specific Tools: 

  Some enterprise-level tools, like Cisco Wireless Access Points (WAPs) or professional network management systems, have their own methods for scheduling reboots. 

Having said that, you should be able to see all speakers after a restart. Ungrouping after a loss of connection might be normal for Sonos as this depends on a stable connection.

Maybe give your speakers a fixed IP address? Or make a diagnosis when it happens and call Sonos?