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

Handle multiple zones with same name #96

Closed
ebaauw opened this issue Jul 31, 2019 · 1 comment
Closed

Handle multiple zones with same name #96

ebaauw opened this issue Jul 31, 2019 · 1 comment

Comments

@ebaauw
Copy link
Owner

ebaauw commented Jul 31, 2019

See #94, Sonos allows multiple zones with the same name. homebridge-zp, and zp, should administer zones under the id of the master zone player, instead of under the zone name.

ebaauw added a commit that referenced this issue Aug 1, 2019
Register zones under id of the master zone player instead of under zone name.  See #96.
ebaauw added a commit that referenced this issue Aug 1, 2019
Register zones under id of the master zone player instead of under zone name.  See #96.

Adjusted `zp info` and `zp topology`.
ebaauw added a commit that referenced this issue Aug 4, 2019
Bug fix:
- Logic around `SonosCoordinator`, see #94.
- Handle multiple zones with same name, see #96.
- Only subscribe to `ZoneGroupTopology` evenst of "associated" zone player, cf. Sonos app.
ebaauw added a commit that referenced this issue Aug 4, 2019
Bug fix:
- Logic around `SonosCoordinator`, see #94.
- Handle multiple zones with same name, see #96.
@ebaauw
Copy link
Owner Author

ebaauw commented Aug 4, 2019

In v1.0.8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant