... still banging my head against the wall with setting up an access
point on this image. I moved back to the method used in SQPOS installing
hostapd and bridge-utils following 'these'
(https://www.cyberciti.biz/faq/debian-ubuntu-linux-setting-wireless-access-point/)
instructions: Only
When LMS is showing the Power is turned on to a squeezelite player, then
Active low means the GPIO will show '0' and active high means the GPIO
will show a '1'
I would think for a backlight, you would want active high.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage:
I've always had problems with the --user flag too. Doing it the way you
are doing it is much better anyway (From a security standpoint)
But it's actually a good question as to why it does it this way..
pCP used to drive the connection from it's end, but with the new system,
The connect is not driven from pCP anymore, pCP expects the connection
to be driven from the speaker (During pairing, the device is set to
trusted, so it can connect anytime) This was done to allow many
different devices
paul- wrote:
>
> Normally when a speaker is powered up, it tried to connect to the device
> in which it's paired, but in the case of your echo, how do you tell it
> to connect to bluetooth?
It is always powered on - ready to do whatever we ask (within reason).
To make it connect we (I) say
Ge Ba wrote:
>
> Maybe a little How-to doc for setting up and connecting/disconnecting
> Bluetooth devices would be helpful
> It's still not self-explanatory despite the good work, sorry to say ;)
Been on my todo list for a month or so.just cannot find time to do
it.
piCorePlayer a
Could a docker image be smart enough to install an architecture
dependent package?
--
Michael
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
Paul Webster wrote:
>
> Next step is to reboot pCP but will have to wait until people stop
> listening over lunch.
Did not reconnect on reboot.
However, going through the process manually to Connect and then restart
the BT Speaker Daemon did work.
Code:
03-25
Successfully upgraded 5.0.1 to 6.0.0 on my 3B+ and connected my
Bluetooth Speaker Marshall Acton.
General handling is fine, took me a while to get behind the concept of
getting another player device dedicated only to the bt.
Working fine now, thanks for the good work.
PS:
Maybe a little
Alright, I found the issue. Python error handling is cool and annoying
at the same time. Update your pcp-bt6 package, (Or install fresh if
you have removed it). If you look at eh log you should see v6.0.0.0004
for the daemon version.
Step 1: Scan (Your alexa device will act like it's
castalla wrote:
> Tried with Echo dot - appeared as bt device, but never showede up in the
> LMS list ... afraid I just got so lost that I uninstalled the bluetooth
> routines.
>
> A guide would be very useful.
Well I just set up a spare pi as a BT device, took some time and a lot
of head
paul- wrote:
> Been on my todo list for a month or so.just cannot find time to do
> it.
Tried with Echo dot - appeared as bt device, but never showede up in the
LMS list ... afraid I just got so lost that I uninstalled the bluetooth
routines.
A guide would be very useful.
LMS server:
kidstypike wrote:
> Well I just set up a spare pi as a BT device, took some time and a lot
> of head scratching, but I managed to pair it to an Echo Dot I purchased
> Black Friday but never bothered to set up until now. Shows in LMS as a
> player, playing now no problem.
>
> Don't ask me to
Yup, works just fine.
29853
Actually not that fine :)Let me do a little debugging.
+---+
|Filename: 2020-03-25_19-17.png |
|Download:
On my VM, the log file is owned as so:
Code:
-rw-r--r-- 1 squeezeboxserver nogroup 160735 Mar 25 12:28 server.log
I think specifying the user is better done with "docker run --user=..."
Perhaps the image is built by the default root user? Do you
I attach you here the files used in Volumio where the display work.
Hope these are useful to you...
+---+
|Filename: DacBerry_Display_Volumio_Plugin.zip |
|Download:
ElFishi wrote:
> You find details of my system 'here'
> (https://forums.slimdevices.com/showthread.php?107366-picoreplayer-3-11-waveshare-3-5-TFT-jivelite-Raspberry-Pi-2B=934132=1#post934132).
> I moved to pCP 6.0 since, not via an in-situ upgrade but starting from a
> fresh download.
>
>
paul- wrote:
> did you try to drop the '/' from the end of --logdir
Yes, just tried that, same behaviour.
As I said earlier, it looks like the files are being created *before*
the process drops to the 'squeezeboxserver' user, so have root:root
ownership and only root can write.
If I change
paul- wrote:
> Not sure what's going on there, but the connection or disconnection is
> driven from the speaker. You might just try to forget it, and make
> sure to reset the bluetooth in the echo too. It could be a conflict
> between old/new settings.
Was just going through that process
paul- wrote:
> Unfortunately dmesg won't show anything. But the piscreen driver should
> not be causing a conflict.
>
> I'm not sure what you mean by turning off the DAC. If you are turning
> off the DAC, then there is a good chance squeezelite is terminating
> without setting the gpio
Ok, just changed the startup script to:
Code:
#!/bin/sh
su squeezeboxserver -s /bin/bash -c "/usr/sbin/squeezeboxserver --user
squeezeboxserver --prefsdir /var/lib/squeezeboxserver/prefs --logdir
/var/log/squeezeboxserver --cachedir
M-H wrote:
>
> It might be like pointed out 'here '
> (www.raspberrypi.org/forums/viewtopic.php?t=245931)
I had a FEW disks not working OKE with UAS ,
and by disabeling UAS in the new xHCI driver ( default with Pi 4 and
USB3 disks ) I got my disks to perform more reliably.
In fact it were
Yes.
(and the container/image would grow too fast anyway, the fs being
layered )
2 SB 3 1 PCP 6 Libratone Loop, Zipp, Zipp Mini iPeng (iPhone +
iPad) LMS 7.9 (linux) with plugins: CD Player, WaveInput, Triode's BBC
iPlayer by bpa IRBlaster by Gwendesign (Felix) Smart Mix, Music
That's what I'm planning to do, have LMS itself *inside* the container
image. The config / music / logs / database etc. would be outside,
passed into the container as volumes.
Ideally Michael's nightly build process would rebuild the container
after it has rebuilt the debs, and push the new
Right.
So the auto-updater could show on the interface a message that a new
version is available, but should not try to DL it.
I guess the start-up script could be rigged to make a check/pull before
start --or not... my own LMS wasn't built yesterday :)
Also, we're talking Docker but systemd
Ok, I thought LMS was running, but turns out it's not:
Code:
2020-03-25 11:01:44 squeezeboxserver_safe started.
2020-03-25 11:01:49 Logitech Media Server died. Restarting.
2020-03-25 11:01:54 Logitech Media Server died. Restarting.
I'm
Don't run squeezeboxserver_safe, that shell script only spawns the
squeezebox server binary and checks for its health:
- it requires an environment that might not be available (shell env or
init.d, I don't remember)
- trying to restart inside the container is the wrong idea. Docker (or
compose)
Thanks for that.
Now running this startup script:
Code:
#!/bin/sh
/usr/sbin/squeezeboxserver --user squeezeboxserver --prefsdir
/var/lib/squeezeboxserver/prefs --logdir /var/log/squeezeboxserver/ --cachedir
/var/lib/squeezeboxserver/cache --charset=utf8 --debug
I think I've seen this kind of thing but I can't recall anything
clearly.
Would you try running your image w/ something like "docker run -ti --rm
--entrypoint /bin/bash image-name" to get a shell and keyboard, and then
manually run the command? Perhaps you could see what's wrong more easily
as
That's exactly what I've done. I've overridden the entrypoint in my
docker-compose file to just be 'bash', and then used docker-exec to
connect to the container and run the script manually.
That's the output I posted.
Andy
Ah yes, I missed the 1st line, sorry.
Mhh.
https://forums.slimdevices.com/showthread.php?106864-Can-t-connect-to-LMS-after-reboot/page3
Rights ok on directories, log file exists?
2 SB 3 1 PCP 6 Libratone Loop, Zipp, Zipp Mini iPeng (iPhone +
iPad) LMS 7.9 (linux) with plugins: CD
Looks like the log files are owned by root:root, and permissions are
644. Could this be because they're being created by the server process
before it then 'becomes' the squeezeboxserver user, and then is unable
to write?
Code:
did you try to drop the '/' from the end of --logdir
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Paul Webster wrote:
> I tried to connect my pCP 6 to the nearby Amazon Echo via Bluetooth.
> It was connected with pCP 5 and the Echo was driven by Squeezelite.
>
> Problem now is that pCP 6 is not able to keep a connection with the
> Echo.
>
> I see this in the logs when I try to initiate a
34 matches
Mail list logo
