Reply To: [NEW UPDATE] Spotify Connect Server – beta available!

Max2Play Home 2016 (en) Forums Max2Play Development (Ideas, Wishes) [NEW UPDATE] Spotify Connect Server – beta available! Reply To: [NEW UPDATE] Spotify Connect Server – beta available!

22. Juli 2017 at 22:50 #30045

I cant seem to get the Spotify Connect plugin for M2P to work. I can not see M2P in spotify app (only with airplay)

The plugin has started correctly. I get the message on the top of the page:
Trying to launch … successful with ID 4635

The Debug log show the follwing:
#### Librespot Output ####
INFO:librespot: librespot cc9dba8 (2017-03-26). Built on 2017-07-17. Build ID: 8zQE3Bpb
INFO:librespot::session: Connecting to AP „gew1-accesspoint-b-wwbl.ap.spotify.com:4070“
INFO:librespot::session: Authenticated as „dongilles“ !
INFO:librespot::session: Country: „NL“
INFO:librespot::audio_backend::alsa: Using alsa sink

#### Librespot Command Line Options ####
error: Required option ’name‘ missing.
Usage: /opt/spotifyconnect/librespot [options]

Options:
-c, –cache CACHE Path to a directory where files will be cached.
–disable-audio-cache
Disable caching of the audio data.
-n, –name NAME Device name
-b, –bitrate BITRATE
Bitrate (96, 160 or 320). Defaults to 160
–onstart PROGRAM
Run PROGRAM when playback is about to begin.
–onstop PROGRAM
Run PROGRAM when playback has ended.
-v, –verbose Enable verbose output
-u, –username USERNAME
Username to sign in with
-p, –password PASSWORD
Password
–disable-discovery
Disable discovery mode
–backend BACKEND
Audio backend to use. Use ‚?‘ to list options
–device DEVICE Audio device to use. Use ‚?‘ to list options
–mixer MIXER Mixer to use

I tried giving it a other name by typing
-n, –name test in the Command Line Options part of the plug in. But then I get an other error:

#### Librespot Output ####
error: Option ’name‘ given more than once.
Usage: /opt/spotifyconnect/librespot [options]

I am still really new to this, can someone help me?