Raspberry PI not showing up (Balena-Sound)

Project help balenaSound
, ,
1

Hi! I followed your Guide: https://www.balena.io/blog/turn-your-old-speakers-or-hi-fi-into-bluetooth-receivers-using-only-a-raspberry-pi/ and it seems to be working mostly… Spotify works and everything but it doesn’t show up as a bluetooth device. All Services including Bluetooth are marked as running and restarting the bluetooth agent doesn’t seem to help. My Raspberry Pi is a RPi 3 B+. Here is a copy of my Bluetooth log: 18.12.20 13:45:07 (+0100) bluetooth Running balena base image entrypoint…
18.12.20 13:45:07 (+0100) bluetooth — Bluetooth —
18.12.20 13:45:07 (+0100) bluetooth Starting bluetooth service with settings:
18.12.20 13:45:07 (+0100) bluetooth - Device name: balenaOS 7c79
18.12.20 13:45:07 (+0100) bluetooth - HCI interface: hci0
18.12.20 13:45:07 (+0100) bluetooth - Pairing mode: SSP
18.12.20 13:45:07 (+0100) bluetooth - PIN code: 0000
18.12.20 13:45:07 (+0100) bluetooth Available HCI interfaces: hci0
18.12.20 13:45:07 (+0100) bluetooth Resetting hci0
18.12.20 13:45:07 (+0100) bluetooth Configuring selected interface: hci0
18.12.20 13:45:07 (+0100) bluetooth hci0 Set Connectable complete, settings: powered connectable ssp br/edr le secure-conn
18.12.20 13:45:07 (+0100) bluetooth hci0 Set Bondable complete, settings: powered connectable bondable ssp br/edr le secure-conn
18.12.20 13:45:07 (+0100) bluetooth hci0 Set Discoverable complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn
18.12.20 13:45:07 (+0100) bluetooth hci0 Set Secure Simple Pairing complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn
18.12.20 13:45:07 (+0100) bluetooth Pairing mode set to ‘Secure Simple Pairing Mode (SSPM)’. PIN code is NOT required.
18.12.20 13:45:09 (+0100) bluetooth Bluetooth agent started!
18.12.20 13:53:00 (+0100) spotify [2020-12-18T12:53:00Z INFO librespot_playback::player] Loading <What’s Up Danger (with Black Caviar)> with Spotify URI spotify:track:5zsHmE2gO3RefVsPyw2e3T
18.12.20 13:53:00 (+0100) spotify [2020-12-18T12:53:00Z INFO librespot_playback::player] <What’s Up Danger (with Black Caviar)> (222306 ms) loaded
18.12.20 13:53:01 (+0100) sound-supervisor Playback started, announcing 192.168.0.23 as multi-room master!
18.12.20 13:53:33 (+0100) Killing service ‘bluetooth sha256:d248a2c53b76f795627ec99d23e909a913f5f94e85856c03f4a3cdb170586f91’
18.12.20 13:53:46 (+0100) Service exited ‘bluetooth sha256:d248a2c53b76f795627ec99d23e909a913f5f94e85856c03f4a3cdb170586f91’
18.12.20 13:53:46 (+0100) Killed service ‘bluetooth sha256:d248a2c53b76f795627ec99d23e909a913f5f94e85856c03f4a3cdb170586f91’
18.12.20 13:53:47 (+0100) Installing service ‘bluetooth sha256:d248a2c53b76f795627ec99d23e909a913f5f94e85856c03f4a3cdb170586f91’
18.12.20 13:53:47 (+0100) Installed service ‘bluetooth sha256:d248a2c53b76f795627ec99d23e909a913f5f94e85856c03f4a3cdb170586f91’
18.12.20 13:53:47 (+0100) Starting service ‘bluetooth sha256:d248a2c53b76f795627ec99d23e909a913f5f94e85856c03f4a3cdb170586f91’
18.12.20 13:53:49 (+0100) Started service ‘bluetooth sha256:d248a2c53b76f795627ec99d23e909a913f5f94e85856c03f4a3cdb170586f91’
18.12.20 13:53:48 (+0100) bluetooth Running balena base image entrypoint…
18.12.20 13:53:49 (+0100) bluetooth — Bluetooth —
18.12.20 13:53:49 (+0100) bluetooth Starting bluetooth service with settings:
18.12.20 13:53:49 (+0100) bluetooth - Device name: balenaOS 7c79
18.12.20 13:53:49 (+0100) bluetooth - HCI interface: hci0
18.12.20 13:53:49 (+0100) bluetooth - Pairing mode: SSP
18.12.20 13:53:49 (+0100) bluetooth - PIN code: 0000
18.12.20 13:53:49 (+0100) bluetooth Available HCI interfaces: hci0
18.12.20 13:53:49 (+0100) bluetooth Resetting hci0
18.12.20 13:53:49 (+0100) bluetooth Configuring selected interface: hci0
18.12.20 13:53:49 (+0100) bluetooth hci0 Set Connectable complete, settings: powered connectable ssp br/edr le secure-conn
18.12.20 13:53:49 (+0100) bluetooth hci0 Set Bondable complete, settings: powered connectable bondable ssp br/edr le secure-conn
18.12.20 13:53:49 (+0100) bluetooth hci0 Set Discoverable complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn
18.12.20 13:53:49 (+0100) bluetooth hci0 Set Secure Simple Pairing complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn
18.12.20 13:53:49 (+0100) bluetooth Pairing mode set to ‘Secure Simple Pairing Mode (SSPM)’. PIN code is NOT required.
18.12.20 13:53:50 (+0100) bluetooth Bluetooth agent started!

