Is anyone updating the Sonos plug-in to support their new multi zone amplifier. It uses one IP address and different ports for the zones.

50 minutes ago, Howard said:

Is anyone updating the Sonos plug-in to support their new multi zone amplifier. It uses one IP address and different ports for the zones.

Not at this time.

I attempt to maintain both the Sonos and ST-Sonos plugins but I don't have any Sonos equipment. That makes attempting to support new features difficult.

Both plugins are based on external libraries so if those libraries add support for the this, it may be possible to update the plugins to take advantage of it. I'd really need to know what support for this means. Is this something that would only change the way the plugin internally address zones or is there some external/visible change to the configuration and/or nodes themselves?

Hi Bob. Thanks for the plugin and responding to my post.

My coding is rusty but I can act as a testbed for your plugins. I have an Amp, Amp Multi and Sonos One. There is also an updated plugin on HA which works with Amp Multi.

The library being used for the sonos (udi-sonos-poly) plugin was updated a couple of weeks ago to add support for Amp Multi, but I don't really know what that means.

I can attempt to update the plugin to use the latest version of the library.

That's great. They changed the way they address the speakers so discovery doesn't work. The Amp multi uses one IP address and different ports for the speakers. The attached may be helpful.

ha-to-eisy.zip

Yes, that's very helpful. But it raises some questions on what's the best way forward. I see a couple of options.

1. I can try and update the existing sonos plugin. It seems possible, at least the discovery of zones part looks pretty easy. But the existing sonos plugin also allows for manually specifying the zone in the config parameters. Converting that to work with Amp Multi looks to be more of a challenge. There are also other areas of this plugin that could/should be updated as well.

2. Use the generated plugin from ha-to-eisy.zip to create a new Sonos plugin (possibly replacing both ST-Sonos and Sonos). I do see some issues in the plugin that would need to be corrected and it seems to be based on outdated PG3 plugin designs.

I'm leaning toward option 2, simply because it seems like the work needed is less and it already has the missing features from the Sonos plugin.

Where did ha-to-eisy come from? I can't find anything in the .zip file that lists the license, author, or url to find out more about this. I'd like to make sure that it's ok to modify and re-distribute the code.

I asked Muse to look at HA and create an EISY version of it. I was thinking of my early days programming and thought it could create a wrapper of sorts. This is the result. The good news is below.

Apache License 2.0 — with one layer worth knowing about, since you're building on it:

The Sonos integration doesn't carry a license of its own. It's part of Home Assistant Core, and the Home Assistant project's governance sets Apache 2.0 for all of its code projects, so the integration inherits that. Apache 2.0 is permissive: you can use, modify, and redistribute the code, including commercially, as long as you keep the copyright/license notices and note changes. It also includes an explicit patent grant from contributors.

Underneath it, the library the integration actually talks to the speakers with — SoCo, the same one your Eisy plugin's backend uses — is MIT licensed, which is even lighter: essentially just keep the copyright notice.

So for your porting work, both layers are permissive and compatible: nothing copyleft, nothing that forces you to open-source the PG3 plugin you derived from them, just attribution obligations if you redistribute their code.

A note about my set up; the AMP is configured as the rear speakers for the Arc Ultra.

You can see from the attached that Amp Multi speakers have a Port assigned and the One: Spa does not. The One: Spa is found by the current plugin.