BETA: piCorePlayer6.0.0 - PI4 support

[simonheard]

So you need to run the following command, for the second command to work.

pcp-load -wi file.tcz


But there is progress, since the player is now listed in the config. I'm confused as to how it's matching the device at disconnect, but not during the connect phase.

After you run the file commands.......I really need to see that output. Then go to the pCP Bluetooth interface and change the name of the player. And then press the "Save" button. Then Disconnect and Reconnect.

Could you clear one thing up - I didn't know I could change the player name in the bluetooth interface - how do I do that, please?

Away from the system at present, but should be able to try this in an hour or so.

Simon

[Zabizabo]

Do not use IP address in the command line.

1 - Start with a freshly burned image, make no edits to the image, except for the next step.
2 - Put a correct wpa_supplicant.conf on your boot partition.
3 - Connect the RPi to your router with an ethernet cable.
4 - Boot the system.
5 - Find the IP address by looking at the router logs, or you should see it in LMS too.
6 - Browse to the pCP web interface, and attach a copy of dmesg and pcp_boot.log.

Thanks Paul,

I will do that this evening. Just one question, do I use the wpa_supplicant.conf # Maintained by piCorePlayer or # Maintained by user?

[paul-]

Could you clear one thing up - I didn't know I could change the player name in the bluetooth interface - how do I do that, please?

Away from the system at present, but should be able to try this in an hour or so.

Simon

From the pCP interface......where it shows paired devices, just change the name and hit save.

[paul-]

Thanks Paul,

I will do that this evening. Just one question, do I use the wpa_supplicant.conf # Maintained by piCorePlayer or # Maintained by user?

Use the maintained by user for now. pCP will use that un-touched.

[simonheard]

Could you clear one thing up - I didn't know I could change the player name in the bluetooth interface - how do I do that, please?

Away from the system at present, but should be able to try this in an hour or so.

Simon

Paul,

Here is the ssh output, some repeated commands


tc@piCorePlayer:~$ pcp-load -wi file.tcz
file is already downloaded.
All files tested good.
tc@piCorePlayer:~$ cat /usr/local/etc/pcp/pcp-bt.conf
EC:81:93:27:64:7D#BOOM 3#1000
tc@piCorePlayer:~$ file /usr/local/etc/pcp/pcp-bt.conf
-sh: file: not found
tc@piCorePlayer:~$ ^C
tc@piCorePlayer:~$ file /usr/local/etc/pcp/pcp-bt.conf
-sh: file: not found
tc@piCorePlayer:~$ cat /usr/local/etc/pcp/pcp-bt.conf
EC:81:93:27:64:7D#Loft#1000
tc@piCorePlayer:~$ cat /usr/local/etc/pcp/pcp-bt.conf
EC:81:93:27:64:7D#Loft#1000
tc@piCorePlayer:~$ file /usr/local/etc/pcp/pcp-bt.conf
-sh: file: not found
tc@piCorePlayer:~$

I've renamed the Boom, here is the bt log:-

