GetZoneGroupTopology fails with http status 500.

[ebaauw]

From Discord: zone player responds with status 500 on POST to /ZoneGroupTopology/Control for GetZoneGroupTopology:

2020-04-12T19:15:20.993Z ZpClient:request:1 post("ZonePlayer", "ZoneGroupTopology", "GetZoneGroupState", {})
2020-04-12T19:15:20.993Z HttpClient1 request(POST, /ZoneGroupTopology/Control, "<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"><s:Body><u:GetZoneGroupState xmlns:u=\"urn:schemas-upnp-org:service:ZoneGroupTopology:1\"></u:GetZoneGroupState></s:Body></s:Envelope>", {"SOAPaction":"\"urn:schemas-upnp-org:service:ZoneGroupTopology:1#GetZoneGroupState\"","content-type":"text/xml; charset=utf-8"})
zp: error: POST /ZoneGroupTopology/Control: http status 500 Internal Server Error

It's a network of 30 zone players - might be stretching it (household can hold a max of 32 zone players). The Sonos app doesn't make this call, but subscribes to ZoneGroupTopology events of the associated zone player.

Unfortunately, ZpClient makes this call when connecting to the zone player, so need to find a way around it. The ZoneGroupTopology events look good, though, see attached output of zp eventlog: zpeventlog.zip

[ebaauw]

In beta v1.4.0-1, zp topology -v uses the topology from the connected zone player to augment the device description of the other zone players. Still need to apply that logic to Homebridge ZP.

Also, the household ID is only reported in the ZoneGroupTopoloy event, but not in the GetZoneGroupTopology response.

[ebaauw]

As of beta v1.4.0-4, Homebridge ZP no longer tries the GetZoneGroupTopology and uses events straight away.

[ebaauw]

In v1.4.0.