Contributor I

The end of SONOS is in sight...

11 replies
413 views

It’s obvious that SONOS doesn’t has the awareness let alone the knowledge / experience to understand that home and business networks are increasingly more complex and thus are on a rapid pace to make themselves irrelevant in the market. Privately, professionally and for my clients we’re no longer recommending Sonos. Not until segmented VLANS are supported via an advanced configuration option. There is NO technical excuse why this couldn’t / shouldn’t be made to work.

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.

Show previous replies

C

craigski

Local Superstar

What is your use case for VLAN(s)? Are all Sonos devices on same VLAN, and you want to access/control from another VLAN?

I have customer subnets that are large enough to require to have devices across various VLANs.. But yes.. I would like to access SONOS locally regardless of what local VLAN it lives on.

You can control the Sonos devices with the controllers on same VLAN, have separate VLAN(s) for other non Sonos devices? Why do you need to put controllers on a different VLAN?

Most (all?) consumer smart home devices don’t play nicely with enterprise networks, thinking out loud, Apple HomeKit/AirPlay, Google Home/Chromecast, Amazon Alexa, etc. If these products did support enterprise networks, consumers would have to pay enterprise prices.

Sign up

Login to the community