Spotify trackURI about sonos2mqtt HOT 14 CLOSED

We got you covered, the metadata helper has specific support for spotify URLs.

Just use only the spotify uri spotify:track:3b9xTm2eiaCRTGqUEWuzxc the Sonos library will guess the rest.

Can you verify? If you found a place in this library where the Spotify uri isn’t supported that probably has to be changed to call the metadata helper before sending to the Sonos lib.

from sonos2mqtt.

Doesn't seem to work. When I send

spotify:track:3b9xTm2eiaCRTGqUEWuzxc

...to 'sonos/set/sonos-sovrum/queue' I get " Error executing queue for Sonos Sovrum {}" in the log.

from sonos2mqtt.

Same result with setavtransporturi

from sonos2mqtt.

I've got an other, "WOMP".....

How are you sending them to the device? Could you show the mqtt message you're sending? I'll try to replicate the issue. I'm always using mqtt fx to test this stuff out.

Or with your track uri.

from sonos2mqtt.

Ha! I didn't notice until now that we used the same track for testing! :)

from sonos2mqtt.

I think you first have to switch it to an existing queue before you can add anything to the queue. To switch to the queue you send a message to sonos/set/sonos-vardagsrum/adv-command

{
  "cmd":"SwitchToQueue"
}

This might only work if there is a queue, so I suggest to queue one song in the sonos app. Then there is a queue to which you can add Spotify tracks.

from sonos2mqtt.

I tried the adv-command you suggested, but got back "Error executing adv-command for Sonos Vardagsrum {}"

from sonos2mqtt.

And what happens it you switch to an empty queue from the Sonos app? #

from sonos2mqtt.

Same result.

from sonos2mqtt.

I cannot reproduce this issue, need more information.

Node version:
sonos2mqtt version:
Sonos software version (see app):
OS:

from sonos2mqtt.

I'm running the latest published docker image on Ubuntu 19.04 (fully patched)

Sonos software version: 10.6.2, build 54273060
Mosquitto 1.6.8 (eclipse-mosquitto:latest).

If I cutnpaste a full URI (x-sonos-spotify:spotify:track:2UKMqNCVsHrAYzBZMA0rxL?sid=12&flags=8224&sn=7) and publish that to either 'queue' or to 'setavtransporturi' it works in both cases.

If i do the same thing with the Spotify URI (spotify:track:2UKMqNCVsHrAYzBZMA0rxL) I get

Error executing setavtransporturi for Sonos Vardagsrum {}
Error executing queue for Sonos Vardagsrum {}

from sonos2mqtt.

Can you run the latest version with the following command DEBUG=sonos:* sonos2mqtt .... this should enable the debug output.

from sonos2mqtt.

I published spotify:track:3b9xTm2eiaCRTGqUEWuzxc to sonos/set/sonos-vardagsrum/queue:

2020-03-07T08:54:44.147Z sonos:metadata Guessing metadata for spotify:track:3b9xTm2eiaCRTGqUEWuzxc


2020-03-07T08:54:44.149Z sonos:service:avtransport:192.168.240.5 AddURIToQueue({ InstanceID: 0, EnqueuedURI: 'x-sonos-spotify:spotify:track:3b9xTm2eiaCRTGqUEWuzxc?sid=9&flags=8224&sn=7', EnqueuedURIMetaData: { Album: undefined, Artist: undefined, AlbumArtUri: undefined, Title: '', UpnpClass: 'object.item.audioItem.musicTrack', Duration: undefined, ItemId: '00032020spotify%3atrack%3a3b9xTm2eiaCRTGqUEWuzxc', ParentId: undefined, TrackUri: 'x-sonos-spotify:spotify%3atrack%3a3b9xTm2eiaCRTGqUEWuzxc?sid=9&flags=8224&sn=7', ProtocolInfo: undefined, CdUdn: 'SA_RINCON2311_X_#Svc2311-0-Token' }, DesiredFirstTrackNumberEnqueued: 0, EnqueueAsNext: true })


2020-03-07T08:54:44.159Z sonos:service:avtransport:192.168.240.5 Sonos error on AddURIToQueue { faultcode: 's:Client', faultstring: 'UPnPError', detail: { UPnPError: { errorCode: 800 } } }


2020-03-07 09:54:44.160 <error> Error executing queue for Sonos Vardagsrum {"Action":"AddURIToQueue","FaultCode":"s:Client","Fault":"UPnPError","UpnpErrorCode":800,"name":"SonosError"}

from sonos2mqtt.

Issue cannot be reproduced and might be fixed by the new version of node-sonos-ts anyway.

from sonos2mqtt.