[email protected]

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Back to forum
    Posted in: Allo USB Bundle
  • [email protected] premium
    24. März 2018 at 1:54 #34710

    hi, Heiner – Spotify Connect has been stable and working well for the last two weeks. If we run into trouble we will update to beta and reinstall Spotify Connect. Thanks for all your help.

    [email protected] premium
    11. März 2018 at 17:05 #34315

    Hi, Heiner, I’ve been out of town and not listening to music; I’ll update you when I’m back.

    [email protected] premium
    8. März 2018 at 3:23 #34268

    I’ve followed your directions (several times) and there was still no sound coming out when I select the max2play device. Music plays on my other devices (phones, Google Home). I deactivated the Spotify Connect plugin, reinstalled Squeezebox and Audioplayer, and the music played for a minute or so and then dropped out. I could restart the music from the phone and it seems to be okay right now. No Spotify Connect though.
    Thanks for your persistence.

    [email protected] premium
    6. März 2018 at 16:48 #34241

    The error message yesterday referred to the wrong sound card (I have Allo Digital and the error message referred to ALSA) but I didn’t save the message. I will in the future.
    Just now I deactivated the Squeezebox and Audioplayer plugins and moved back the Spotify Connect, and the process is running (no error messages) but there is no sound from our system. This time the Android phone shows that music is playing on the max2play device, so the device itself is remaining stable (not disappearing after a second like it did previously), but no sound. A reboot and a reinstallation of Spotify Connect (and then another Reboot) did not resolve the issue.

    Active plugins are just ALLO, Settings/Reboot, WiFi/LAN, Raspberry Settings and Spotify Connect, in that order. I’m running version 2.45 Rasberry Pi 3 and the output device is allo digione.

    Yesterday when I was running Squeezebox, Squeezelite and Spotty, the music kept stopping every few minutes and then starting again. The max2play device stayed on the phone, but the music dropped out repeatedly.

    Thanks for following up on this issue. We only listen to Spotify on Max2Play, and I’m spending hours trying to troubleshoot.

    [email protected] premium
    5. März 2018 at 18:46 #34230

    Thanks, I installed Spotty successfully on LMS (using your instructions). I have installed the new Spotify Connect and it has not resolved the problem, so I’m going back to Spotty until the next Spotify Connect update.

    [email protected] premium
    2. März 2018 at 19:56 #34183

    I have been trying to install Spotty but the instructions are missing details that are essential for noobies. For example, the ‚How-To‘ link didn’t say which version of deb should be downloaded (I guess it’s arm).
    How can I attach the Squeezebox player? It isn’t showing any player even though I entered authentication for spotify at http://192.168.2.28:9000/settings/index.html?player=
    The settings page says, „Cannot access Spotify services without a player connected.“
    I have disabled all active plugins except for spotty as instructed. Were the player settings on the active plugins page? Is there another set of instructions that I’m missing?
    Sorry for these basic questions. I had not realized how complex max2play was.

    [email protected] premium
    1. März 2018 at 5:51 #34153

    I’m having problems maintaining a connection to spotify connect. My android phone connects to max2play for a few seconds but max2play disappears from the device list as soon as I select it. I have Spotify Premium, and an active max2play license. It worked perfectly for several weeks and stopped working last weekend. It’s on a Raspberry Pi 3 with Allo digione player. I have disconnected the other music players, have installed the beta version of Spotify Connect, updated the max2play to v.2.25, tried with the Beta version, but nothing works.

    The Spotify Connect page shows this error:

    Trying to launch … NOT successful Click here to show detailed information
    INFO:librespot: librespot (). Built on 2017-08-17. Build ID: fMyATDNy
    INFO:librespot_core::session: Connecting to AP „guc3-accesspoint-b-7frq.ap.spotify.com:4070“
    INFO:librespot_core::session: Authenticated as „[useraccount]“ !
    INFO:librespot::audio_backend::alsa: Using alsa sink
    INFO:librespot_core::session: Country: „CA“
    thread ‚main‘ panicked at ‚called Result::unwrap() on an Err value: WireError(InvalidEnumValue(13))‘, /checkout/src/libcore/result.rs:860
    note: Run with RUST_BACKTRACE=1 for a backtrace.

    Thanks

Viewing 7 posts - 1 through 7 (of 7 total)