Skip to main content

My Roam has, as it does occasionally, moved locations, so I factory reset it and added it to a different S2 system. Added fine, connected to wifi, all good, but it reports itself as “not registered”. There’s a “Fix It” button, which pretends to do something, but it doesn’t really.

This happens using my iPhone, my wife’s iPhone, her Mac and my PC. The Desktop apps refuse to allow any other speakers to be used. The Mobile apps allow basic access to other speakers, but block access to actual music selection (everything is greyed out).

Digging into the topology XML I can see that the reason the Roam is quarantined is “upnpovertls”, which is curious. (This translates to UPnP Over TLS).

I have reset the apps, ensured I am logged into the correct Sonos account, and still this Roam will not register, it is still quarantined.

 

I hate to ask you such an obvious question, but what did Support say, when you called in?

I certainly don’t have any better suggestion, unfortunately. 

Will the original SONOS system accept the unit?

Déjà vu?

I know is not exact same error as 2 years ago, but could it be a firmware version difference/mismatch if it has moved between systems?

That’s odd. I was all set to refute the possibility, when I looked at the hardware version on my S2 Roam, which is 1.33.1.8-1.9.

Which still means I don’t know. I’d think that ‘quarantined’ isn’t the right answer, it should be ‘needs updating’ or some such. The problem is his seems ‘newer’ than mine is. Our Version numbers match, though. 

But I’m afraid that only Sonos can ‘fix’ this, for whatever reason it occurred. Nothing is popping to mind, and heaven knows ​@controlav knows a lot more about Sonos than I do. 

Thinking about this a little more, Quarantine and UPnP Over TLS suggests a ‘trust’ issue with keys/certificates? I am curious, so would like to know what the actual answer is.

The irony, the Roam wont roam between systems. 😀

Déjà vu?

I know is not exact same error as 2 years ago, but could it be a firmware version difference/mismatch if it has moved between systems?

Firmware version matches.

Will the original SONOS system accept the unit?

That is 2000 miles away, so somewhat inconvenient to try.

That’s odd. I was all set to refute the possibility, when I looked at the hardware version on my S2 Roam, which is 1.33.1.8-1.9.

Which still means I don’t know. I’d think that ‘quarantined’ isn’t the right answer, it should be ‘needs updating’ or some such. The problem is his seems ‘newer’ than mine is. Our Version numbers match, though. 

But I’m afraid that only Sonos can ‘fix’ this, for whatever reason it occurred. Nothing is popping to mind, and heaven knows ​@controlav knows a lot more about Sonos than I do. 

Quarantined is the correct word, its how the device reports its problem in the topology XML. Previously I knew about Vanished devices (they are listed with their MAC address), but Quarantined devices were new to me. While it is in this state I swiftly added detection to my app, which is where the screenshot comes from.

A quarantined device is set up on the Wifi, it is a part of a Household (has an ID and is in the topology), but is not allowed to participate in playback or grouping. There is a reason code, which I listed, that is as far as I have got.

Thinking about this a little more, Quarantine and UPnP Over TLS suggests a ‘trust’ issue with keys/certificates? I am curious, so would like to know what the actual answer is.

The irony, the Roam wont roam between systems. 😀

Yeah its weird, I know they improved actual roaming in Gen 2 but this is a Gen 1, and has been moved in this way several previous times.

Will the original SONOS system accept the unit?

That is 2000 miles away, so somewhat inconvenient to try.

Different timezone? 

Fixed it: used the Android app! Clicking “Fix It” on that made it do things that the iOS app never did (asked to press buttons, specifically) and it fixed it right then.

I guess this kind of thing can happen when the codebase is different on the different platforms (unlike the old app, where only the UX was different).

Bonus: the Android app was also able to resurrect my old Boost, which the iOS app could not.

 

Definitely odd. I’m glad you reported it, hopefully the information will be passed on to someone who can look in to it.

Terms & ConditionsCookie settings