Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonos integration adding both devices in Stereo pairs #82257

Closed
NRForbes opened this issue Nov 17, 2022 · 5 comments
Closed

Sonos integration adding both devices in Stereo pairs #82257

NRForbes opened this issue Nov 17, 2022 · 5 comments

Comments

@NRForbes
Copy link

The problem

In some cases both devices in a stereo pair are created as devices (though one is always unavailable). All devices have fixed IPs, but there are 3 Sonos Households on the network:

Main system: 7 Zones, 3 of which are stereo pairs - only 7 devices are created in Home Assistant (stereo pairs are detected and created correctly most of the time, occasionally the 2nd device appears)

Standalone A system: 1 zone (a stereo pair), both devices are always created in Home Assistant (1 is unavailable)

Standalone B system: 1 zone (a stereo pair), both devices are always created in Home Assistant (1 is unavailable)

What version of Home Assistant Core has the issue?

2022.11.2

What was the last working version of Home Assistant Core?

None (has always been in issue in 2022)

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Sonos

Link to integration documentation on our website

https://www.home-assistant.io/integrations/sonos/

Diagnostics information

sonos-5bcc0e2163235dfae10826df1b087ccd-Lauras Room-a8616adb61d11dc168322838ba4c2e5a.json.txt
sonos-5bcc0e2163235dfae10826df1b087ccd-Lauras Room-1554d5209cc515d9af2ebec3030f5c08.json.txt
home-assistant sonos.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Attached are the diagnostics files for the two devices created (one incorrectly).
Also the discovery log for the Sonos integration.

Additional information

No response

@home-assistant
Copy link

Hey there @cgtobi, @jjlawren, mind taking a look at this issue as it has been labeled with an integration (sonos) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of sonos can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign sonos Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


sonos documentation
sonos source
(message by IssueLinks)

@cmaglio
Copy link

cmaglio commented Nov 23, 2022

I am also seeing this behavior for a stereo pair of Sonos Roams...

Sonos App:
image

Home Assistant:
image

@jezzamine
Copy link

I have the same issue with a stereo pair of Sonos Fives.

I've deleted the Sonos integration, manually removed them from core.device_registry, restarted HA, rebooted system, power cycled the Fives and reinstalled the integration several times with no change.

@csoltenborn
Copy link
Contributor

I had the same issue, i.e., a two paired speakers were shown as such in the Sonos app, but as two different devices in HA. In my case, splitting up the pair of speakers in the Sonos app and then repairing them fixed the issue on the HA side.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale May 2, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jun 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants