Skip to main content
Contributor I
January 6, 2017
Answered

Changing the name of a speaker

  • January 6, 2017
  • 32 replies
  • 5460 views
I just moved a speaker to another room. How do I change its name so I don't have multiple speakers with the same name?
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 jgatie
Seting->Room Settings->(Room name), tap on the room name to edit.

32 replies

Contributor II
February 5, 2019
Wireless. My router is linksys velop. Verizon gigabyte. I just got off the phone with a Sonos support. Based on the rep recommendation I hard wired a sonos one to the router and then change the names of the speakers. I then remove the sonos one from the router. I will monitor now to see if issue continues. The rep suggests that I get a Boost as the speakers are not all on the same channel. The next step is to reset to factory setting.
February 5, 2019
Don't factory reset it is pointless at best. Do you have Apple Homekit by any chance?
ratty
February 5, 2019
Wire one Sonos component. A Sonos system in WiFi/'wireless' mode attached to a mesh WiFi is not a good idea. With the players forced to use different channels, performance will be suboptimal.
Contributor II
February 5, 2019
Yes to the Apple Homekit but I hardly use. I plan to purchase the Boost to hopefully improve performance. Is getting the Boost a waste of money when I plan to set up a home theatre and two sonos ones will be in the same Media Room. Since I hate wires all the equipment including the mesh network are located in a closet and the position of the second sonos one hard wired to the Mesh network might not be the ideal location. The second issue is the velop router only has one ethernet port which i current use for vonage. Thanks for the feedback.
ratty
February 5, 2019
Is getting the Boost a waste of money when I plan to set up a home theatre and two sonos ones will be in the same Media Room. Since I hate wires all the equipment including the mesh network are located in a closet and the position of the second sonos one hard wired to the Mesh network might not be the ideal location.If the Ones are intended to be surround speakers, using one of them as the sole wired device is not recommended.

The second issue is the velop router only has one ethernet port which i current use for vonage.
The Boost has two Ethernet ports, partly to cope with this kind of situation. The Vonage could be daisy-chained through the Boost.
Contributor II
February 5, 2019
Appreciate the feedback. I will purchase the Boost.
Airgetlam
February 5, 2019
John B’s question about Apple HomeKit is relative as there have been several issues reported in this forum where the HomeKit app appears to be resetting/controlling the name of the speaker. Some users have reported changing the name in the Sonos App, and finding that the name gets changed back to what the Apple thinks it is.
Bruce
Steve_144
Lyricist III
July 26, 2019
You are no longer allowed to change the name of a speaker using a PC or a Mac. Because Sonos hate us.
Are you telling me I can no longer use use windows (or a PC) any more to update my rooms. Let me say this, I do not think Sonos hates us, but as a retired IT person of 30 years I will say this: Sonos is losing their innovative edge or in other words losing perspective of technology. I am a Canadian but will quote a famous US president : not because they are easy, but because they are hard: Sonos is becoming a company that is taking the EASY way out.

After thousands of dollars invested in Sonos and losing components yearly, I conclude: when I lose my Play 5 (about a year or 2 out), l will go back to hard wiring speakers to amplifies. Strange, all my old speakers and amps still work! Out lasting Sonos by 30 or more years. (this is Fn true).

Here is a thought for you millenniums, Why do we spend money on stuff and shortly send it to the landfill. So not environmental!

Have a Nice Steve
Airgetlam
July 26, 2019
I'd say maintaining four separate paths for the code base was onerous, and expensive. The decision to remove that support came around (but not concurrent with) when the company went public. I'm taking the position that it was an effort to concentrate the available resources where the user base was. While we don't have access to numbers, I'm sure the person who took this decision did, and I'd guess that the number of desktop OS users were much smaller than user numbers for mobile controllers.

It's mildly inconvenient at times, but not terrible, for me.
Bruce
ratty
July 27, 2019
Also, one should distinguish between the number of desktop OS users, for simple playback control, and those who configured their systems that way. The latter could well be a small proportion of the former, given the convenience of a handheld device for set up, and the desire for follow-on activities such as Trueplay and adding voice control.