Answered

ROAM

  • 29 March 2024
  • 8 replies
  • 121 views
C
Userlevel 1
Badge

I am SO frustrated with this thing.   But I now think it’s an APP issue.  I have an original ROAM with a charging base.  I use it mainly out on our deck and grouped with speakers in the same area, ie: kitchen and family room.  Lately every time I use it then place it on the charger for the night the next time I go to use the Roam, it isnt in the app.  I have to do the main reset (12 Sec) then the roam will start playing whatever music the “group” that its not a part of is playing,  App says that its there, but powered off or asleep,  No amount of button pushing on Roam changes the app status but the music plays and volume is controllable from Roam.  All the SONOS products are great,,,,, this thing has been a head ache from day one!!!!  About to just relegate to a very expensive BT speaker.  Any one have a fix?   Again,, this time I think the issue is the app.

 

icon

Best answer by Airgetlam 31 March 2024, 03:50

View original

8 replies

Ken_Griffiths

The ‘discovery’ of the Sonos products by the Sonos controller App can sometimes be a slightly complex area to explore, but briefly… 

SSDP (the UPnP simple service discovery protocol) is used to initially discover the Sonos players and is done via multicasting via UDP to 239.255.255.250:1900 and, for good measure, broadcasting to 255.255.255.255:1900. 

Both the Sonos players and controllers must share the same network subnet. However if the Sonos devices are connecting to multiple access points, the recommendations (from myself) are that they be set to the same WiFi channel and channel-width. This is for optimum performance particularly in groups and for some reason with some (not all) mesh-based WiFi systems, it appears some will work okay with Sonos, but others may not, particularly if the satellites/AP’s are perhaps auto-selecting their own WiFi channels. I’ve seen some people report issues with Google ‘nest’ mesh WiFi, for example, although others will occasionally say it works for their ‘small’ Sonos setup.

What is certainly not supported though by Sonos, are wireless range extenders, as some can mangle device MAC addresses and EoP (powerline) adapters.. so if you are using those type of wireless access points, to extend the wireless network coverage, then that may cause such intermittent device discovery issues by the Sonos Controller App.

Reserving the IP addresses in the routers DHCP reservation table can often help with device discovery, so consider making your Sonos IP addresses static. The router user-manual will normally assist you to do that in most cases.

Just to add aswell, it can sometimes be Apps/software running on the mobile ‘controller’ device that interfere with ‘device discovery’ Examples to perhaps consider are…

  • VPN Client 
  • Firewall software
  • Antivirus software
  • WiFi Calling/Dial assist
  • Private network address (MAC address spoofing)
  • Mobile data enabled for the Sonos App  

So consider disabling these features, even temporarily, just to see if that may fix your device ‘discovery’ issue.

C
Userlevel 1
Badge

Ken

 

thanks. I will try hard IP addresses 

 

still baffled the Only issue out of 9 Sonos speakers that I have repeated issues with

 

Schlumpf
Userlevel 7
Badge +16

Just to add one thing to @Ken_Griffiths list of possible reasons:

Sometimes I saw people running in such an issue because an IP was listed twice on the routers IP list. Deleting the one and giving a new static one to the device or via DHCP sometimes solved the problem. 
So imo a check for double listed IPs also would be worth a try. 

Ralf
Ken_Griffiths

Ken

 

thanks. I will try hard IP addresses 

 

still baffled the Only issue out of 9 Sonos speakers that I have repeated issues with

@cooperd5908,
If you do still encounter a problem and you think there maybe a fault with the product, then (when the Roam is showing in your App) you can always submit a Sonos system diagnostic report from within the Sonos App, note it’s reference and then contact/chat with Sonos Support Staff via this LINK and see what the Staff can perhaps suggest to resolve the matter.

buzz

Just to add one thing to @Ken_Griffiths list of possible reasons:

Sometimes I saw people running in such an issue because an IP was listed twice on the routers IP list. Deleting the one and giving a new static one to the device or via DHCP sometimes solved the problem. 
So imo a check for double listed IPs also would be worth a try. 

I caught my router pulling this stunt. An unreserved SONOS ROAM pair was given the same IP addresses reserved for two unrelated clients. The reservations were made a year or so before the ROAM’s were installed.

C
Userlevel 1
Badge

Update.  

I gave every Sonos device in the house a static IP. Repowered speakers and router.  All devices confirmed with new static IP.  Worked for a bit so, I put the roam back on the charger while playing.  Got up this morning, Roam still on charger still has white light.  Open App - No Roam.

Take Roam off of charger - No Roam, Press Power button light goes dark, press again, get white light and Roam shows in app as asleep. Back to same old problem, it would still play music from another group of speakers even though app says its asleep.   So then do a 5 sec press, Roam comes back on and App now sees it.  WHAT A PAIN.  My MOVE has never done anything like this. It apps that in order for the App to see it (see everything else) the Roam needs to be totally reset every time you want to use it.   This problem is about a month old. It never did this before and the move doesnt so still thinking it is an app issue.

 

Thanks

Doug

PS: also confirmed no duplicate IP’s, and Router is Netgear MR63.  

buzz

In general routers will not report duplicates, although some will. My router tends to attract ‘fires’ when you search for it on the Internet. I have made it a practice to reboot the router once a month.

It may be productive to Factory Rest the ROAM. As you restart it, take care to add it to an existing system, don’t accidentally setup a new system.

Airgetlam

You’ve certainly reduced the variables, which helps. If @buzz ‘s suggestion doesn’t work, you’re in a better position to submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Bruce

Reply


Terms & ConditionsCookie settings