Bluetooth does not auto connect

Max2Play Home 2016 (en) Forums Max2Play on Raspberry PI Bluetooth does not auto connect

This topic contains 10 replies, has 2 voices, and was last updated by  clarenze premium 15 hours, 54 minutes ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • 6. März 2019 at 11:23 #44671

    Hi all,

    I successfully setup a bluetooth connection to my SB Roar speaker. When I manually connect and manually start a multisqueeze instance it works fine, but it will not auto connect.
    Here is what I did:
    – Turn off speaker
    – Reboot raspi
    – Turn on speaker
    => nothing happens.

    When I click „Connect“ on the max2play Bluetooth page, the speaker makes a sound and the bluetooth address turns green. But the multisqueeze instance is still inactive until I click „Start squeezelite“.

    I am using max2play 2.47 on a Raspi.

    Here is the DEBUG info from the Bluetooth page:

    #### Bluetooth Installation ####

    #### Bluetooth Dongle ####
    hci0: Type: Primary Bus: UART
    BD Address: B8:27:EB:ED:96:81 ACL MTU: 1021:8 SCO MTU: 64:1
    RX bytes:766 acl:0 sco:0 events:49 errors:0
    TX bytes:2264 acl:0 sco:0 commands:49 errors:0

    #### DEVICE SB ROAR SR20A ####
    Name: SB ROAR SR20A
    Alias: SB ROAR SR20A [rw]
    Address: 00:02:3C:5F:60:AA
    Icon: audio-card
    Class: 0x2c041c
    Paired: 1
    Trusted: 1 [rw]
    Blocked: 0 [rw]
    Connected: 0
    UUIDs: [Headset, AudioSink, AVRemoteControlTarget, AdvancedAudioDistribution, AVRemoteControl, Handsfree]

    #### BLUEALSA RUNNING ####

    And here is the DEBUG info from the multisqueeze page:

    Squeezelite Max2Play v1.0.2 based on v1.8.4-726, Copyright 2012-2015 Adrian Smith, 2015-2016 Ralph Irving.

    ### Configuration of Audioplayers
    SQUEEZELITE_PARAMETER=-o sysdefault:CARD=sndrpihifiberry -a 80:4:: -C 5
    SHAIRPORT_PARAMETER=-d default:CARD=sndrpihifiberry
    YMPD_PARAMETER=–webport 8081
    MULTISQUEEZE_PARAMETER_1=-o plug:bluetooth -a 80:4::
    MULTISQUEEZE_PARAMETER_0=-o sysdefault:CARD=sndrpihifiberry -a 80:4::
    LMSIP=squeeze:[email protected]:9000/

    #### SQUEEZELITE -l ####
    Output devices:
    null – Discard all samples (playback) or generate zero samples (capture)
    plugequal – Equalizer for plughw:0,0
    bluetooth – Your Bluetooth device 00:02:3C:5F:60:AA
    default:CARD=ALSA – bcm2835 ALSA, bcm2835 ALSA – Default Audio Device
    sysdefault:CARD=ALSA – bcm2835 ALSA, bcm2835 ALSA – Default Audio Device
    dmix:CARD=ALSA,DEV=0 – bcm2835 ALSA, bcm2835 ALSA – Direct sample mixing device
    dmix:CARD=ALSA,DEV=1 – bcm2835 ALSA, bcm2835 IEC958/HDMI – Direct sample mixing device
    dsnoop:CARD=ALSA,DEV=0 – bcm2835 ALSA, bcm2835 ALSA – Direct sample snooping device
    dsnoop:CARD=ALSA,DEV=1 – bcm2835 ALSA, bcm2835 IEC958/HDMI – Direct sample snooping device
    hw:CARD=ALSA,DEV=0 – bcm2835 ALSA, bcm2835 ALSA – Direct hardware device without any conversions
    hw:CARD=ALSA,DEV=1 – bcm2835 ALSA, bcm2835 IEC958/HDMI – Direct hardware device without any conversions
    plughw:CARD=ALSA,DEV=0 – bcm2835 ALSA, bcm2835 ALSA – Hardware device with all software conversions
    plughw:CARD=ALSA,DEV=1 – bcm2835 ALSA, bcm2835 IEC958/HDMI – Hardware device with all software conversions
    default:CARD=sndrpihifiberry – snd_rpi_hifiberry_dacplus, – Default Audio Device
    sysdefault:CARD=sndrpihifiberry – snd_rpi_hifiberry_dacplus, – Default Audio Device
    dmix:CARD=sndrpihifiberry,DEV=0 – snd_rpi_hifiberry_dacplus, – Direct sample mixing device
    dsnoop:CARD=sndrpihifiberry,DEV=0 – snd_rpi_hifiberry_dacplus, – Direct sample snooping device
    hw:CARD=sndrpihifiberry,DEV=0 – snd_rpi_hifiberry_dacplus, – Direct hardware device without any conversions
    plughw:CARD=sndrpihifiberry,DEV=0 – snd_rpi_hifiberry_dacplus, – Hardware device with all software conversions

    Where does the LMSIP parameter come from? That’s the address to the old squeezeboxserver. Meanwhile I am using the squeezebox server on max2play. How do I get rid of this setting?



    7. März 2019 at 15:17 #44691

    Hi Clarenze,

    That should be Shairport’s advanced options‘ Shairport/Squeezelite automatic Audio-Switch.

    8. März 2019 at 8:19 #44712

    thanks, but that was only a side question. do you have an idea why bluetooth does not connect and why squeezelite instance #2 does not start?

    8. März 2019 at 16:44 #44715

    Sorry, the answer was half out the door yesterday.

    We’ve not had any experience with the SB Roar nor with the automatic switch on MultiSqueeze.

    Could you try changing the outputs to BT on Audioplayer and your primary player on MultiSqueeze to see if this makes a difference?

    8. März 2019 at 20:37 #44718

    no, it does not. the first problem is that BT does not auto-connect. the multisqueeze instance not being started is problem #2.

    11. März 2019 at 12:39 #44740

    The auto-connect function works in tandem with the BT device’s own protocol for connection. Some speakers need constant re-connection, some are completely open to all pairings, some require a code to be entered. As mentioned, we have not had any experience with the SB Roar but seems to be an advanced Bluetooth solution.
    Please try to do the apt-get update upgrade (takes a few minutes) through our Raspberry Settings to rule out any possible dependency issue with Raspbian’s packages (our BT solution is directly based upon the official Raspbian solution).

    Please also make sure the „Bluetoooth-Speaker“ player below the pairing list is not active or in autostart.

    Meanwhile, I will try to recreate the issue here with a Pi3B and Max2Play 2.47 image. Please let me know if there any other factors in your system (like LMS installed) that might also recreate.

    12. März 2019 at 9:26 #44749

    I did the upgrade and a reboot but the speaker still did not auto-connect. Then I did a manual connect and turned off the speaker again. After that the auto-connect worked. Also the second squeezebox instance was started automatically. But I don’t hear any sound. Squeezebox server shows that it is playing something on the bluetooth output, but the SB Blaster stays silent.

    Bluetooth-Speaker is not active and I don’t have anything special installed (only what you can configure through max2play).

    14. März 2019 at 20:44 #44769

    Do you have any more tips for me?

    Today I noticed that when Bluetooth is not connected and I play radio via the hifiberry output, the stream stops every couple of minutes. Also squeezeplayer will ignore my attempts to select „No synchronization“. I killed the blueooth squeezeplayer instance now. Hope that will help.

    15. März 2019 at 15:42 #44780

    Hi clarenze,

    Very odd. We’ve had a few RPi 3B+ whose Bluetooth connection was very unreliable. It also shares the same antenna as the WiFi connection, so using both can cause dropouts.
    If you have not yet, try using the BT pairing with ethernet connection and WiFi disabled.

    16. März 2019 at 9:01 #44781

    Thanks, but it still does not work reliably.
    Here is what I did:
    – connected ethernet
    – disabled WIFI
    – rebooted
    – turned on Bluetooth speaker
    => speaker connected, max2play started second multisqueeze instance
    – started radio stream on squeezeplay bluetooth channel
    => worked
    – turned speaker off
    => bluetooth connection turns red in max2play GUI; bluetooth multisqueeze instance stays; squeezebox continues to stream (seconds count up)
    – turned speaker on
    => bluetooth connection turns green; squeezebox continues to stream; no sound
    – stopped bluetooth squeezebox instance
    – started bluetooth squeezebox instance
    => sound starts playing on speaker

    So the problem seems to be that mulitsqueeze does not stop the bluetooth squeezeplayer, when bluetooth is disconnected.

    23. März 2019 at 8:43 #44857

    is it planned to fix this issue?

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

You must be logged in to reply to this topic.

Register here