Bring back http://:1400/reboot

Don't you rather want to avoid rebooting at all?
Of course!
However, the issues are infrequent, and not reproducible at will.
It's just a pain to need to power a device off, and back on, when it doesn't have a power button, nor remote reboot capabilities.

Hey guys,

thanks for the great interaction in this discussion. I feel the same like most of the advanced user at the moment.

My Situation: I live in a house with 4 Levels and Sonos is spreed everywhere in ever rooms. Why ever the last update crashed a little bit my setup and it changed my root birdge. The RB was a wired boost direct plugged to the fritzbox, but now its in a secondary node and my BEAM in the living room (wirless) is set now as the RB :-(

Usually such things can happen (should not), but with few IP commandos quit fixed again.
1. [IP-ADDRESS] BOOST:1400/advconfig
2. [IP-ADDRESS] BOOST:1400/reboot
3. DONE!!!!

But the POINT 2 is no longer supported to change the RB back again easily !!! Pretty sporty in a house with 4 Levels!!!

MY HONEST REQUEST:
Please please insert that function in the controller(e.g. advanced setting) and also via the ip-commando like before. The possiblity to restart all devices with a one-click would be awsome

SORRY FOR MY FRANK WORD:
I KNOW SONOS HAS CHANGED THEIR TARGET GROUPE WITH FOCUS ON BASIC USER. BUT WITH SUCH SMALL CHANGES THE ADVANCED SONOS-USER GET BOGGED.

MY SUGGESTION:
FOR SUCH CHANGES ---> SPEAK TO THE YOUR BIG COMMUNITY BEFORE AND SEND OUT SHORT SUVERYS. THERE YOU WILL GET A IMPORTANT VOICE

Greetings
WoHA

Bring back /reboot I hate to crawl throught the house to reboot the 24 sonos devices just because of a new network setup. Stupid.

How often does your network screw up?? Maybe you should get a new router or something.

Perhaps @hcq doesn't have screw-ups, and merely wants to make all units re-request the DHCP server. I've done this a number of times when moving a household between subnets.

@controlav -- My Sophos XG does not neet to be replaced - it works fine (and could be rebooted remotely if needed). I changed SSID names, this made my SONOS stop working correclty. Nevertheless I do see the SONOS via sonos_ip:1400 and why can i play an mp3 via http-sonos-api (http://sonos_api:5005/room/clip/doorbell.mp3/75) to an SONOS "room" but not via the SONOS Mac OS app / Android App without rebooting the SONOS player?

Count me in for another +1 for reboot functionality. We have several Connects in awkward spots, and even getting to the plug for the Play5 is a nightmare (buried behind a rack) such that if I did want to reboot them it would be a pain. I have even rebooted stuff once when on the other side off the world and the OH was complaining of issues with Sonos.

Is the security risk that someone could reboot them? Someone who is already on my network. If that is the case I have bigger problems to worry about than missing a few minutes of radio.

How much of an issue? Well probably less than once or twice year. Wired network onto Ubiquiti UniFi network with USG-4-Pro-4, switches and APs. All Connects and Playbar, and Play 5 wired, a few Sonos 1s on Sonosnet. But unplugging 13 devices would take circa 30-minutes to complete. All because functionality was removed.

Is the security risk that someone could reboot them? Someone who is already on my network.No, someone on the internet. It was evidently found that thousands of Sonos units were visible across the 'net because 'unwise' users (I'm being charitable here) had forwarded incoming traffic to port 1400 on their devices.

How much of an issue? Well probably less than once or twice year.

Sonos updates are rather more frequent than that, and they obviously trigger a full system reboot. Unless of course you've elected to lock your system at some ancient version...

Is the security risk that someone could reboot them? Someone who is already on my network.No, someone on the internet. It was evidently found that thousands of Sonos units were visible across the 'net because 'unwise' users (I'm being charitable here) had forwarded incoming traffic to port 1400 on their devices.

That would have to be a deliberate act on the users part surely. I can't see a router having a default port forward to port 1400, and I don't see how you can accidentally set a port forward. Do we have to have wind-up players because some users opened their devices and licked the live parts?

How much of an issue? Well probably less than once or twice year.Sonos updates are rather more frequent than that, and they obviously trigger a full system reboot. Unless of course you've elected to lock your system at some ancient version...
Updates don't see me having to go round the devices rebooting them manually, the reboots are automatic. Maybe you misunderstood that the thread is about the user initiated remote reboot facility. I would hate to think you are just pedantically looking for things you can nitpick at. Maybe once or twice a year I want to initiate reboots, mainly due to network topology reasons, or I have had a switch out of action.

I am currently held back on updates but I await the day that a killer feature comes out that will make me want to abandon my CR100s in favour of the new killer feature. The removal of remote reboot functionality isn't that killer feature. I do read the version releases and all I can say is I am still waiting. Is the current app the bees knees, is the user base rejoicing in its simplicity of control?

It was evidently found that thousands of Sonos units were visible across the 'net because 'unwise' users (I'm being charitable here) had forwarded incoming traffic to port 1400 on their devices.

That would have to be a deliberate act on the users part surely.Correct. Hence my use of the bolded phrase above.

Updates don't see me having to go round the devices rebooting them manually, the reboots are automatic. Maybe you misunderstood that the thread is about the user initiated remote reboot facility.I didn't, and IIRC I was one of the first to complain about the loss. My point was simply that, for most users, the system gets a full reboot whenever a firmware update arrives. These days that's about the only time my systems restart.