Skip to content

Feature Request: Improve documentation for working with presets and limitations of Favorites #202

@jzajac2

Description

@jzajac2

I have several questions, hopefully the output of this is I can submit a PR for some doc updates:

  1. the node-sonos-http-api allows for a folder named presets in it (for organization purposes) and it is the preferred way so perhaps we should update accordingly (I believe it even hot loads them / don't have to restart the server when you add new json files to presets folder)
  2. When I have a .json file in presets folder where the "favorite" name contains more than one word for example "All Duran Duran Albums", utterances don't seem to be able to capture that. If I trim it down to one word like "Duran" (then change the name of the corresponding Favorite in sonos controller app to "Duran"), then it works. Now, I prefer Favorites as I had some issues with regular the presets, but if another way supports my desire to have longer/more explicit utterances then I'm open to it. I also see a test:
    console.log('Calling preset by JSON'); return sonosProxy.preset('{"players": [{ "roomName": "Kitchen", "volume": 30}], "state": "PAUSED", "pauseOthers": false}');

That seemed to work!
Now with Favorites, I am limited to the one word utterances, it PLAYS, however I get
ERROR Invalid music service
and Alexa responds

Starting playing artist favorite all duran duran albums

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions