Using PI as Bluetooth-Speaker – Make Pairing easier

Max2Play Home 2016 (en) Forums Max2Play Add-ons Using PI as Bluetooth-Speaker – Make Pairing easier

Tagged: 

This topic contains 2 replies, has 3 voices, and was last updated by  ghoeher premium 1 year, 6 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • 17. Februar 2019 at 1:02 #44477

    Hi,

    I’m using my PI as airplay and bluetooth streaming endpoint and both work fine. I’ve setup BT in the bluetooth page and I’m using the Bluetooth-Speaker plugin.

    I really like Max2Play and I appreciate all the work that went into it.

    Issue:
    I found it very difficult to pair devices with my pi. The discover-device button sort of reverses the proccess that I expect as end-user. I wasn’t able to pair my firetv at all with the gui.

    How I think it would be great:
    Userstory:
    Goal: I want to to play music from my phone on my pi with bluetooth
    Process:
    – I put the PI into pairing mode by clicking a button on the bluetooth page (alternative PI is always in pairing mode)
    – I scan for BT-devices on my phone and I expect the max2play to show up
    – I connect to the max2play BT and I’m ably to pair with a passcode (or no password at all)

    Workaround:
    Here is how I was able to pair my firetv on the cli:

    – Configure bluetooth device as AUDIO player: sudo hciconfig hci0 class 0x00041C
    – Run bluetoothctl:
    Make the device discoverable and pairable and perform the pairing:

    [bluetooth]# discoverable on
    Changing discoverable on succeeded
    [bluetooth]# pairable on
    Changing pairable on succeeded
    [bluetooth]# agent on
    Agent registered
    [bluetooth]# default-agent
    Default agent request successful
    [CHG] Device XX:XX:XX:XX:XX:XX Connected: yes
    Request confirmation
    [agent] Confirm passkey 424242 (yes/no): yes
    Authorize service
    [CHG] Controller XX:XX:XX:XX:XX:XX Class: 0x0c0000
    [CHG] Controller XX:XX:XX:XX:XX:XX Discoverable: no
    [agent] Authorize service 00000000-0000-0000-0000-000000000000 (yes/no): yes
    [CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 00000000-0000-0000-0000-000000000000
    [CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 00000000-0000-0000-0000-000000000000
    [CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 00000000-0000-0000-0000-000000000000
    [CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 00000000-0000-0000-0000-000000000000
    [CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 00000000-0000-0000-0000-000000000000
    [CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 00000000-0000-0000-0000-000000000000
    [CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 00000000-0000-0000-0000-000000000000
    [Sebastian's Fire TV]# trust
    [CHG] Device XX:XX:XX:XX:XX:XX Trusted: yes
    Changing trust succeeded

    Questions:
    – Are there any plans on making the pairing process more user friendly?
    – Shouldn’t the interface be always configured with a device class as audio player?
    – If I set the class and make my bluetooth adapter permanently discoverable in /etc/bluetooth/main.conf will that get overriden by max2play?

    18. Februar 2019 at 11:23 #44501

    Hi Sebastian,

    Thank you for the detailed feedback!

    I will discuss these points with our head developer in our next meeting.

    17. April 2019 at 19:21 #45062

    Hi Heiner,

    any news regarding this topic?
    I’m also searching for a easier pairing solution …
    It would be very nice to do the pairing from the device you want to pair (e.g. smartphone) without any action required on the M2P device.
    Or at least as Sebastian wrote, after setting M2P into pairing move by a button on the webinterface (or a hardware-button connected to the GPIO).

    Kind regards
    Georg

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

You must be logged in to reply to this topic.

Register here