pCP Bluetooth extension build:0003
Starting BT Controller
bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
Set Controller UART speed to 3000000 bit/s
Device setup complete
RPi Bluetooth Hardware Address: DC:A6:32:2A:0B7
Starting pCP BT Pairing Agent
BT Controller Ready
01-01 00:00 INFO ------------Starting pCP BT Speaker Daemon v6.0.0.0003------------
01-01 00:00 INFO Resetting asound.conf.
01-01 00:00 INFO Removing bt_ from asound.conf
01-01 00:00 INFO Current contents of /usr/local/etc/pcp/pcp-bt.conf.
01-01 00:00 INFO EC:81:93:27:64:7D#BOOM 3#1000
01-01 00:00 INFO Starting connection signal handlers.
02-17 16:07 INFO ---- Caught Connect signal ----
02-17 16:07 INFO MAC:EC:81:93:27:64:7D
02-17 16:07 INFO PROFILE:a2dp
02-17 16:07 INFO Modes:source
02-17 16:12 INFO ------------Starting pCP BT Speaker Daemon v6.0.0.0003------------
02-17 16:12 INFO Resetting asound.conf.
02-17 16:12 INFO Removing bt_ from asound.conf
02-17 16:12 INFO Current contents of /usr/local/etc/pcp/pcp-bt.conf.
02-17 16:12 INFO EC:81:93:27:64:7D#Loft#1000
02-17 16:12 INFO Found a2dp source EC:81:93:27:64:7D connected.
02-17 16:12 INFO No squeezelite process for device EC:81:93:27:64:7D. Starting squeezelite......
02-17 16:12 INFO Connected Loft
02-17 16:12 INFO Starting squeezelite with output device: bt_Loft
02-17 16:12 INFO Checking for squeezelite pid:12130
02-17 16:12 INFO Player Connected to LMS at: 192.168.2.200:9000
02-17 16:12 INFO Sending Play command for Loft to LMS at 192.168.2.200
02-17 16:12 INFO Starting connection signal handlers.
02-17 16:13 INFO ---- Caught Disconnect signal ----
02-17 16:13 INFO MAC:EC:81:93:27:64:7D
02-17 16:13 INFO PROFILE:a2dp
02-17 16:13 INFO Checking for squeezelite pid:12130
02-17 16:13 INFO Sending Poweroff command for Loft to LMS at 192.168.2.200
02-17 16:13 INFO Disconnected Loft
02-17 16:13 INFO Removing bt_Loft from asound.conf
02-17 16:16 INFO ---- Caught Connect signal ----
02-17 16:16 INFO MAC:EC:81:93:27:64:7D
02-17 16:16 INFO PROFILE:a2dp
02-17 16:16 INFO Modes:source
02-17 16:18 INFO ------------Starting pCP BT Speaker Daemon v6.0.0.0003------------
02-17 16:18 INFO Resetting asound.conf.
02-17 16:18 INFO Removing bt_ from asound.conf
02-17 16:18 INFO Current contents of /usr/local/etc/pcp/pcp-bt.conf.
02-17 16:18 INFO EC:81:93:27:64:7D#Loft#1000
02-17 16:18 INFO Found a2dp source EC:81:93:27:64:7D connected.
02-17 16:18 INFO No squeezelite process for device EC:81:93:27:64:7D. Starting squeezelite......
02-17 16:18 INFO Connected Loft
02-17 16:18 INFO Starting squeezelite with output device: bt_Loft
02-17 16:18 INFO Checking for squeezelite pid:14909
02-17 16:18 INFO Player Connected to LMS at: 192.168.2.200:9000
02-17 16:18 INFO Sending Play command for Loft to LMS at 192.168.2.200
02-17 16:18 INFO Starting connection signal handlers.
02-17 16:25 INFO ---- Caught Disconnect signal ----
02-17 16:25 INFO MAC:EC:81:93:27:64:7D
02-17 16:25 INFO PROFILE:a2dp
02-17 16:25 INFO Checking for squeezelite pid:14909
02-17 16:25 INFO Sending Poweroff command for Loft to LMS at 192.168.2.200
02-17 16:25 INFO Disconnected Loft
02-17 16:25 INFO Removing bt_Loft from asound.conf
02-17 16:28 INFO ---- Caught Connect signal ----
02-17 16:28 INFO MAC:EC:81:93:27:64:7D
02-17 16:28 INFO PROFILE:a2dp
02-17 16:28 INFO Modes:source


The speaker is on, and about to auto power off.

I looked at usr/local/etc/pcp/ and there is a file pcp-bt.conf in there. it contains one line reading EC:81:93:27:64:7D#Loft#1000

Simon

[paul-]

Well that is connecting fine now.

[simonheard]

Well that is connecting fine now.

No, it only connected when I saved the name change, which restarted the connection. When I power of and then on again, it does not reconnect. The ssh output seems to show that the .conf file isn't being found. So the issue remains, I'm afraid.

[paul-]

It's quite possibly something odd with your device, that there is no way for me to test. I don't have a single device that only connects the A2DP channel. All of my speakers also connect the SCO profile. But programatically, there is no difference.

I'm using my BT earbuds right now. I've done this many times, and it works every time for me. So I'm not even sure where to go.

[Paul Webster]

So the issue remains, I'm afraid.

Perhaps worth checking to see if there is a firmware update available for the BOOM 3.
There is always a danger of firmware updates making things worse - so I would suggest first checking to see if there is one and then trying to work out what the update changes to see if anything might be relevant and then check around other forums to see if people had success using it

https://support.ultimateears.com/en/boom3/#collapse26

[simonheard]

It's quite possibly something odd with your device, that there is no way for me to test. I don't have a single device that only connects the A2DP channel. All of my speakers also connect the SCO profile. But programatically, there is no difference.

I'm using my BT earbuds right now. I've done this many times, and it works every time for me. So I'm not even sure where to go.

I think you may be right. I've just reinstalled the .iso on a reformatted sd card, and although the BOOM is still not reconnecting, I have paired my earbuds and they are working perfectly with the SCO profile.

