Skip to main content
Trending Lyricist I
February 29, 2024
Answered

Incompatible Software Versions - S2

I used to love Sonos. Now I only love their hardware…

 

I have 5 older speakers (4xPlay:1 and 1xPlay:5) that are not compatible with the new S2 system - but I don’t care. After many, many problems caused by relentless Sonos “upgrading” - I now drive my speakers through the Home Assistant integration which is magnificent. It does everything I want, and doesn’t bug me with extras I don’t care about. Unfortunately, it still requires the Sonos app to add a speaker to the system before I can use it in Home Assistant.

We just built an extension to the house and I wanted some more speakers in new areas. My investment in Sonos infrastructure was too great to move to another ecosystem. I was incorrectly advised by an Ikea salesperson, that their Sonos based Symphonisk range were S1 compatible - so I bought 3 of them. 2 x Bookshelf and 1 x Table Lamp.

When I installed the first of the Bookshelf speakers shortly afterwards I discovered they were S2 only. I was very annoyed - but after some research shut down all my S1 gear, installed the S2 app on my iPad Pro, and configured that speaker as a solo unit on its own “network”. Home Assistant didn’t care, and all 6 of them have been working together happily for many months now.

The builders have finally finished the construction so I’ve now gone to install the last two Symphonisk units. Again shut down my entire S1 network - and fired up the S2 app on the iPad. It found the Table Lamp speaker and installed it fine (fell over at the Registration system - but registration on the Sonos website is not required for the speaker to work in Home Assistant.)

Then it discovered the other Bookshelf speaker - but will not even attempt to install it - claiming the infamous “Incompatible Software Versions” error. All three Ikea speakers were bought on the same day, are installed on the same network, with the same App on the same iPad. Two of them worked, and one is apparently “incompatible”.

I checked the S2 App for updates (we all know how much Sonos loves updates) but it tells me there is no update available. All my S1 equipment is disconnected and so not relevant to the issue. And I can’t access the new Bookshelf speaker in any way to tell what is happening with it.

What can I do?

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.
pcalAnswer
Trending Lyricist I
April 5, 2024

OK. So I have fixed my own problem - which had nothing whatsoever to do with the Bridge, or the existence of an S1 system or anything else I got pointed to here…

For the benefit of any others beating their heads against this same wall:

The “Incompatible Software Versions” error does not necessarily mean there are incompatible software versions in the system at all. Make sure your router is allowing connections (at least temporarily) to the Amazon address 52.52.194.122. This is where the system is hosted that determines if your software is compatible or not. If data can’t get through, your software is deemed incompatible no matter if is or not.

This address is also involved somehow in the APP being able to find your speakers on your own network. Missing speakers magically reappear when this address is unblocked.

13 replies

Corry P
Sonos Staff
April 5, 2024

Hi @pcal 

Thanks for updating this thread with your discovery, and I am glad to hear that you have resolved the issue.

Out of curiosity (and in case it helps anyone else with similar issues), how was it that the stated Amazon address was being blocked on your network? Are you using Pi-hole, or something similar? Or does your router have an in-built filtering system of some kind - if so, what make/model router do you have?

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
pcalAuthor
Trending Lyricist I
April 6, 2024

Out of curiosity (and in case it helps anyone else with similar issues), how was it that the stated Amazon address was being blocked on your network?

I’m using a Fritzbox router (7490 - but trying to transition to a 7590 - another long story!) with everything set to maximum stealth / security.

I’m also at the very far end of a FTTN connection on Australia’s NBN network which means my connection to the net is just a tad less than I used to get out of my old ADSL service. I do have a new fiber connection coming that should relieve that situation, but it isn’t here yet. As I have had no bandwidth to spare, in the early days I ran regular network scans with tools like EtherApe looking for systems that were hogging bandwidth - especially when I didn’t request anything from the machines in question. Pages of bandwidth hogging IP addresses got added to the http filters in the Fritzbox - and if no adverse consequences followed - there they stayed.

I haven’t added anything to those lists for several years so this address has been blocked for some time.

Curiously, adding the first 2 of my new S2 speakers worked without a hitch. It was only after a construction delay of a few months when I tried to add the 3rd that this issue arose, so logically one had no reason to assume a router setting that had been in place for many years would have had anything to do with it. I can only assume there was also some other change at the Sonos end that elevated the importance of this particular data pathway.

Perhaps Corry you could illuminate that issue for us?

Corry P
Sonos Staff
April 8, 2024

Hi @pcal 

Thanks for sharing those details!

Yes - we recently made the whole speaker setup procedure more secure, so things are a little different now than they were back when you set up your other speakers. The IP address you report is AWS (Amazon web Services) rather than, say amazon.com, as that is where the servers are hosted. So, nothing to worry about, over all.

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein