Contributor I

Answered

sonos are suggesting i replace my bridge with Boost - why?

Forum|Forum|7 years ago
August 26, 2019
39 replies
6082 views

Just received email from Sonos suggesting I replace my bridge with a boost. The mail is non specific as to why? Just really says it’s old!

my bridge is used as a stand alone booster to extend range of my Sonos to the garden (which is well covered by a mesh Wi-Fi system).

What exactly is “wrong” with bridge (apart from the known dodgy psu) that warrants replacement? Or is this a warning for end of support?

Alarms

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 ratty

I would have to wonder if there’s an upcoming change in the way the software/transmission works that makes SonosNet 1.0 no longer viable, and in order to mitigate issues, they’re attempting to get people to upgrade before that happens.Perhaps Sonos is being forced, by no-nothing magazine reviewers, to embrace "hi-rez" for no good technical reasons. It's mentioned in virtually every review as a "negative" of Sonos vs the competition. Would be sad, but marketing forces being what they are, who knows?

Possibly, but a more likely explanation is that Bridge is simply a growing support issue. Flaky PSUs can cause intermittent hard-to-trace problems. And as the linchpin of a SonosNet mode system Bridge has been outclassed for nigh on five years by Boost. Sat beside ever-more-powerful routers Bridge could well be feeling rather overwhelmed.

Show previous replies

M

Martin PigottAuthor

Contributor I

A Connect is Ethernet connected to my router, the bridge is only used try and extend the Sonos as far as our Summerhouse maybe 50-60m away. The Wi-Fi is no problem as I use 4x BT whole home mesh Wi-Fi nodes

Airgetlam

I would have to wonder if there’s an upcoming change in the way the software/transmission works that makes SonosNet 1.0 no longer viable, and in order to mitigate issues, they’re attempting to get people to upgrade before that happens.

Bruce

ratty

I would have to wonder if there’s an upcoming change in the way the software/transmission works that makes SonosNet 1.0 no longer viable, and in order to mitigate issues, they’re attempting to get people to upgrade before that happens.

But ZP100 and ZP80 use SonosNet 1.0.

chicks

I would have to wonder if there’s an upcoming change in the way the software/transmission works that makes SonosNet 1.0 no longer viable, and in order to mitigate issues, they’re attempting to get people to upgrade before that happens.

Perhaps Sonos is being forced, by no-nothing magazine reviewers, to embrace "hi-rez" for no good technical reasons. It's mentioned in virtually every review as a "negative" of Sonos vs the competition. Would be sad, but marketing forces being what they are, who knows?

Airgetlam

Aha, I had forgotten. So, it’s not what I suggested at all.

Bruce

rattyAnswer

I would have to wonder if there’s an upcoming change in the way the software/transmission works that makes SonosNet 1.0 no longer viable, and in order to mitigate issues, they’re attempting to get people to upgrade before that happens.Perhaps Sonos is being forced, by no-nothing magazine reviewers, to embrace "hi-rez" for no good technical reasons. It's mentioned in virtually every review as a "negative" of Sonos vs the competition. Would be sad, but marketing forces being what they are, who knows?

Possibly, but a more likely explanation is that Bridge is simply a growing support issue. Flaky PSUs can cause intermittent hard-to-trace problems. And as the linchpin of a SonosNet mode system Bridge has been outclassed for nigh on five years by Boost. Sat beside ever-more-powerful routers Bridge could well be feeling rather overwhelmed.

biggetjeindewei

Collaborator II

Interesting topic, as I’m also using a Bridge somewhere halfway the house to extend Sonosnet coverage.
The Bridge is hardwired and currently I’m not experiencing any issue.
Is there a way to check which Sonosnet is being used?

ps, I’m still using Sonos 9.1 on the iMac. My iOS devices all using SonoPad/SonoPhone and do not provide Sonosnet info

Maurice

ratty

The Bridge is hardwired and currently I’m not experiencing any issue.

Good.

Is there a way to check which Sonosnet is being used?

Devices with SonosNet 1.0 -- ZP100, ZP80 and Bridge -- will talk that to their immediate neighbours. Anything else will be using SonosNet 2.0.

ps, I’m still using Sonos 9.1 on the iMac.

Any particular reason you're so out of date?

biggetjeindewei

Collaborator II

Thanks for the info ratty.
The other Sonos component hardwired to my router is an ZP90. If that one is using Sonosnet 2.0, is the Bridge now limiting to Sonosnet 1.0 to my other wireless Sonos speakers?
The router and ZP90 are on the ground floor, Bridge and other speakers on second floor.

Wrt being hopeless outdated, I have no need to upgrade since I’m using SonoPad which I prefer above the Sonos app. Also my CR200 is still alive and kicking on 7.4...... 😉

Maurice

ratty

The other Sonos component hardwired to my router is an ZP90. If that one is using Sonosnet 2.0, is the Bridge now limiting to Sonosnet 1.0 to my other wireless Sonos speakers?
The router and ZP90 are on the ground floor, Bridge and other speakers on second floor.

As I say, the Bridge will be using SonosNet 1.0 to the wireless units which it's supporting directly.

The ZP90 would be talking SonosNet 2.0 to the ones on the ground floor, though it doesn't sound like you have any. It might be talking to some of the wireless devices on the second floor.

Show more replies

Sign up

Login to the community