Closed hklages closed 5 months ago
At the moment this library only supports local
control. as in
flowchart LR
A[NodeRED] -->|Invoke| B(node-sonos-ts)
B -->|Soap mostly or HTTP| C{Sonos Speaker}
All the endpoints in the Control API are cloud based like the suspend command.
flowchart LR
A[NodeRED] -->|Invoke| B(node-sonos-ts)
B --> |1. Get token with user interaction| Cloud{Sonos Cloud}
Cloud -->|2. Access token| B
B --> |3. Keep token| B
B --> |4. Control api| Cloud
Cloud -->|Https| Speaker
Issues with control api:
Until now everything was possible by talking directly to the sonos speakers, which is something I really prefer. But I'm open for discussion.
Apart from that, the most recent commit in the beta branch contains code to *locally talk to the control API directly on the speaker. This might be your entry point. See https://github.com/svrooij/node-sonos-ts/commit/2a88a897f6e284ed84b1907468858dff2633d884
Any maybe even this comment
Care to give it a go @nficano
@hklages I'm currently checking this out. And I seem to get some of the details working.
But for the suspend
command, you seem to need the sessionId
and this can only be retrieved whedn creating a sessions (so it seems.
https://docs.sonos.com/reference/playbacksession-suspend-sessionid
I'm closing this issue since, I cannot access the sessionId. If you know a way on how to get this, I'm happy to create this feature.
Yeah. Thanks for your effort. Session id is difficult to handle
Is your feature request related to a problem? Please describe
No.
Describe the solution you'd like
just add "playbackSession.suspend" similiar to play clip.
Describe alternatives you've considered
No idea
Additional context
see