[ANNOUNCE] SqueezeButtonPi - Tool to use buttons and rotary encoders on a RPi

[meq123]

Sorry to seem impatient, but does anyone have any insights?

Especially my question...

1) If/when the POWR function works, does the same button allow restart after a power-down?

I'm in the end stages of making the case & front panel and want to know if I can use a single (simple) switch to do the power down/restart, or if I need to a double-pole type to both use the power GPIO line AND use GPIO3 to restart again?

[paul-]

SqueezebuttonPi only interfaces with the LMS server, or with scripts as you are using.

You can use overlays.....take a look at

https://github.com/raspberrypi/linux...ys/README#L728

PCP also has a shut down monitor too that works with these overlays.

[Jeff07971]

SqueezebuttonPi only interfaces with the LMS server, or with scripts as you are using.

You can use overlays.....take a look at

https://github.com/raspberrypi/linux...ys/README#L728

PCP also has a shut down monitor too that works with these overlays.

I just tried "gpio-shutdown" but it does not shutdown the pi as the readme suggests it only does "Player power off"

the next button push does "Player power on"

Jeff

[paul-]

The shutdown is driven by monitoring the key events.......since pCP does not run systemd. The shutdown monitor extension does this function.

[meq123]

So I have the basic buttons working (though yet to try/test a rotary encoder) except the POWR function doesn't work. Now I can get around it using a one line 'shutdown' script, with the "SCRIPT:" command, but this doesn't seem right. Has the POWR command been depreciated? Or must I be doing something wrong, like missing a step(s)?

After much playing around, I found the reason why the POWR command doesn't work. It's a bug in the sbpd_commands.cfg file... there's an extra double-quote at the end of the POWR cfg line:

#
#   sbpd_commands.cfg  -  Custom commands definition
#
#   <CODE>=<JSON Formatted lms cli command>
#
#       CODE - MUST be a 4 character code, to be reference on command line when defining buttons
#
#       For commands reference the LMS cli documentation, commands are to be JSON formatted.
#
# Default commands
PLAY=["pause"]
VOL-=["button","voldown"]
VOL+=["button","volup"]
PREV=["button","rew"]
NEXT=["button","fwd"]
POWR=["button","power"]"
MIX+=["mixer","volume","+5"]
MIX-=["mixer","volume","-5"]

But having corrected it (and now that it works) I'm not sure what the use of the POWR command really is :-/ I can see that it stops playback and extinguishes the LED on my HifiBerry DAC+, but otherwise, it just acts like a pause/play button.

Does anyone know if this might be a safety-net prior to hard powering-off a self-contained piCorePlayer (with LMS on board)? And anyway, what *IS* the problem with hard powering-off a piCorePlayer with LMS on board?

[paul-]

That is all it does. However you can set squeezelite to act upon it, look at the option.... Power On/Off GPIO (-G) Most use the signal to turn an amp on or off.

[edwin2006]

Hard powering off the pcp with running lms can cause sd card corruption (happened me twice, now running on a Ups)

[meq123]

Hard powering off the pcp with running lms can cause sd card corruption (happened me twice, now running on a Ups)

Ouch. Is this with the music files source on the same device? Or across a network to a NAS (which is my case)?

I assume it was the piCore SDcard that was corrupted?

[Paul Webster]

I expect that it would be due to writing being in progress ... so location of LMS logs likely to have been the issue.

[paul-]

If you are using pCP as your LMS server, then you need to be careful as to how you shut down. If pCP is just a player, then pull the plug is fine.

If you use the shutdown monitor that I have setup for this, then a halt command is issued before dropping power.