Hey @chuckalicious,  beta discussion shouldn’t be taking place on the public community as we do try to keep all mention of being involved in beta tests confidential with the NDA everyone signs to be part of the program. For one reason, sometimes features are tested that will never make it into the product, and we don’t want anyone to feel left out. Sometimes during a beta test, a bug will surface that doesn’t have major enough impact to stop the release from going out as planned, assuming other features or software in it need to get shipped in a certain timeframe. We do a lot of work with other companies and software releases often are timed together, so depending on the severity of a bug, it may still ship. That doesn’t mean that a fix isn’t coming, and in fact, staying in the beta program is going to get you a fix faster than leaving it (assuming the bug is in the current production build). 

We’re working on that issue you described already,  as you said, if you make your Beam the group coordinator this echo won’t come up. It’s certainly frustrating to hear an echo, so rest assured that we’re on it. We don’t consider making the main speaker the coordinator is a solution, it’s a workaround while we get a fix prepared and launched.

Thanks for the reply and Im glad the issue is being worked on. It would be worth your support team saying the same thing rather than "so hopefully that's your problem sorted". 

However, I didn't discuss any features from the beta testing (this echo can't be from the beta because it's happening on stock software). My mention of the beta was there for background information and where I first saw the issue. 

The team definitely should know about it, so if you worked with someone they should have been able to let you know what was happening and what the workaround is while we get a solution ready. There are a couple threads here on the community on the topic too, I think I’m in all of them already, having talked about it. In any case, hang tight, we’ll let you know when it’s resolved.

Thanks Ryan. The last communication I got from Sonos was:

"This issue should be resolved if you set the Beam up as the Group Coordinator i.e. the speaker you start the group from.

Please test the system for a while in this setup, and if you continue to experience issues, submit another diagnostic for review"

You can understand why I didn't get the impression there was any suggestion of it being a problem or that it was getting worked on. 

Understood completely, I’ll look into that one to make sure the person you spoke with learns to include the full details. Sorry for the trouble!

I am a bit confused.  I have purchased a Sonos Beam and two Ikea bookshelf Symfonisk speakers to add to the Sonos beam I use for television.  I have not taken the speakers our of the box and installed them yet.  I do not want to install them if there is an echo.  Is there another speaker I should be buying if I do not want the echo?

Hey @StephenOffice, if you’re using those two as surrounds for the Beam, you won’t have any echo at all, don’t worry about this thread. The title is a bit alarmist and on the misleading side.

If you’re using those speakers as separate rooms in the Sonos app, and having them grouped with the Beam, just make sure you have the Beam playing music first and group the speakers to it first, and you won’t have this echo either.

This issue (which is currently being fixed) happens only if you have music on and playing to other rooms that are then grouped with the Beam, sometimes they get out of sync.