I hope you can help me…

2

Hello @Skratymir,

I can’t spot anything off in the logs you just shared. What device are you using to scan Bluetooth? Is that device able to detect other Bluetooth devices?

Cheers,
Nico.

4

Yes it can. I tried it using my phone (Samsung Galaxy Note 10) and my Laptop (Dell XPS15)

5

Hi, something you could try is to try running bluetoothctl from a terminal to the container, then the show command will tell us if the device is discoverable or not. It should say pairable: yes and discoverable: yes. If either of these say no you can toggle it by using pairable on|off and discoverable on|off

7

Hello everyone,

It seems that I am having similar troubles with BT: I can’t find the Pi in the pairing menu of my Sony Walkman NW-A55.

It is strange because I was able to pair without any issue:

  • my iPhone and MacBook to the Pi,
  • my Walkman to a headphone and to a BT speaker.

Only Walkman + Pi is not matching.

I have done what is suggested above and here is what I get:

    Class: 0x000c0000
    Powered: yes
    Discoverable: yes
    DiscoverableTimeout: 0x00000000
    Pairable: yes

So nothing looking wrong on this side…

Thanks in advance for the support!

Best,

BenGast

13

Hello,

Thanks for providing the output of the bluetoothctl command and you are right - all seems fine on the Pi side.

Unfortunately, we do not have a Sony Walkman NW-A55 to be able to reproduce this.

Here are some suggestions

  • Can you run dmesg and journalctl -u bluetooth --no-pager in the hostOS terminal? We would be grateful if you can open an issue on this repo with the logs.

  • You could also try changing the pairing mode to legacy one which requires a pin that you can set up.
    You would have to set the following service variables for the bluetooth service:

  • Set BLUETOOTH_PAIRING_MODE to LEGACY

  • Set BLUETOOTH_PIN_CODE to whatever you would like (Must be numeric and up to six digits (1 - 999999))

You can find more info on how to set up variables here

Hope this helps

15

Hey @bengast. Have you had any success collecting further logs as suggested by the colleague?

17

@pranasziaukas Thanks a lot for pinging me. In fact, I had missed the reply of @rahul-thakoor. I will provide the logs in the next couple of days.

Thanks for the support!

Best,

18

No problem, cheers!