Avid Contributor III

Answered

Unable to add my Amp to the network ...

Forum|Forum|2 years ago
October 22, 2023
93 replies
2022 views

Hello,

Our Sonos system consist of 2 Boosts, 5 Connect Amp compatible with S2, 1 Amp and 1 Arc. The Connect Amps are distributed in the home while the Arc and Amp are in the living room connected to our television. Boosts are needed to extend the Sonos network.

I recently realized that a part of our home internet network was not working. Some ethernet connections needed to be worked on. I had to make changes in the wiring and the connections.

I suspect that part of my problems were created when adding a TP-Link Deco mesh system on my home network to have a better signal in all our home that is not ethernet wired entirely.

So I played around with all the wires and cables of our internet and Sonos networks. When reconnecting everything, my Amp was not recognized anymore on my Sonos network and my Arc’s button were not responsive anymore. I don’t know if the 2 problems are caused by the same problem.

So I tried very hard to have my Amp recognize by the network. I also tried resetting it to factory settings many times with no success. Later, it did recognize the Amp by was never able to add it to the Sonos system.

This morning, I moved the Amp near my main Boost. I reset it another time to it’s factory setting. This time the Amp was recognized and added to the system, but Sonos said it was unable to add it to displayed configuration of the Sonos app. I tried once more with no success.

Over the years, I never had problems configuring or making changes to my Sonos configuration with my older S2 compatible Connect Amp. I never had any problem. Everything was a breeze. I was always surprised how simple the Sonos setup was taken care of.

Since the newer Amp, configuration has been tricky, quite complicated and not straightforward anymore. Is it my fault or caused by our more complicated internet network or is the new Amp more flaky, I don’t know. One thing is sure, I have done a-lot of work and I am at the end of my personal options.

Can anyone help me going further fixing my 2 problems ?

Thanks in advance.

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.

Best answer by rlesperance

Hello glad helpers …. I just wanted to make a follow up on my case. Calling Sonos helped to focus on the hardware problem.

The Sonos Amp was not connecting because it was blocked from the TP-Link Deco system. Sorry to say that. I don’t know why and how it was blocked but once unblocked, it simply joined the network smoothly and simply as all Sonos devices always did. I learned that the Sonos Amp can self diagnostic iitself by displaying different color signals.

I I had 3 blocked devices. Not sure what they all were yet. But now that they are unblocked, everything got back to Sonos normal and simplicity. Even the Apple TV (salle familliale) connected to the Deco system.

Ken … I also called Videotron. I was able to have my other Apple TV (not shown on the diagram) joined the Deco network through B2 and thus could disable the repeater like you suggested. I did not convert my ISP’s router to a bridge … yet.

So thanks again for being supportive.

P.S. The diagram has been updated.

Show previous replies

Ken_Griffiths

So it’s

IR—→ PDH—-Boost 1

Just leave your GES (switch) out of the setup - it’s a just a temporary measure and let all your Sonos devices show up in the Sonos App and then try setting up the Amp via Add Product.

Ken_Griffiths

I thank you very much for trying and doing your best. I will give Sonos a call.

Before you do give up and walk away, is it possible that you have ALSO wired your GES switch to you IR - in addition to wiring IR to the PDH —my reason for asking is your Apple TV is using the IR wired subnet, rather than the Deco subnet… and that’s causing me some confusion🤔? It’s like something else is wired to your ISP router when in fact things should ALL be wired to your GES (switch).

ratty

Why on earth don’t you just wire the Amp to the second port of the Boost (B1)? It only needs to be a temporary connection. If even that doesn’t allow you to add it to the system there’s something really wrong.

The OP has actually setup the Amp in the past when wired - it’s when they then try to run it wireless afterwards that he has had issues.. it seems quite clear now that the wired network (as can be seen from the Apple TV screenshot) is a different subnet to the WiFi network SSID "LespeReeves” being used by the iPhone mobile controller device - the user needs to switch their mobile controller devices to connect to the other WiFi network - sadly it seems they do not know the ‘other’ SSID, or how to access it - I don’t even know myself (yet) if the Deco WiFi and IR WiFi (incorrectly) have the same SSID.

Even when the Amp is setup here and working, it seems to me that the OP’s local network setup will still need looking at in detail, as it seems like it’s in a bit of a mess and certainly split across two subnets.

Well, yes, there’s definitely some uncertainty about how the network is configured, and there are obviously two subnets with different SSIDs.

I was simply reacting to the fact that the Sonos controller could evidently see the system via a Boost (#1) wired to the primary mesh node. Ergo the Amp ought to be easily addable wired, or even wireless.

On reflection there could also be something odd as a result of the daisy-chain through several switches and Deco node #2.

Ken_Griffiths

@ratty,

Thanks for the assistance - I think that there’s certainly an issue with @rlesperance network and it maybe best (much quicker/easier) for @rlesperance to talk things through with the Support Staff over the phone as it’s clear that he has some difficulties making changes to the two routers etc.

I have one quick question though - might the class 4C subnet mask (255.255.252.0) - 1k addresses possibly cause Sonos any issues - I appreciate it’s the same subnet, but was just wondering? I couldn’t test this as my VM/Plume setup does not allow me to change the third octet here? It makes the host address 10 bits rather than the usual 8.🤔

ratty

I have one quick question though - might the class 4C subnet mask (255.255.252.0) - 1k addresses possibly cause Sonos any issues - I appreciate it’s the same subnet, but was just wondering?

Deco evidently chooses to issue /22 addresses, presumably to allow for a plethora of IoT devices. I don’t see how it ought to matter.

R

rlesperanceAuthor

Avid Contributor III

Thanks all for being helpful.

In all my set ups, the only thing I did is connect items together, and let the system arrange itself. I never modified any SSI ID, or IP addresses.

As for being unable to have wired and unwired Sonos devices on the network, why is that ? Do I read in your comments that's it is possible but for some reason in my network it is not or is it impossible to have both at the same time ?

Ken_Griffiths

Thanks all for being helpful.

In all my set ups, the only thing I did is connect items together, and let the system arrange itself. I never modified any SSI ID, or IP addresses.

As for being unable to have wired and unwired Sonos devices on the network, why is that ? Do I read in your comments that's it is possible but for some reason in my network it is not or is it impossible to have both at the same time ?

I’ve never seen a message where a wired device is not allowed - In larger Sonos systems in fact, at one stage, it was sometimes helpful to wire several products to the LAN (just not to Mesh satellite hubs) and it’s not always good practice to wire a Home Theatre Surround, or Sub, to the LAN either where the ‘main’ player is wireless.

I think the issue in your case @rlesperance is the different routers/subnets you have setup and what appears to be a double NAT configuration. I’m guessing you have more than the Deco Primary Hub wired to your ISP provided router too. Sonos Support will hopefully be able to sort it with you a little easier over the phone.🤞

Anyhow…

@ratty - thanks re the /22 address reply.👍

ratty

Just a few comments:

Double NAT is not an issue per se. My system’s behind two routers. (I’ve also run systems in Triple NAT).
Being on the wrong side of a secondary router absolutely is an issue, as it would put the controller on the wrong subnet. Sonos controllers need to be on the same subnet as the players.
I’ve never ever seen a message telling me I couldn’t wire a Sonos device. And I’ve had a mix of wired and wireless devices for 15+ years.
Wiring the second Boost through the Deco satellite might not be a good idea. Some meshes use a flavour of STP (Spanning Tree Protocol) for loop avoidance which could potentially get into a fight with Sonos’ STP variant. If the switches have STP as well things could also get messy.