Hi All,
I'm trying to set up my UE Wonderboom as a BT speaker for a Pi3a+ board
running picoreplayer 4.1.0. Wifi working, and BT extensions installed,
but the Wonderboom just will not pair. Any pointers for me?
simonheard
I'd appreciate some help with an issue I'm experiencing. I'm running b9
on a Pi4B LMS on a separate Ubuntu server, ethernet connections. I can
connect a BOOM 3 BT speaker but when it's switched off and on again, I
have to restart the BT speaker daemon to get any sound. Here is the BT
log.
pCP Bl
paul- wrote:
> The connection right after startup is missing alot of steps.The
> initial message looks like your speaker might connect as the daemon is
> starting.
>
> 1) Shut off the speaker when booting your pCP device.
> 2) When you switch off the speaker, give it 5 seconds or so before
paul- wrote:
> Lots of changes in the Bluetooth code, but same driver base as pcp5.
> Ill have to run a fresh install and test. My upgraded version works
> fine. So you can see your speakers in LMS, they just wont play sound?
>
> Can you try to change your player name, and then press save
paul- wrote:
> Lots of changes in the Bluetooth code, but same driver base as pcp5.
> Ill have to run a fresh install and test. My upgraded version works
> fine. So you can see your speakers in LMS, they just wont play sound?
>
> Can you try to change your player name, and then press save
paul- wrote:
> Forget about the squeezelite page, and the default picoreplayer device.
> Do everything from the bluetooth page.
>
> Pair device
> Once pairing is complete, Disconnect device (you can use the button)
> Wait about 5 seconds,
> Reconnect the device (You can use the button)
> Wha
paul- wrote:
> The device is connecting fine. And squeezelite is starting fine.
> Perhaps you are just clicking things too fast.
>
> When a player connects to LMS, it will take a bit to show up in the LMS
> web interface..although the player is still connected and available.
Thanks,
Fo
carsten_h wrote:
> I think that is the behaviour I also had at the beginning, but that
> suddenly disappeard and the entry for my headphone stays there. The only
> thing I changed was to deinstall Bluetooth and install it again, then
> restarted, paired my headphones and then the entry stays the
paul- wrote:
> If you started from a b9 fresh image, you will be on the latest config.
> I added a build number to the log, 0001 is the current release.
> Restarting the daemon really doesnt do anything different. It does
> check for dangling devices and processes, and cleans it up. But the
carsten_h wrote:
> I think that is the behaviour I also had at the beginning, but that
> suddenly disappeard and the entry for my headphone stays there. The only
> thing I changed was to deinstall Bluetooth and install it again, then
> restarted, paired my headphones and then the entry stays the
paul- wrote:
> Simon,
>
> Do me a favor and do not restart the daemon. Power off your bluetooth
> speakers. Then reboot your system.
>
> After it is well started, turn on your BT speakers..wait for couple
> of minutes, Then disconnect them. Wait a couple of minutes and restart
> them.
>
paul- wrote:
> Simon, I really wanted more cycles, but the Unknown device is the
> problem. Does the device show in the paired device table on the web
> interface?
No. I have four devices showing in LMS and the fifth (BOOM 3) only shows
after daemon restart. The four are all on ethernet connec
paul- wrote:
> PCP shows the paired devices, not lms. Can you post a screenshot of the
> pCP Bluetooth web page.
Here you go, Paul
+---+
|Filename: Bluetooth.jpg|
|Download: http://for
paul- wrote:
> Alright run 2 commands from an ssh session for me. It appears there is
> a problem in the config file.
>
> >
Code:
> >
> tc@pCP-devel:~$ cat /usr/local/etc/pcp/pcp-bt.conf
> 19:08:28:16:01:B3#TOZO T6#1000
>
> tc@pCP-devel:~$ file /usr/local/et
paul- wrote:
> Before I go down the wrong rabbit hole, can you post exact output. It
> sounds like the config file is missing, which should not happen.
After first command:-
tc@piCorePlayer:~$ tc@pCP-devel:~$ cat /usr/local/etc/pcp/pcp-bt.conf
-sh: tc@pCP-devel:~$: not found
tc@piCorePlaye
paul- wrote:
> Before I go down the wrong rabbit hole, can you post exact output. It
> sounds like the config file is missing, which should not happen.
And after adding the second command:-
tc@piCorePlayer:~$ tc@pCP-devel:~$ cat /usr/local/etc/pcp/pcp-bt.conf
-sh: tc@pCP-devel:~$: not foun
paul- wrote:
> Dont copy my command prompts, just the commands
>
> >
Code:
> >
> cat /usr/local/etc/pcp/pcp-bt.conf
>
> file /usr/local/etc/pcp/pcp-bt.conf
>
> >
tc@piCorePlayer:~$ cat /usr/local/etc/pcp/pcp-bt.conf
tc@piCorePlayer:~
paul- wrote:
> Simon,
>
> Please press the "Forget Device" button for any paired devices.
> Power off your bluetooth devices.
>
> Then update the bluetooth extensionsreboot. current build number
> will be 6.0.0.0003
>
> Once started, Scan and Pair your device. You should never need to
paul- wrote:
> Simon,
>
> Please press the "Forget Device" button for any paired devices.
> Power off your bluetooth devices.
>
> Then update the bluetooth extensionsreboot. current build number
> will be 6.0.0.0003
>
> Once started, Scan and Pair your device. You should never need to
paul- wrote:
> 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.
simonheard wrote:
> 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,
He
paul- wrote:
> 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- wrote:
> 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
paul- wrote:
> We are not using the sco profile, but it does seem to connect faster,
> then I have the ability to give it a kick.
>
> There is no feasible way for me to go back. Use a rpi3, and pCP 5.0.0.
Thanks Paul,
I'e had pcp 5.0.0 running on an rpi3b for the last two, and have
success
Delighted to report that I am now running bluetooth successfully with
the latest update. BOOM3 now works!
Simon
simonheard's Profile: http://forums.slimdevices.com/member.php?userid=57556
View this thread: http://forums.s
25 matches
Mail list logo