Any chance you could repost the beta 5 .iso - I had things working with that!

Simon

pCP Bluetooth extension build:0003
Starting BT Controller
bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
Set Controller UART speed to 3000000 bit/s
Device setup complete
RPi Bluetooth Hardware Address: DC:A6:32:2A:0B7
Starting pCP BT Pairing Agent
BT Controller Ready
02-17 17:47 INFO ------------Starting pCP BT Speaker Daemon v6.0.0.0003------------
02-17 17:47 INFO Resetting asound.conf.
02-17 17:47 INFO Removing bt_ from asound.conf
02-17 17:47 INFO Current contents of /usr/local/etc/pcp/pcp-bt.conf.
02-17 17:47 INFO EC:81:93:27:64:7D#Loft#1000
02-17 17:47 INFO Starting connection signal handlers.
02-17 17:48 INFO ---- Caught Connect signal ----
02-17 17:48 INFO MAC:EC:81:93:27:64:7D
02-17 17:48 INFO PROFILE:a2dp
02-17 17:48 INFO Modes:source
02-17 17:51 INFO ---- Caught Disconnect signal ----
02-17 17:51 INFO MAC:EC:81:93:27:64:7D
02-17 17:51 INFO PROFILE:a2dp
02-17 17:51 INFO Removing bt_Loft from asound.conf
02-17 17:52 INFO ---- Caught Connect signal ----
02-17 17:52 INFO MAC:00:1F:F0:0E:07:F4
02-17 17:52 INFO PROFILE:sco
02-17 17:52 INFO Modes:source, sink
02-17 17:52 INFO Starting a2dp background monitor.
02-17 17:52 INFO ---- Caught Connect signal ----
02-17 17:52 INFO MAC:00:1F:F0:0E:07:F4
02-17 17:52 INFO PROFILE:a2dp
02-17 17:52 INFO Modes:source
02-17 17:52 INFO Connected Melomania R Cambridge
02-17 17:52 INFO Starting squeezelite with output device: bt_Melomania_R__Cambridge
02-17 17:52 INFO Device: dev_00_1F_F0_0E_07_F4, connected normally. Monitor exiting.
02-17 17:52 INFO Checking for squeezelite pid:10883
02-17 17:52 INFO Player Connected to LMS at: 192.168.2.200:9000
02-17 17:52 INFO Sending Play command for Melomania R Cambridge to LMS at 192.168.2.200
02-17 17:52 INFO ---- Caught Disconnect signal ----
02-17 17:52 INFO MAC:00:1F:F0:0E:07:F4
02-17 17:52 INFO PROFILE:sco
02-17 17:55 INFO ---- Caught Disconnect signal ----
02-17 17:55 INFO MAC:00:1F:F0:0E:07:F4
02-17 17:55 INFO PROFILE:a2dp
02-17 17:55 INFO Checking for squeezelite pid:10883
02-17 17:55 INFO Sending Poweroff command for Melomania R Cambridge to LMS at 192.168.2.200
02-17 17:55 INFO Disconnected Melomania R Cambridge
02-17 17:55 INFO Removing bt_Melomania_R__Cambridge from asound.conf
02-17 17:55 INFO ---- Caught Connect signal ----
02-17 17:55 INFO MAC:00:1F:F0:0E:07:F4
02-17 17:55 INFO PROFILE:sco
02-17 17:55 INFO Modes:source, sink
02-17 17:55 INFO Starting a2dp background monitor.
02-17 17:55 INFO ---- Caught Connect signal ----
02-17 17:55 INFO MAC:00:1F:F0:0E:07:F4
02-17 17:55 INFO PROFILE:a2dp
02-17 17:55 INFO Modes:source
02-17 17:55 INFO Connected Melomania R Cambridge
02-17 17:55 INFO Starting squeezelite with output device: bt_Melomania_R__Cambridge
02-17 17:55 INFO Device: dev_00_1F_F0_0E_07_F4, connected normally. Monitor exiting.
02-17 17:55 INFO Checking for squeezelite pid:12376
02-17 17:55 INFO Player Connected to LMS at: 192.168.2.200:9000
02-17 17:55 INFO Sending Play command for Melomania R Cambridge to LMS at 192.168.2.200
02-17 17:55 INFO ---- Caught Disconnect signal ----
02-17 17:55 INFO MAC:00:1F:F0:0E:07:F4
02-17 17:55 INFO PROFILE:sco