Bring back http://:1400/reboot
Left stereo paired Sonos Play:1 plays sound.
Right stereo paired Sonos Play:1 is silent.
The only thing that fixed the right stereo paired Sonos Play:1 was to power cycle the Sonos Connect.
Shouldn't need to schlep across the house to unplug a power cable, and spend an eternity trying to plug it back in, when the device is already connected to the network.
Let me reboot it from my computer.
Let me reboot it from my tablet.
Do I really need to buy a WeMo outlet to accomplish this?
Setup...
Router -> (ethernet) Sonos Connect -> (SonosNet) 2 - Sonos Play:1s (stereo paired)
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
Same here. Added some new devices, changed them to static mapping, now have to go unplug them instead of issuing a quick reboot command.
The Sonos app can issue reboot commands for devices as part of updates, should be exposed via the app for our use as well, even if it’s not an api call or url.
I just made DHCP reservations and need to reboot 11 devices to get their new addresses. I thought it would be nice to hit a URL or a button in the app, but I guess instead I’ll pull out the couch, move the tv and climb a ladder instead. You can add me to the list of “wish I didn’t hafta”s.
Worryingly on a recent tech support call, the very friendly and competent chap helping me rebooted all my devices remotely...
I would like to add that if you have found your system regularly needs a restart, there may be some underlying issues that our support team can assist with finding on your network which may remove the need for these reboots.
I would like to add that if you have found your system regularly needs a restart, there may be some underlying issues that our support team can assist with finding on your network which may remove the need for these reboots.
I'm annoyed by the removal of this option and the views of diagnostic data, however, I will point out that I don't reboot my units from one year to the next -- unless there is a major change in the network. If the network has collapsed to the point where I can't contact a player, having the option to reboot the player from the network is not helpful.
I just completed rebooting 8 Sonos devices. They are located on three floors and two of the devices required me to (dangerously) climb up a ladder. This is why we need the once active IP:1400/reboot command feature.
Micro outages are a big pain because some items might go down and reboot, while others might continue, but dazed and confused. Do you have a UPS (Uninteruptable Power Supply) available for the router? Including BOOST on this would probably be helpful too. At least reserve IP addresses for all regular network clients.
I have to reboot some or all of my sonos devices from time to time because they just stop playing. this happens several times a year. remote reboot was good, because a lot of those devices are difficult to unplug/replug. disabling remote boot is totally stupid. in the past i have already ditched blue note in favor of sonos because it seemed to work better and with less glitches, but it looks like it’s time to switch again.
people who randomly open their network ports deserve to get hacked.
One troubleshooting approach worth trying (to rule out other causes) would be to plug an ethernet cable between the two play:1s and run it for a while to see if this problem goes away. Then you should get back to Sonos Support and explain the problem, see if they can give you some pointers (or if the right Play:1 is actually faulty).
When you power cycle the Connect, you effectively cut the wireless link to both Play:1s, and the renegotiation of the link seems to be what brings it back to life. Or, you are forcing the right play:1 to connect to the left:1 directly.
I would also consider swapping place of the two speakers, to see if you get a different problem in that case (both going silent perhaps). This means, also unpairing them and re-pair them with opposite channels (R becoming L, and L becoming R)
I have 3 'Connect', 3 'Play:3' , 5 'Play:1' and a Boost.
In my area, we have a lot of micro power outages, and each time this happen, it take quite a long time ( days ) for the mesh network to find the 'best path'. During that time. I experience cuts in audio, etc ..
Over time, I learned the best 'boot' sequence for each devices, and it was easy to restart each device in the right order. But now, it I have to go to each device and unplug/re-plug ... which is somewhat a pain ( Ok - yes I am lazy )
The reboot option was really useful for me.
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.
finsprings Get a Boost or wire one or more of your existing Sonos devices and move your Sonos off your home WiFi. I am so much happier now that I've done that.
I don't see how that would be possible, if this direct routing is in effect it would choose the cable over a wireless link, since it would have a fixed path cost of 10.
If some of your access points are unavailable, of course they are gonna connect to the one available. If they still have decent signal, they won't roam to another unit. Maybe the Sonos unit could have more aggressive roaming, and maybe you should raise that issue with sonos, it is a possible scenario that becomes more and more common with all the new wifi mesh solutions coming up.
Some access points have the possibility to de-associate units, which makes them disconnect. That would make them re-evaluate which is the strongest AP and do the same thing as the reboot, probably. But you might also wanna adjust the signal strength of your access points to better balance unit onto the right AP, and not run all of them on full power.
I don't see how that would be possible, if this direct routing is in effect it would choose the cable over a wireless link, since it would have a fixed path cost of 10.
Cabling between units in this way appears to defeat the Direct Routing algorithm which, remember, is designed to be a wireless shortcut between branches of the spanning tree. Under such circumstances the system reverts to the STP topology. If the root path costs of the two units differs by less than 10 the wire won't be used, and the traffic has to take a long trip via a more distant node.
Cabling between units in this way appears to defeat the Direct Routing algorithm which, remember, is designed to be a wireless shortcut between branches of the spanning tree. Under such circumstances the system reverts to the STP topology. If the root path costs of the two units differs by less than 10 the wire won't be used, and the traffic has to take a long trip via a more distant node.
That sounds completely broken, tbh. Couldn't have been intentional, and sounds like a massive bug.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.