loving my Sonos One SL + Move system - except that when I pause the music and the Move goes to sleep, it doesn’t wake back up. The light comes on, and the buttons respond with little blip noises, but the app doesn’t see it as awake. Tried all of the things the app suggests to do, it just never sees it awake and ready. If I put it back on the charger, it will eventually wake up - but I make it wake up when I want to. I see a similar discussion here on the Roam - anyone else seeing this with the Move?
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Page 1 / 2
What you describe matches my experience... but still getting mucked up status in app. Says asleep when clearly not. Did the reset you suggested...now says powered off, when clearly not. I can even get it to play using voice control ... whilst app still says unit is powered off!!! Some funky stuff going on Sonos ..
Hope there's a fix out there soon!
I would try a reboot of the local router and mobile controller device. Also power off the speaker off it’s charger by holding the rear power button for 5+ seconds until you hear the descending shutdown tones, wait 10+ seconds and return the Move to its charger loop and see if that fixes the issue. If not then try a Sonos App reset as mentioned in this link:
https://support.sonos.com/en-us/article/reset-the-sonos-app
Then follow the instructions to connect the App to your existing Sonos system.
Hope those suggested steps helps you to fix the issue.
just tried this. App says it’s in Sleep mode. Press power button. Small beep, White light comes on. App still says sleep mode. Pressing play button, makes a two-toned beep, then white light flashes red for 2 seconds. I don’t do any voice control, so not sure about that.
I put it back on the charger - charging light at the bottom comes on for only about 30 seconds, so the battery is very charged. Still in sleep mode 15 minutes later. Force quit phone app, restarts - still in sleep mode. While on the charger, power it off, then back on - still in sleep mode.
Power it off and leave it off for 30 minutes. Powered it up - still in sleep mode.
Shut it down by holding the power button down for 5 seconds - makes a noise before turning off. Leaving it off for 15 minutes, then restarting with a normal button press. now the white lights pulses, while rebooting, then it finall comes online.
so - have repeated this, with success.
1 - Move goes to sleep.
2 - wake it up by pressing power power button. (App will say is still in sleep mode)
3 - SHUT DOWN, by holding power button for 5 seconds or so, it chimes as it shuts down.
4 - restart with power button press - light will pulse while it’s booting up, then it will show up in the app.
Hope this helps others. Still hope there’s a firmware fix sometime...
What you describe matches my experience... but still getting mucked up status in app. Says asleep when clearly not. Did the reset you suggested...now says powered off, when clearly not. I can even get it to play using voice control ... whilst app still says unit is powered off!!! Some funky stuff going on Sonos ..
Hope there's a fix out there soon!
Yes it did Ken. Thamk you for pointing me in the right direction!
I think I have solved it. But I am not happy with Sonos for the issue. Switching from the newer standard Rapid Spanning Tree Protocol (RTSP) to the older Spanning Tree Protocol (STP) seems to have fixed the problem. Discovery of the Move is now immediate. And that would also explain why my older, cheaper router would not have had a problem ... it likely also defaulted to STP.
Ah glad to hear the Unifi & Sonos document link helped you to sort it.
Userlevel 7
+22
At some point Sonos will switch to newer system internals and the Linux they are using should then support RSTP and a lot of other newer protocols. No idea when but I do know it will be a huge and expensive change.
I think I have solved it. But I am not happy with Sonos for the issue. Switching from the newer standard Rapid Spanning Tree Protocol (RTSP) to the older Spanning Tree Protocol (STP) seems to have fixed the problem. Discovery of the Move is now immediate. And that would also explain why my older, cheaper router would not have had a problem ... it likely also defaulted to STP.
Thanks Ken. I will continue experimenting. But it shouldnt be this hard! Sigh.
I agree. It’s not something I have seen widely reported though here in the user community, so my thoughts are it’s a local network/controller discovery issue (something to do with your local setup) and I’ve just simply listed all I can think of (off the top of my head) to try to assist you to perhaps sort it, rather than just letting it reoccur. Honestly I’m not seeing the issue here, so it likely is something closer to Home.
Thanks Ken. I will continue experimenting. But it shouldnt be this hard! Sigh.
I have a Ubiquiti Dream Router. Default config. Both my phone and the Move are on 2.4ghz wifi channel, same SSID.
I don’t know your chosen router (sorry), but maybe see if this link, that I stumbled upon, might give you some things to perhaps try…
FWIW - My WiFi is a plume WiFi AX mesh system (UPnP enabled). All Sonos IP addresses are reserved in the routers DHCP reservation table.
I am using iOS Sonos controllers (iPad/iPhone) - On those controller devices I have no security software enabled like VPN, Firewall etc. I have disabled WiFi calling, switched off mobile data access by Sonos App. I have also disabled ‘Private WiFi Address’ (MAC spoofing) in its WiFi connection properties.
So maybe try some of those things, as perhaps that might help you with device discovery across the LAN subnet.
I have a Ubiquiti Dream Router. Default config. Both my phone and the Move are on 2.4ghz wifi channel, same SSID.
Note when the Move is on its charger-loop, the speaker is merely in ‘standby’ rather than ‘sleep’ mode so you should always see the speaker when it’s on its charger. My Move never fails to show here.
Hi Ken. My Move is on its charger most of the time 99.99% of the time. It doesnt make a difference one way or the other.
My thoughts are it’s some kind of device-discovery issue across the network - it might perhaps be something on your mobile device blocking its discovery, or the multicast discovery packets are having issues communicating across your network/router. What router and mobile device are you using?
Hi Ken. My Move is on its charger most of the time 99.99% of the time. It doesnt make a difference one way or the other.
Hi Ken. Thank you for the reply. I wish it was that easy. The battery saver is OFF.
FWIW, I’m not seeing the Spotify ‘direct connect’ issue here - but I mostly leave my speaker on its charger 24/7 when in the Home and if I do move it around the place then its mostly playing and awake. I have the battery saver enabled.
Hi Ken. Thank you for the reply. I wish it was that easy. The battery saver is OFF.
I am having similar problems with my Move. If I leave it alone for more than … an hour? … it disappears from Spotify Connect. I have to go in to the Sonos app on my phone. It will first complain “Unable to connect to Sonos”, but I ignore that message and just let it sit. Within about 30 - 60 seconds, the Move will appear in the app. I can then go back to Spotify and within 30 seconds, the Move will then appear there through Spotify Connect. This works, but it is a pain in the ass. I have had my Move for about 1 ½ years. I have never had this problem until a few months ago. I am suspecting a firmware problem. Sonos … any comment?
What power saving options are you using with your speaker? See this link:
https://support.sonos.com/en-us/article/battery-settings-for-portable-sonos-products
Unlikely to be a firmware issue, or you’d see thousands upon thousands of posts on a similar vein. What did Sonos Support say when you contacted them?
I am having similar problems with my Move. If I leave it alone for more than … an hour? … it disappears from Spotify Connect. I have to go in to the Sonos app on my phone. It will first complain “Unable to connect to Sonos”, but I ignore that message and just let it sit. Within about 30 - 60 seconds, the Move will appear in the app. I can then go back to Spotify and within 30 seconds, the Move will then appear there through Spotify Connect. This works, but it is a pain in the ass. I have had my Move for about 1 ½ years. I have never had this problem until a few months ago. I am suspecting a firmware problem. Sonos … any comment?
I was getting some spotty wifi coverage out in the backyard, so I upgraded to a mesh router system, and for whatever reason, the Move is working perfectly now - wakes up after going to sleep. I don’ even need to touch it - just select it as the speaker I want and it wakes up within a sec or two. Pretty awesome. Sorry it doesn’t help those who are having issues with their Wifi!
the work round of powering off and back on? It’s always worked for me, and I’ve not heard of any software update. I also haven’t tried the other suggestions about alternate wifi or whatever. Sorry I’m no help!
So I have a variation on this issue with my Sonos Move, which started 3 days ago after we’d been on holiday for 4 days so none of the speakers (Beam, Move, Roam) had been used. House wifi remained on.
The Move is fully charged, online, up and running and responding to Alexa commands as normal.
But in the app running on my Samsung A54 it shows in Sleep mode, even though it is playing music via Alexa. When I touch on the speaker in the app it helpfully tells me its asleep and I need to press the power button. More curiously in the iOS app on my iPad Mini the Move doesn’t show up at all. The other two speakers (Beam and Roam) are working fine through either app.
I’ve restarted the Move which made no difference. Works fine through Alexa so its obviously connected to the wifi but still shows in Sleep mode on Android and is missing on iPad.
Suggestions?
I followed your work around without it working. I reset the Sonos app and the move appeared….for now😓. Is there a software fix ?
So a few days ago I bought a cheap wireless router on Amazon and setup my Sonos devices to that wireless network. So far it seems to have fixed the issue.
I have a Century Link C3000Z that came with my fiber service. I set it up 4 years ago and I have no idea how to do that again. LOL...
Page 1 / 2
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.