Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Spotify: Song aus Playliste entfernen! http comand

NEWS

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    467

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    10
    1
    385

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    976

Spotify: Song aus Playliste entfernen! http comand

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
spotifyvoice commandsonosplaylist
9 Beiträge 2 Kommentatoren 642 Aufrufe 2 Beobachtet
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • R Offline
    R Offline
    rehmosch
    schrieb am zuletzt editiert von rehmosch
    #1

    Servus,

    gibts denn irgendwie eine Lösung wie man per Sprachbefehl ein Lied aus der Playliste löschen kann?

    Anscheinend ist es möglich per http comand einen Song aus der Playliste zu löschen. Hier wäre es doch mit dem "Spotify Premium Adapter" die Playlist- & Song- ID URIs aus dem Adapter auszulesen und mit 2 Variablen einen http request comand abzusetzen, um einen Song aus der Playliste zu löschen, oder nicht?

    Lohnt es sich hier Zeit zu investieren?

    Bei Spotify hab ich das gefunden:
    https://developer.spotify.com/documentation/web-api/reference/playlists/remove-tracks-playlist/
    https://developer.spotify.com/community/news/2018/06/12/changes-to-playlist-uris/

     Remove Tracks from a Playlist
    
    Remove one or more tracks from a user’s playlist.
    Endpoint
    
    DELETE https://api.spotify.com/v1/playlists/{playlist_id}/tracks
    
    Request Parameters Path Parameters Path Parameter 	Value
    playlist_id 	The Spotify ID for the playlist.
    Header Fields Header Field 	Value
    Authorization 	Required. A valid access token from the Spotify Accounts service: see the Web API Authorization Guide for details. The access token must have been issued on behalf of the user. Removing tracks from a user’s public playlist requires authorization of the playlist-modify-public scope; removing tracks from a private playlist requires the playlist-modify-private scope. See Using Scopes.
    Content-Type 	Required. The content type of the request body: application/json
    
    There are several ways to specify which tracks to remove, determined by the request parameters. Removing all occurrences of specific tracks
    
    You can remove all occurrences of a track (or multiple tracks) by specifying only the track URI(s): Request data 	Value type 	Value
    tracks 	array of objects containing Spotify URI strings 	Required. An array of objects containing Spotify URIs of the tracks to remove. For example: { "tracks": [{ "uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh" },{ "uri": "spotify:track:1301WleyT98MSxVHPZCA6M" }] }. A maximum of 100 objects can be sent at once.
    Removing a specific occurrence of a track
    
    You can remove a track from a certain position by specifying both the track URI and the track position in the playlist. If you specify incorrect information (for example, if the given track does not exist at the given position) an error will be returned and the entire request will fail. If you specify multiple deletions and one is malformed, the entire request will be failed and no edits will take place. Request data 	Value type 	Value
    tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
    { "tracks": [{ "uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [0,3] },{ "uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
    The positions parameter is zero-indexed, that is the first track in the playlist has the value 0 , the second track 1 , and so on.
    A maximum of 100 objects can be sent at once.
    Removing a specific occurrence of a track in a specific playlist snapshot
    
    To guard against errors when concurrent edits happen to the same playlist, we recommend specifying a snapshot_id parameter. The snapshot_id lets us know which version of the playlist you are trying to edit. Concurrent edits by another user will be automatically resolved. If a given track in a given position is not found in the specified snapshot, the entire request will fail and no edits will take place.
    
    Although this mechanism should help avoid errors from conflicting edits, you should always endeavor to use the most recent snapshot_id available. Request data 	Value type 	Value
    tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
    { "tracks":[{"uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [2] },{"uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
    The positions parameter is zero-indexed, that is the first track in the playlist has the value 0 , the second track 1 , and so on.
    A maximum of 100 objects can be sent at once.
    snapshot_id 	string 	Optional. The playlist’s snapshot ID against which you want to make the changes. The API will validate that the specified tracks exist and in the specified positions and make the changes, even if more recent changes have been made to the playlist.
    Removing the track at a given position in a specific playlist snapshot
    
    Instead of specifying the tracks’ URIs, this endpoint also accepts which positions to remove. To guard against errors during concurrent editing, this requires you to specify snapshot_id parameter. Request data 	Value type 	Value
    tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
    
    { "tracks":[{"uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [2] },{
    "uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
    
    The positions parameter is zero-indexed, that is the first track in the playlist has the value 0, the second track 1, and so on.
    
    A maximum of 100 objects can be sent at once.
    snapshot_id 	string 	Optional. The playlist’s snapshot ID against which you want to make the changes. The API will validate that the specified tracks exist and in the specified positions and make the changes, even if more recent changes have been made to the playlist.
    Response Format
    
    On success, the response body contains a snapshot_id in JSON format and the HTTP status code in the response header is 200 OK. The snapshot_id can be used to identify your playlist version in future requests.
    
    On error, the header status code is an error code and the response body contains an error object. Trying to remove a track when you do not have the user’s authorization returns error 403 Forbidden. Attempting to use several different ways to remove tracks returns 400 Bad Request. Other client errors returning 400 Bad Request include specifying invalid positions. Example
    
    Note that cURL requires quotation marks within the JSON data to be escaped, for example. \"spotify:track:1301WleyT98MSxVHPZCA6M\".
    
    curl -X DELETE -i -H "Authorization: Bearer {your access token}" -H "Content-Type: application/json" "https://api.spotify.com/v1/playlists/71m0QB5fUFrnqfnxVerUup/tracks" --data "{\"tracks\":[{\"uri\": \"spotify:track:4iV5W9uYEdYUVa79Axb7Rh\", \"positions\": [2] },{\"uri\":\"spotify:track:1301WleyT98MSxVHPZCA6M\", \"positions\": [7] }] }"
    
    HTTP/1.1 200 OK
    { "snapshot_id" : "JbtmHBDBAYu3/bt8BOXKjzKx3i0b6LCa/wVjyl6qQ2Yf6nFXkbmzuEa+ZI/U1yF+" }
    
    Frequently Asked Questions
    
        Is it possible to delete a playlist? No, it isn’t. The reason there is no endpoint for this is explained in our Working With Playlists Guide in the section Following and Unfollowing a Playlist.
        Can I use X-HTTP-Method-Override or similar to send a DELETE request overriding the HTTP verb? Not at the moment, the delete operation needs to be specified through a DELETE request.
    
    NOTE: looking for DELETE https://api.spotify.com/v1/users/{user_id}/playlists/{playlist_id}/tracks? Read the blog post.
    

    Würde sogar den Musik-Dienst wechseln, jedoch funktioniert (hab noch nix gefunden) es bei keinem meiner Anbieter (Spotify, Google Music, Youtube Music, Amazon Music).

    Google verschlüsselt und hat leider keine Api, so dass es hier keine Lösungweg gibt.

    Alexa, kann zwar bei Amazon-Music Songs hinzufügen, jedoch keine löschen ;(

    Würde mich sehr freuen, wenn jemand einen Tip hätte

    Danke

    Jutta

    RP4/Conbee II/Pihilips Hue/HarmonyHub/Sonos/Alexa/Aqara Sensoren/Tradfri/ZigbeeThermostate/Xiaomi Saugroboter/Smarte Türklingel & Briefkasten ...

    R J.A.R.V.I.S.J 2 Antworten Letzte Antwort
    0
    • R rehmosch

      Servus,

      gibts denn irgendwie eine Lösung wie man per Sprachbefehl ein Lied aus der Playliste löschen kann?

      Anscheinend ist es möglich per http comand einen Song aus der Playliste zu löschen. Hier wäre es doch mit dem "Spotify Premium Adapter" die Playlist- & Song- ID URIs aus dem Adapter auszulesen und mit 2 Variablen einen http request comand abzusetzen, um einen Song aus der Playliste zu löschen, oder nicht?

      Lohnt es sich hier Zeit zu investieren?

      Bei Spotify hab ich das gefunden:
      https://developer.spotify.com/documentation/web-api/reference/playlists/remove-tracks-playlist/
      https://developer.spotify.com/community/news/2018/06/12/changes-to-playlist-uris/

       Remove Tracks from a Playlist
      
      Remove one or more tracks from a user’s playlist.
      Endpoint
      
      DELETE https://api.spotify.com/v1/playlists/{playlist_id}/tracks
      
      Request Parameters Path Parameters Path Parameter 	Value
      playlist_id 	The Spotify ID for the playlist.
      Header Fields Header Field 	Value
      Authorization 	Required. A valid access token from the Spotify Accounts service: see the Web API Authorization Guide for details. The access token must have been issued on behalf of the user. Removing tracks from a user’s public playlist requires authorization of the playlist-modify-public scope; removing tracks from a private playlist requires the playlist-modify-private scope. See Using Scopes.
      Content-Type 	Required. The content type of the request body: application/json
      
      There are several ways to specify which tracks to remove, determined by the request parameters. Removing all occurrences of specific tracks
      
      You can remove all occurrences of a track (or multiple tracks) by specifying only the track URI(s): Request data 	Value type 	Value
      tracks 	array of objects containing Spotify URI strings 	Required. An array of objects containing Spotify URIs of the tracks to remove. For example: { "tracks": [{ "uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh" },{ "uri": "spotify:track:1301WleyT98MSxVHPZCA6M" }] }. A maximum of 100 objects can be sent at once.
      Removing a specific occurrence of a track
      
      You can remove a track from a certain position by specifying both the track URI and the track position in the playlist. If you specify incorrect information (for example, if the given track does not exist at the given position) an error will be returned and the entire request will fail. If you specify multiple deletions and one is malformed, the entire request will be failed and no edits will take place. Request data 	Value type 	Value
      tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
      { "tracks": [{ "uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [0,3] },{ "uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
      The positions parameter is zero-indexed, that is the first track in the playlist has the value 0 , the second track 1 , and so on.
      A maximum of 100 objects can be sent at once.
      Removing a specific occurrence of a track in a specific playlist snapshot
      
      To guard against errors when concurrent edits happen to the same playlist, we recommend specifying a snapshot_id parameter. The snapshot_id lets us know which version of the playlist you are trying to edit. Concurrent edits by another user will be automatically resolved. If a given track in a given position is not found in the specified snapshot, the entire request will fail and no edits will take place.
      
      Although this mechanism should help avoid errors from conflicting edits, you should always endeavor to use the most recent snapshot_id available. Request data 	Value type 	Value
      tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
      { "tracks":[{"uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [2] },{"uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
      The positions parameter is zero-indexed, that is the first track in the playlist has the value 0 , the second track 1 , and so on.
      A maximum of 100 objects can be sent at once.
      snapshot_id 	string 	Optional. The playlist’s snapshot ID against which you want to make the changes. The API will validate that the specified tracks exist and in the specified positions and make the changes, even if more recent changes have been made to the playlist.
      Removing the track at a given position in a specific playlist snapshot
      
      Instead of specifying the tracks’ URIs, this endpoint also accepts which positions to remove. To guard against errors during concurrent editing, this requires you to specify snapshot_id parameter. Request data 	Value type 	Value
      tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
      
      { "tracks":[{"uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [2] },{
      "uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
      
      The positions parameter is zero-indexed, that is the first track in the playlist has the value 0, the second track 1, and so on.
      
      A maximum of 100 objects can be sent at once.
      snapshot_id 	string 	Optional. The playlist’s snapshot ID against which you want to make the changes. The API will validate that the specified tracks exist and in the specified positions and make the changes, even if more recent changes have been made to the playlist.
      Response Format
      
      On success, the response body contains a snapshot_id in JSON format and the HTTP status code in the response header is 200 OK. The snapshot_id can be used to identify your playlist version in future requests.
      
      On error, the header status code is an error code and the response body contains an error object. Trying to remove a track when you do not have the user’s authorization returns error 403 Forbidden. Attempting to use several different ways to remove tracks returns 400 Bad Request. Other client errors returning 400 Bad Request include specifying invalid positions. Example
      
      Note that cURL requires quotation marks within the JSON data to be escaped, for example. \"spotify:track:1301WleyT98MSxVHPZCA6M\".
      
      curl -X DELETE -i -H "Authorization: Bearer {your access token}" -H "Content-Type: application/json" "https://api.spotify.com/v1/playlists/71m0QB5fUFrnqfnxVerUup/tracks" --data "{\"tracks\":[{\"uri\": \"spotify:track:4iV5W9uYEdYUVa79Axb7Rh\", \"positions\": [2] },{\"uri\":\"spotify:track:1301WleyT98MSxVHPZCA6M\", \"positions\": [7] }] }"
      
      HTTP/1.1 200 OK
      { "snapshot_id" : "JbtmHBDBAYu3/bt8BOXKjzKx3i0b6LCa/wVjyl6qQ2Yf6nFXkbmzuEa+ZI/U1yF+" }
      
      Frequently Asked Questions
      
          Is it possible to delete a playlist? No, it isn’t. The reason there is no endpoint for this is explained in our Working With Playlists Guide in the section Following and Unfollowing a Playlist.
          Can I use X-HTTP-Method-Override or similar to send a DELETE request overriding the HTTP verb? Not at the moment, the delete operation needs to be specified through a DELETE request.
      
      NOTE: looking for DELETE https://api.spotify.com/v1/users/{user_id}/playlists/{playlist_id}/tracks? Read the blog post.
      

      Würde sogar den Musik-Dienst wechseln, jedoch funktioniert (hab noch nix gefunden) es bei keinem meiner Anbieter (Spotify, Google Music, Youtube Music, Amazon Music).

      Google verschlüsselt und hat leider keine Api, so dass es hier keine Lösungweg gibt.

      Alexa, kann zwar bei Amazon-Music Songs hinzufügen, jedoch keine löschen ;(

      Würde mich sehr freuen, wenn jemand einen Tip hätte

      Danke

      Jutta

      R Offline
      R Offline
      rehmosch
      schrieb am zuletzt editiert von
      #2

      @rehmosch Hab jetzt mal auch auf github gepostet und hier mal einen Link:
      https://github.com/twonky4/ioBroker.spotify-premium/issues/75

      RP4/Conbee II/Pihilips Hue/HarmonyHub/Sonos/Alexa/Aqara Sensoren/Tradfri/ZigbeeThermostate/Xiaomi Saugroboter/Smarte Türklingel & Briefkasten ...

      1 Antwort Letzte Antwort
      0
      • R Offline
        R Offline
        rehmosch
        schrieb am zuletzt editiert von
        #3

        kann doch nicht sein, dass hier keiner seine Playliste pflegen möchte!?! Wie macht ihr das sonst?

        RP4/Conbee II/Pihilips Hue/HarmonyHub/Sonos/Alexa/Aqara Sensoren/Tradfri/ZigbeeThermostate/Xiaomi Saugroboter/Smarte Türklingel & Briefkasten ...

        1 Antwort Letzte Antwort
        0
        • R rehmosch

          Servus,

          gibts denn irgendwie eine Lösung wie man per Sprachbefehl ein Lied aus der Playliste löschen kann?

          Anscheinend ist es möglich per http comand einen Song aus der Playliste zu löschen. Hier wäre es doch mit dem "Spotify Premium Adapter" die Playlist- & Song- ID URIs aus dem Adapter auszulesen und mit 2 Variablen einen http request comand abzusetzen, um einen Song aus der Playliste zu löschen, oder nicht?

          Lohnt es sich hier Zeit zu investieren?

          Bei Spotify hab ich das gefunden:
          https://developer.spotify.com/documentation/web-api/reference/playlists/remove-tracks-playlist/
          https://developer.spotify.com/community/news/2018/06/12/changes-to-playlist-uris/

           Remove Tracks from a Playlist
          
          Remove one or more tracks from a user’s playlist.
          Endpoint
          
          DELETE https://api.spotify.com/v1/playlists/{playlist_id}/tracks
          
          Request Parameters Path Parameters Path Parameter 	Value
          playlist_id 	The Spotify ID for the playlist.
          Header Fields Header Field 	Value
          Authorization 	Required. A valid access token from the Spotify Accounts service: see the Web API Authorization Guide for details. The access token must have been issued on behalf of the user. Removing tracks from a user’s public playlist requires authorization of the playlist-modify-public scope; removing tracks from a private playlist requires the playlist-modify-private scope. See Using Scopes.
          Content-Type 	Required. The content type of the request body: application/json
          
          There are several ways to specify which tracks to remove, determined by the request parameters. Removing all occurrences of specific tracks
          
          You can remove all occurrences of a track (or multiple tracks) by specifying only the track URI(s): Request data 	Value type 	Value
          tracks 	array of objects containing Spotify URI strings 	Required. An array of objects containing Spotify URIs of the tracks to remove. For example: { "tracks": [{ "uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh" },{ "uri": "spotify:track:1301WleyT98MSxVHPZCA6M" }] }. A maximum of 100 objects can be sent at once.
          Removing a specific occurrence of a track
          
          You can remove a track from a certain position by specifying both the track URI and the track position in the playlist. If you specify incorrect information (for example, if the given track does not exist at the given position) an error will be returned and the entire request will fail. If you specify multiple deletions and one is malformed, the entire request will be failed and no edits will take place. Request data 	Value type 	Value
          tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
          { "tracks": [{ "uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [0,3] },{ "uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
          The positions parameter is zero-indexed, that is the first track in the playlist has the value 0 , the second track 1 , and so on.
          A maximum of 100 objects can be sent at once.
          Removing a specific occurrence of a track in a specific playlist snapshot
          
          To guard against errors when concurrent edits happen to the same playlist, we recommend specifying a snapshot_id parameter. The snapshot_id lets us know which version of the playlist you are trying to edit. Concurrent edits by another user will be automatically resolved. If a given track in a given position is not found in the specified snapshot, the entire request will fail and no edits will take place.
          
          Although this mechanism should help avoid errors from conflicting edits, you should always endeavor to use the most recent snapshot_id available. Request data 	Value type 	Value
          tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
          { "tracks":[{"uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [2] },{"uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
          The positions parameter is zero-indexed, that is the first track in the playlist has the value 0 , the second track 1 , and so on.
          A maximum of 100 objects can be sent at once.
          snapshot_id 	string 	Optional. The playlist’s snapshot ID against which you want to make the changes. The API will validate that the specified tracks exist and in the specified positions and make the changes, even if more recent changes have been made to the playlist.
          Removing the track at a given position in a specific playlist snapshot
          
          Instead of specifying the tracks’ URIs, this endpoint also accepts which positions to remove. To guard against errors during concurrent editing, this requires you to specify snapshot_id parameter. Request data 	Value type 	Value
          tracks 	array of objects containing Spotify URI strings and their position in the playlist 	Required. An array of objects containing Spotify URIs of the tracks to remove with their current positions in the playlist. For example:
          
          { "tracks":[{"uri": "spotify:track:4iV5W9uYEdYUVa79Axb7Rh", "positions": [2] },{
          "uri": "spotify:track:1301WleyT98MSxVHPZCA6M", "positions": [7] }] }
          
          The positions parameter is zero-indexed, that is the first track in the playlist has the value 0, the second track 1, and so on.
          
          A maximum of 100 objects can be sent at once.
          snapshot_id 	string 	Optional. The playlist’s snapshot ID against which you want to make the changes. The API will validate that the specified tracks exist and in the specified positions and make the changes, even if more recent changes have been made to the playlist.
          Response Format
          
          On success, the response body contains a snapshot_id in JSON format and the HTTP status code in the response header is 200 OK. The snapshot_id can be used to identify your playlist version in future requests.
          
          On error, the header status code is an error code and the response body contains an error object. Trying to remove a track when you do not have the user’s authorization returns error 403 Forbidden. Attempting to use several different ways to remove tracks returns 400 Bad Request. Other client errors returning 400 Bad Request include specifying invalid positions. Example
          
          Note that cURL requires quotation marks within the JSON data to be escaped, for example. \"spotify:track:1301WleyT98MSxVHPZCA6M\".
          
          curl -X DELETE -i -H "Authorization: Bearer {your access token}" -H "Content-Type: application/json" "https://api.spotify.com/v1/playlists/71m0QB5fUFrnqfnxVerUup/tracks" --data "{\"tracks\":[{\"uri\": \"spotify:track:4iV5W9uYEdYUVa79Axb7Rh\", \"positions\": [2] },{\"uri\":\"spotify:track:1301WleyT98MSxVHPZCA6M\", \"positions\": [7] }] }"
          
          HTTP/1.1 200 OK
          { "snapshot_id" : "JbtmHBDBAYu3/bt8BOXKjzKx3i0b6LCa/wVjyl6qQ2Yf6nFXkbmzuEa+ZI/U1yF+" }
          
          Frequently Asked Questions
          
              Is it possible to delete a playlist? No, it isn’t. The reason there is no endpoint for this is explained in our Working With Playlists Guide in the section Following and Unfollowing a Playlist.
              Can I use X-HTTP-Method-Override or similar to send a DELETE request overriding the HTTP verb? Not at the moment, the delete operation needs to be specified through a DELETE request.
          
          NOTE: looking for DELETE https://api.spotify.com/v1/users/{user_id}/playlists/{playlist_id}/tracks? Read the blog post.
          

          Würde sogar den Musik-Dienst wechseln, jedoch funktioniert (hab noch nix gefunden) es bei keinem meiner Anbieter (Spotify, Google Music, Youtube Music, Amazon Music).

          Google verschlüsselt und hat leider keine Api, so dass es hier keine Lösungweg gibt.

          Alexa, kann zwar bei Amazon-Music Songs hinzufügen, jedoch keine löschen ;(

          Würde mich sehr freuen, wenn jemand einen Tip hätte

          Danke

          Jutta

          J.A.R.V.I.S.J Offline
          J.A.R.V.I.S.J Offline
          J.A.R.V.I.S.
          Developer
          schrieb am zuletzt editiert von
          #4

          @rehmosch es gibt eine API für Google, die du verwenden könntest.

          R 1 Antwort Letzte Antwort
          0
          • J.A.R.V.I.S.J J.A.R.V.I.S.

            @rehmosch es gibt eine API für Google, die du verwenden könntest.

            R Offline
            R Offline
            rehmosch
            schrieb am zuletzt editiert von
            #5

            @J-A-R-V-I-S hey, leider gibt es keine offizielle Api mehr von Google ;(

            Hier die Antwort vom Dev der Sonos Api node:
            https://gitter.im/node-sonos-http-api/Lobby
            @MAXVORSTADT23_twitter the thumbs up/down are not part of the Sonos SOAP api but rather an implementation directly from the controller, and requires direct implementation of the underlying music service API (which may, or may not, exist, publically). That is why the thumbs up/down doesn't work. Google Music is especially hard since they don't have an offical API

            RP4/Conbee II/Pihilips Hue/HarmonyHub/Sonos/Alexa/Aqara Sensoren/Tradfri/ZigbeeThermostate/Xiaomi Saugroboter/Smarte Türklingel & Briefkasten ...

            J.A.R.V.I.S.J 1 Antwort Letzte Antwort
            0
            • R rehmosch

              @J-A-R-V-I-S hey, leider gibt es keine offizielle Api mehr von Google ;(

              Hier die Antwort vom Dev der Sonos Api node:
              https://gitter.im/node-sonos-http-api/Lobby
              @MAXVORSTADT23_twitter the thumbs up/down are not part of the Sonos SOAP api but rather an implementation directly from the controller, and requires direct implementation of the underlying music service API (which may, or may not, exist, publically). That is why the thumbs up/down doesn't work. Google Music is especially hard since they don't have an offical API

              J.A.R.V.I.S.J Offline
              J.A.R.V.I.S.J Offline
              J.A.R.V.I.S.
              Developer
              schrieb am zuletzt editiert von
              #6

              @rehmosch https://developers.google.com/youtube/

              R 1 Antwort Letzte Antwort
              0
              • J.A.R.V.I.S.J J.A.R.V.I.S.

                @rehmosch https://developers.google.com/youtube/

                R Offline
                R Offline
                rehmosch
                schrieb am zuletzt editiert von
                #7

                @J-A-R-V-I-S Lieben Dank ;) Hättest du denn einen Link, wie man den Dislike bzw. Like-Button (thumb down bzw. up) einbauen könnte? Ich finde da nämlich gar nichts, da google die uri verschlüsselt ... Am liebsten für Google Music da ich Youtube Music gar nicht mag.

                Danke ;) 🙏

                RP4/Conbee II/Pihilips Hue/HarmonyHub/Sonos/Alexa/Aqara Sensoren/Tradfri/ZigbeeThermostate/Xiaomi Saugroboter/Smarte Türklingel & Briefkasten ...

                J.A.R.V.I.S.J 1 Antwort Letzte Antwort
                0
                • R rehmosch

                  @J-A-R-V-I-S Lieben Dank ;) Hättest du denn einen Link, wie man den Dislike bzw. Like-Button (thumb down bzw. up) einbauen könnte? Ich finde da nämlich gar nichts, da google die uri verschlüsselt ... Am liebsten für Google Music da ich Youtube Music gar nicht mag.

                  Danke ;) 🙏

                  J.A.R.V.I.S.J Offline
                  J.A.R.V.I.S.J Offline
                  J.A.R.V.I.S.
                  Developer
                  schrieb am zuletzt editiert von
                  #8

                  @rehmosch das musst du mir ein bisschen mehr erläutern. Möchtest du die abgespielt Titel direkt bewerten, oder wie muss ich das verstehen?

                  R 1 Antwort Letzte Antwort
                  0
                  • J.A.R.V.I.S.J J.A.R.V.I.S.

                    @rehmosch das musst du mir ein bisschen mehr erläutern. Möchtest du die abgespielt Titel direkt bewerten, oder wie muss ich das verstehen?

                    R Offline
                    R Offline
                    rehmosch
                    schrieb am zuletzt editiert von
                    #9

                    @J-A-R-V-I-S IVielen Dank für deine Antwort und Hilfsbereitschaft. Ich erläutere es dir sehr gerne: Ich höre eigentlich fast immer Music über Sonos mit Google Music oder Spotify. Ich liebe Google Music da es immer eine Bewertungsmöglichkeit für Daumen hoch bzw. Daumen runter gibt. Leider macht mich Spotify fast wahnsinnig da es eigentlich nie Daumen runter Optionen gibt, und es wirklich kompliziert ist einzelne Lieder aus der Playliste zu löschen. Da man bei Spotify nicht direkt das gespielte Lied löschen kann, hier muss man dann immer erst die Playliste raussuchen & dann öffnen, dann erst in der langen Liste in der Playliste nach dem jetzt gespielten Lied (dieses ist grün markiert) suchen, dann markieren und auf die 3 Punkte klicken und dann kann man es erst löschen ;(

                    Ich möchte eigentlich nur an die Bewertungen von Google Music rankommen von jetzt gespielte Songs ODER in Spotify das jetzt gespielte Lied aus der Playliste löschen.

                    Jedoch gibt es leider keine API von SONOS für die Daumen hoch oder runter. Jetzt kommen die Musik-Anbieter ins Spiel, hier gibt es eigentlich auch keine API für Bewertungen jedoch habe ich hier was auf github (Entwickler für den Spotify Adapter) gepostet und mir wurde auch schon vom Entwickler geantwortet:

                    https://github.com/twonky4/ioBroker.spotify-premium/issues/75

                    Jedoch bekomme ich es nicht hin ;()

                    RP4/Conbee II/Pihilips Hue/HarmonyHub/Sonos/Alexa/Aqara Sensoren/Tradfri/ZigbeeThermostate/Xiaomi Saugroboter/Smarte Türklingel & Briefkasten ...

                    1 Antwort Letzte Antwort
                    0

                    Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                    Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                    Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                    Registrieren Anmelden
                    Antworten
                    • In einem neuen Thema antworten
                    Anmelden zum Antworten
                    • Älteste zuerst
                    • Neuste zuerst
                    • Meiste Stimmen


                    Support us

                    ioBroker
                    Community Adapters
                    Donate
                    FAQ Cloud / IOT
                    HowTo: Node.js-Update
                    HowTo: Backup/Restore
                    Downloads
                    BLOG

                    406

                    Online

                    32.8k

                    Benutzer

                    82.8k

                    Themen

                    1.3m

                    Beiträge
                    Community
                    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                    ioBroker Community 2014-2025
                    logo
                    • Anmelden

                    • Du hast noch kein Konto? Registrieren

                    • Anmelden oder registrieren, um zu suchen
                    • Erster Beitrag
                      Letzter Beitrag
                    0
                    • Home
                    • Aktuell
                    • Tags
                    • Ungelesen 0
                    • Kategorien
                    • Unreplied
                    • Beliebt
                    • GitHub
                    • Docu
                    • Hilfe