Multi Switch Shutdown Script!

[mrnebu]

@cyperghost hello, i use the nespi+ case, 3b+ but no retropie. the scripts i found so far only work with emulationstation but not if you run console. could you add shutdown now for power and reboot for reset with the led? i tried myself but too much stuff going on in the nespi case for me to finish it within a year and i dont want to mess up your script.

would it be possible to add a function in case shutdown is stuck cause no es is running? it could work down other shutdown / reboot options and your script your get even more universal?

[cyperghost]

@mrnebu said in Multi Switch Shutdown Script!:

would it be possible to add a function in case shutdown is stuck cause no es is running?

That's already possible within the script. For the NESPi+ you see the lines

    # Initiate Shutdown per ES
    es_action --ES-CLOSEEMU
    es_action --ES-POWEROFF

    # If ES isn't running use regular shutoff
sudo poweroff

So indeed if ES is not running it already uses the regular poweroff. On the other hand you can use this script to read status of ES or running emulators and can then decide on your own what to do. So I think it is as flexible as you descripe and will cover a lot of usescases if you know how to use. So I made created a usecase for python here and also RetroFlag mentioned the script.

[Rion]

@Ranma I have been wondering about that to. @mitu Do you have any taughts, ideas?

[mitu]

@Rion said in Multi Switch Shutdown Script!:

taughts

The early bird catches the ... something.

Now, if you want the prompt to disappear and you already modified the .bashrc file, just add as last lines of the file:

export PS1=""
tput civis

and then logout.

[Rion]

@mitu Thank you Mr Bash Shell Wizard!

[Ranma]

@mitu I'll add my love here too. This works! Awesome! Thanks so much for replying.

You always know the answer @mitu

Superstar!

[janderclander14]

I've modified the python script from this post, which calls the Multiswitch script, to add several reset behaviors with generic buttons connected to the GPIO.

Assuming two buttons, the behavior is as follows:

• One button (connected to GPIO 3) acts as shutdown (and power up)
• The other button resets the system. One short press, quits the current emulator or restarts emulationstation. One long press (3 sec) restarts the system.

I attach here the code just in case someone finds it useful (it assumes multi_switch.sh is in /home/pi). You may add this as a python call to /opt/retropie/configs/all/autostart.sh

#!/usr/bin/env python3
from gpiozero import Button, LED
import os 
from signal import pause
import subprocess
import time

powerPin = 3 
resetPin = 2 

resetMinSeconds = 2

#functions that handle button events
def when_pressed():
 output = int(subprocess.check_output(['/home/pi/multi_switch.sh', '--es-pid']))
 
 if output:
     os.system("/home/pi/multi_switch.sh --es-poweroff")
 else:
     os.system("sudo shutdown -h now")

def reboot():
 start_time=time.time()
 diff=0

 while rebootBtn.is_active and (diff < resetMinSeconds):
     now_time=time.time()
     diff=-start_time+now_time

 output = int(subprocess.check_output(['/home/pi/multi_switch.sh', '--es-pid']))
 output_rc = int(subprocess.check_output(['/home/pi/multi_switch.sh', '--rc-pid']))
 if (diff > resetMinSeconds):
     if output:
         os.system("/home/pi/multi_switch.sh --es-reboot")
     else:
         os.system("sudo reboot")
 else:
     if output_rc:
         os.system("/home/pi/multi_switch.sh --closeemu")
     elif output:
         os.system("/home/pi/multi_switch.sh --es-restart")
     else:
         os.system("sudo reboot")
 
btn = Button(powerPin)
rebootBtn = Button(resetPin)
rebootBtn.when_pressed = reboot 
btn.when_pressed = when_pressed
pause()

[cyperghost]

@janderclander14 Hehe ;) Nicely done

[cyperghost]

@janderclander14 I've done some changes to the python script for some other system. To get rid of the pathes I added

#get script directory
scriptDir = os.path.dirname(os.path.realpath(__file__))

So the directory from the python script is catched. Assuming the python and the bash script are stored in the same directory we can use....

os.chdir(scriptDir)
..
..
     elif output:
         os.system("./multi_switch.sh --es-restart")

I was fixed to to /opt/RetroFlag because RetroFlag use as default in the installer and so I use this path to overwrite their script. But congrats you are the first one who activly uses the provided output to create a new shutdown script. Such it was intended to do ;)

[janderclander14]

@cyperghost Certainly, using relative directories is always better. And thanks to you for the script! It just had all the functionalities one would need.

[quicksilver]

@cyperghost Would it possible to adapt your script to work with the new RetroFlag GPi case? It only has a shutdown switch (no reset function). This is the script that is currently supplied by retroflag:

#!/usr/bin/env python3
from gpiozero import Button, LED
import os 
from signal import pause

powerPin = 26 
powerenPin = 27 
hold = 1
power = LED(powerenPin)
power.on()

#functions that handle button events
def when_pressed():
  os.system("sudo killall emulationstation && sleep 5s && sudo shutdown -h now")
  
btn = Button(powerPin, hold_time=hold)
btn.when_pressed = when_pressed
pause()

As you can see they are just using a "sleep" function to handle saving metadata which is not ideal.

[cyperghost]

@quicksilver Yes .... the os.system call has to be changed.

os.system("bash /path/to/multi_switch/multi_switch.sh --es-poweroff")

This will try to close all open emulators and then shutdown the system (after all metadata is saved)

[quicksilver]

@cyperghost That was easy and it works like a charm! Thank you my friend!

[quicksilver]

@cyperghost is there a way to get your script to shutdown if you exit emulation station to the terminal? Or if emulation station crashes or something?

[cyperghost]

@quicksilver said in Multi Switch Shutdown Script!:

is there a way to get your script to shutdown if you exit emulation station to the terminal?

Therefore you can use .bashrc from your home directory.
Just add a poweroff command and if you go to terminal the command will be executed.

Or if emulation station crashes or something?

You would ask for the PID of Emulationstation simply with pidof emulationstation
You will obtain the one from the binary and as long this is alive you know ES is running. If there is a change in the PID or the status of SIGNAL has changed you can assume that there someting happend to ES. To determine if it a user action (Reboot, Shutdown...) you watch for files placed into/tmp dir

The files are

1. /tmp/es-sysrestart for sytem wide reboot
2. /tmp/es-restart for just restarting ES
3. /tmp/es-shutdown for poweroff

So to answer your question if my script can do this .... only for the .bashrc part that is really no rocket science and a sudo poweroff command call would be more effictive.

Be aware to not shoot in your own leg with this!

[WeirdH]

Just wanted to say thanks for this awesome script. After (unsuccessfully) messing around with 'dtoverlay' in config.txt and some years old non-functioning auto-installed stuff, I finally have a single button safe shutdown for ES. Thanks to cyperghost and all involved!

[danick8989]

SuperPi case, i came from your outdated script that's linked on RetroFlag's github and this script doesn't work. When a game is running, i need to flip the reset button several times then it kills retroarch. Same for shutdown, after 2-3secs "Killed" appears on the screen then it shuts down

[cyperghost]

@danick8989 You to explain in a more clear way. The script can be utilzed in two ways.

1. If you use it in pure shell mode then you need to hold the button for one second. The pure bash script uses simple polling to check GPIO state.
2. If you "came" from RetroFlag then you utilize python and this uses interrupts so it recognizes button presses instantly. And the lack of "reaction" is likely a faulty case.

Furthermore: if it terminates retroarch and returns you to ES and it shuts down your Pie why are you assuming it's outdated and does not work?

[danick8989]

@cyperghost I'm not assuming it as outdated, i said i came from your previous revision of the script that's linked on RetroFlag's github page(they didn't update it to this one). And i thought killing retroarch and ES would be discouraged? Like, previously didn't the script send a command to ES for it to close RA properly or something? Also it's not clear to me, how do i use python instead of a bash script, and since it seems to work more seamlessly, why isn't it the default? I rolled back to the old multiswitch script in the meantime, since it still works flawlessly for me aside from exiting from Kodi.

[AndersHP]

Hi, I kind of hijacked another thread regarding Pegasus, but thought I would ask here instead.

I'm not using a RetroFlag unit, but a Kite Circuit Sword from Sudomod.com

I'm unsure if my shutdown script, the cs_shutdown.sh file in /opt/ folder, does something special that can harm the safe-shutdown process if not built into another script, e.g. your Multi Switch Script. My file looks like this (also mentions a shutdown file?):

#!/bin/bash

# Get ES pid
ES_PID=`pidof emulationstation`

if [[ $ES_PID != "" ]] ; then

  echo "ES_PID: $ES_PID"

  # Touch the shutdown file
  touch /tmp/es-shutdown
  chown pi:pi /tmp/es-shutdown

  # Tell ES to terminate
  kill -s SIGTERM $ES_PID

  echo "ES has been asked to shutdown"

else

  echo "Could not find ES PID ($ES_PID)"
  sudo shutdown -h now &

fi

Could I just delete this file, and install your Multi Switch Script with the modifications that @SinisterSpatula mentions? Or would I miss something? How much is this solely for RetroFlag builds?

For instance: The RetroFlag is a Pi Zero right? My Circuit Sword is a CM3+ module (not GPIO based, but basically a RPi 3+).

How can I tell if the script works as intended apart from the screen going black?