search

hklages / node-red-contrib-sonos-plus

A set of Node-RED nodes to control SONOS player in your local network.
MIT License
76 stars 14 forks source link

Improvement request: get.state for Player & Houshold #202

Closed xX-Nexus-Xx closed 5 months ago

xX-Nexus-Xx commented 2 years ago

Hi there,

I'm using your node for a while with great sucess, all works seamlessly .. thx a lot

You currently have a node Group.get.state ... is it possible to have the same for Player & Houshold ??

e.g. Player.get.state ... Household.get.state

this would simplify the collection of state information dramatically , avoiding several get calls

thanks for considering

goog wook .. keep going

hklages commented 2 years ago

Hi. Can you explain your use case? A lot is already now possible with group.create.snap and the standard Node-RED tools.

There is no single SONOS command to get the state. group.get.state sends 6 requests to the SONOS-Player, extracts the relevant information and output them. Most other group.* commands take 2 requests.

For a better understanding:

player.get.state: All data are group related (playbackstate, group volume, group mutestated, ....) so a player.get.state for any player in a group would provide the same data as the the group.get.state. If you are interested in the player volume and player mute state you can already now get these data for all player in a group with group.create.snap

householde.get.state: I could implement it by sending group.get.state to all group coordinator. It will take some time as everything is serial and each command needs 6 request. With nodeRED split/join it is parallel, therefore much faster and already now available. See this example: example 9

hklages commented 5 months ago

no response -> closed