node-red-contrib-sonos-plus

node-red-contrib-sonos-plus copied to clipboard

Description

node player.become.standalone stops musing on provided player and actually all players currently in the same group

What node/command (topic)/state (payload)

node: universal node command: player.become.standalone state: ok

In case of a bug: Are you able to reproduce the error

yes

Versions and Infrastructure

what system: promox node-red-contrib-sonos-plus version: 6.9.0 Node-RED version: 4.0.2 NodeJS version:

see: [https://flows.nodered.org/flow/a5c42641bf33dd0da9bfd4426a06950a]

Hi. At my test system: SonosKueche (is coordinator) SonosBad SonosWohnzimmer it behave as follows:

Applying the "become.standalone" to the any non-coordinator such as SonosBad the rest of the group continuous playing and SonosBad stops playing (because it is not anymore in the group).

Applying the "become.standalone" to the the coordinator SonosKueche another player becomes the coordinator and the new group continuous playing. The ex-coordinator stops playing (because it is not anymore in the group).

Please verify that the remaining group does not continou to play. What would you like to achieve?

@hklages thanks for taking your time to respond.

here is my scenario:

I am in bedroom, I ask alexa to play music or radio.

I go to other room, sonos joins in as per node red automation.

I live that room, become.standalone kicks in that room for that speaker - all stops playing.

is there anything I can do to provide more details/logs?

thanks!

Ok maybe player leave group does the job.

https://github.com/hklages/node-red-contrib-sonos-plus/wiki/A.1-Universal-Node#playerleavegroup

or household.create.group where you define the new group without that player.+

I am out of my home and can not test it.