sonos.getTopology() does not work after upgrading to Sonos version 9.1

[magnlund]

After upgrading to Sonos Version 9.1 sonos.getTopolgy() does not work anylonger and therefore sonos.JoinGroup() fails

Expected Behavior

http://IP_ADRESS:1400/status/topology seems to be empty and therefore sonos.getTopology() fails with error message "Cannot read property 'ZonePlayer' of undefined"

Possible Solution

I would really like an update on this cause grouping management is essential in my HA setup. Thanks in advance

Versions (and Environment)

Node version: 8.9.3
node-sonos version: 1.4.1
OS:

[ebaauw]

This got me scared, but it looks like homebridge-zp is still working. Please be aware that upgrading the ZonePlayer causes it to reboot, losing all subscriptions. There's no notification (that I've seen, or handle) to clients with an open subscription, so effectively clients are no longer receiving events until they renew the subscription or are restarted.

[magnlund]

Thanks for your quick respons. If I got you correct I need to restart the CLIENT. I tried to factory reset all my players but that did not help. Please confirm. Sent from ProtonMail Mobile

…

On Wed, Sep 5, 2018 at 22:28, Erik Baauw ***@***.***> wrote: This got me scared, but it looks like homebridge-zp is still working. Please be aware that upgrading the ZonePlayer causes it to reboot, losing all subscriptions. There's no notification (that I've seen, or handle) to clients with an open subscription, so effectively clients are no longer receiving events until they renew the subscription or are restarted. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#332 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhG13S13LtrsD5-7Ae_FFtNwAZgUAVXaks5uYDPggaJpZM4Wbgxm).

[ebaauw]

That’s what I needed to do.

[magnlund]

This Seems to be tricky. I have done factory reset on all my 3 players and restarted my Rpi. Still the same issue. More tip are highly appreciated cause I really rely on your script in my HA setup. I have 2 connect amps and one Sonos One Sent from ProtonMail mobile

…

-------- Original Message --------

On 6 sep. 2018 07:19, Erik Baauw wrote: That’s what I needed to do. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#332 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhG13ZvvkantPoCqbufAsrNVKycHMzpqks5uYLBqgaJpZM4Wbgxm).

[magnlund]

Please find this thread. It comes from node-sonos. The next came from you as well but from zonebridge Sent from ProtonMail mobile

…

-------- Original Message --------

On 5 sep. 2018 22:28, Erik Baauw wrote: This got me scared, but it looks like homebridge-zp is still working. Please be aware that upgrading the ZonePlayer causes it to reboot, losing all subscriptions. There's no notification (that I've seen, or handle) to clients with an open subscription, so effectively clients are no longer receiving events until they renew the subscription or are restarted. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#332 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhG13S13LtrsD5-7Ae_FFtNwAZgUAVXaks5uYDPggaJpZM4Wbgxm).

[ebaauw]

http://IP_ADRESS:1400/status/topology

These are undocumented debug pages, and have been known to change unannounced. Best not base node-sonos (or any client) on this. Use the zoneGroupTopology service instead.

[magnlund]

Makes sense but this is the adress which is being used by getTopology() in sonos.js. I would be extremely happy if a new updated version of sonos.js could be released because joinGroup() does NOT work with sonos 9.1 Sent from ProtonMail Mobile

…

On Thu, Sep 6, 2018 at 22:13, Erik Baauw ***@***.***> wrote: > http://IP_ADRESS:1400/status/topology These are undocumented debug pages, and have been known to change unannounced. Best not base node-sonos (or any client) on this. Use the zoneGroupTopology service instead. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#332 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhG13ZE1EEOACS4wqzhsK9mW6XsrcnShks5uYYHrgaJpZM4Wbgxm).

[bencevans]

🎉 This issue has been resolved in version 1.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[magnlund]

Just installed 1.5.0. Works like a charm. Thank you SO MUCH for this quick response

[jcleek]

Can you tell me how exactly you installed the new version and got it to work? I have tried both packages listed by bencevans and neither cause it to work. Homebridge crashes on SONOS.

[magnlund]

Just to clarify. This is about node-sonos 1.5.0; not homebridge. After release of 1.5.0 yesterday evening i simply did this: -Changed my package.json file to 1.5.0 - Installed 1.5.0 via npm install Sent from ProtonMail Mobile

…

On Mon, Sep 10, 2018 at 23:57, jcleek ***@***.***> wrote: Can you tell me how exactly you installed the new version and got it to work? I have tried both packages listed by bencevans and neither cause it to work. Homebridge crashes on SONOS. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#332 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AhG13RZbUKgT4SoUzYGCYEQzNCJsSuvkks5uZuA8gaJpZM4Wbgxm).

[jcleek]

ah, ok. Thank you sir. Hopefully someone smarter than me can get this working with homebridge.