About the RetroFlag cases! Surprise surprise.... They can cut off power!

[diablo]

I am so close to having this working but I am missing something that to you guys is probably glaringly obvious.

First: install raspi-gpio with sudo apt install raspi-gpio (done, all seemed fine there)

Second: install shutdown_fan script as descriped in point 6 (again I think thats ok)
Today (03/05/18) I got a NESPi+ case so I was able to elaborate the issue. Thanks to @gollumer for your patince!

Set NESPi+ case switch to safe shutdown ON. (done)
Login with SSH
Type in commands mkdir /home/pi/RetroPie/scripts && cd /home/pi/RetroPie/scripts (again seemed to go ok)

This is where I think I have drifted off target.

DL: wget https://raw.githubusercontent.com/crcerror/ES-generic-shutdown/master/multi_switch.sh && chmod +x multi_switch.sh ( i thought I did it right, but not sure now)

3.1 If there is an older version please remove this one with rm multi_switch.sh (there is definitely a multi_switch file there somewhere, but I cant see it. But if i run with the above dl again its gets renamed to .1/.2 etc. So its there. But if i ssh in and go to the scripts directory I cant see anything there.)
3.2 Otherwise the current downloaded version will get a .sh.1 filename! (Yep, thats happening alright)

Now edit ES autostart with nano /opt/retropie/configs/all/autostart.sh and add script to like .... (Not a 100 percent sure what you meant there, did you mean to say look like?)
Anyway, after edit my autostart looks exactly like this now

/home/pi/RetroPie/scripts/multi_switch.sh --nespi+ &
emulationstatio #auto

(In theory, could I have stopped now, if it had gone right for me, and come back to do the fan aspect later? I only ask out of interest, trying go learn on the fly here)

Install fan_shutdown script: cd /lib/systemd/system-shutdown/ && sudo wget https://raw.githubusercontent.com/crcerror/ES-generic-shutdown/master/shutdown_fan && sudo chmod +x shutdown_fan
6.1 The shutdown_fan is setted to GPIO4 as standard
6.2 Therefore you might edit with sudo nano /lib/systemd/system-shutdown/shutdown_fan (again, if I had stayed with the way the nespi+ default setup, would I even need to to this bit?)

i think my whole issue is the 'not being able to see/access the script file. Something the pi is sharing with me as it cant see it either. The fact that the download adds another version kind of suggests that the original file is there. During my failed attempts to work things out I have seen it deny access to those renamed download files (.2 and .3 before realising I was chasing my tail)

I really like the idea of having things set up as you have done them. But I am stuck now. After hours of trying I am at the point where I either asked for help, or just gave up and installed the default 'nespi+' script.

I did read in a follow up, that the question of automatic or executable came into play. Thats a definite level above my capabilities at this moment as I jave no idea which it should be, or how to even change it if its wrong.

Sorry for asking, but I am totally stuck now and my fumbling around is liable to do more damage than good.

[cyperghost]

@diablo No problem.... Maybe I should provide an installer later. That makes these things automatic.

Good: raspi-gpio is needed

What do you mean with: "there is definitely a multi_switch file there somewhere, but I cant see it". Do you use WINSCP and it's command interface? If yes you should press the reload button, and then the files will appear. But all in all prefer the use of putty or kitty. But step by step

If you type in: mkdir /home/pi/RetroPie/scripts && cd /home/pi/RetroPie/scripts are folders created and are you in this folder with command prompt?

Now next: if you type in wget https://raw.githubusercontent.com/crcerror/ES-generic-shutdown/master/multi_switch.sh && chmod +x multi_switch.sh after that you can use ls command to list the directory. There the file should appear.

Yes... the autostart is also correct. So it should be a proper setup.

The GPIO bit to shutoff the fan in the second script needs no change by default! It's just a hint if someone want to rewire the NESPi enclosure.

What is the output of: ls /home/pi/RetroPie/scripts
Or can you even execute the multi_switch.sh itself?
So what is the output of: /home/pi/RetroPie/scripts/multi_switch.sh

To make something executable means to use chmod +x command. The script is simple a text file and needs to be made excutable, so it can be called by the command line. But you will see it if you execute the script via command line. That's it :)

BTW: Are other scripts running? Maybe the original from retroflag? You should disable them by removing the call from rc.local therefore sudo nano /etc/rc.localand remove the sudo python ..... entry or set a # before to comment it out.

[cloudlink]

Is there a line I can put into a shell script that will restart EmulationStation, saving metadata?

[diablo]

@cyperghost am not at home as I write this so not in range of my gear. But I wanted to say thank you for the response asap. I will get into it later. All looks logical and easy to follow (at this stage thats needed). A couple of things i can confirm are that I am using putty, and I didnt install any retroflag stuff. the directories are there. Its just the multiswitch that seemed to be awol. Again thanks, will check it out asap.

[cyperghost]

@cloudlink yes multi_switch.sh --es-restart
Therefore I wrote the script...
For more help type multi_switch.sh --help

@diablo You are welcome

[diablo]

cyperghost, you are a legend. When I first asked the question I had a few doubts about how I had done things. Something had happened with mine that kicked it off track though. I should have added that I am using a pi 3b. Anyway, following your instructions (to the letter), showed that the file structure was correct, though no multiswitch file (sorry for spelling it wrong, but i need to write this fast as i am needed elsewhere in twenty mins). Running the wget https bit gave me a newly created multiswitch.1 file. So it was definitely saving it.

Ls of the scripts folder still showed nothing there.

Backtracking through the hierarchy though I discovered both multiswitch and its newly created ms.1 version were both in the 'home' folder. Not where they should have been obviously.

A quick google on how to move a file within putty (told you i was new to all this) and i moved ms to the scripts folder.

Ls confirmed the move was good.

Rechecked the ES autostart details, all looked good.

Restarted the pi, finally seeing a flicker from the led then eventually lit solid.with ES fully loaded. Tried a game, pressed reset and it jumped back to game selection. Hit the power button and a second or three later it shut down. A number of test shutdowns and resets later and Basically, its working perfectly now (albeit without a fan as the one I had fitted sounds like a 747 taking off, so no idea about fan script working or not, though I have no reason to think it wont now the rest is ok.

So again, cyperghost, thank you. Your 'fault finding' was used, albeit in a different manner, but its now working as intended thanks to your input. Greatly appreciated.

I know a lot of people think the nespi has been done to death, but with the + sat next to my c64 and snes minis, and knowing its abilities, the pi is awesome to me now. It just looks'right'.

[cloudlink]

@cyperghost said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

multi_switch.sh --es-restart

It worked!
Thank you so much!

[OhOhOne]

@cyperghost said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

@ilackiq Yes safe shutdown is possible.
With the bash script posted here ... you have all the features you mentioned. Power on power off, reset ends running emulators, reset inside emulationstation restarts emulationstation only (NO REBOOT!). All with safe shutdown!
But then you have to disable uninstall your python script!

But you can also use the modified python script that I already posted to you, there you need just to follow instructions and do not need to disable the python script, you exchange it with the one I gave you link. This provides also safe shutdown of course. With this script you just restart emulationstation with reset button... feel free to extend this, if you want - that's also easily possible.

cyperhost, I tried following your directions for replacing the stock RetroFlag script with your python script (as I had already installed the stock one), but it's not working for me, the red light just blinks indefinitely and never turns off. What did I do wrong? How can I disable or uninstall the python script so I can switch you your bash script and use that instead, since the reset button seems so much more useful on your bash script?

Thanks.

[cyperghost]

@OhOhOne
Did you installed the original script by retroflag?
Can you check if multi_switch.sh is executable and is located into cd /opt/RetroFlag folder?
Is the python script exchanged by the one given in the thread?

If you decide to install the bash script then you have to remove the installed python script first. Type sudo nano /etc/rc.local and remove or comment with # the line with the python code.

Btw: You can easily extend the python with an el-if branch to just restart emulators if they are running.... I just give an example how script can be invoked into other languages. So the bash and the python script function equally.

[OhOhOne]

@cyperghost
I double checked everything and its still not working.
I installed the original script by retroflag. It was working fine, but I wanted something that would save metadata, so I followed your directions posted in the other thread for replacing the original script with your own python scripts. But ever since then the power button just blinks red when I push it to off, and the reset switch doesn't do anything at all. I double checked and multi_switch.sh is there in /opt/RetroFlag and is executable, and I deleted the original python script and replaced it with yours (again, just to be sure). But its still not working.

Am I missing something? Did I skip a step?

EDIT: this is what I get when I type sudo nano rc.local:
GNU nano 2.2.6 File: rc.local

By default this script does nothing.

Print the IP address

_IP=$(hostname -I) || true
if [ "$_IP" ]; then
printf "My IP address is %s\n" "$_IP"
fi

/etc/switch.sh &
/etc/switch.sh &
sudo python3 /opt/RetroFlag/SafeShutdown.py &
exit 0

[cyperghost]

@ohohone Why double /etc/switch.sh? Try to remove this first.
You can also remove the sudo from the python3 call. etc.local is already root

[OhOhOne]

@cyperghost
Okay, I made those changes to rc.local but there's no change, it still doesn't work. :(

[cyperghost]

@ohohone Sorry. I made just a quick try with the python code and it worked fine in my case. Maybe you can add a "print output" line to see if there is any value returned. But you can still use the bash script itself.Use the newest version. You can add it to rc.local or to autostart.sh with path/to/script/multi_switch --nespi+ &

Install raspi-gpio with sudo apt install raspi-gpio before. That should do the job.

[PWN3D_]

Hi,
I think I got it all right, the reset button work just as it should and reset to the ES loading screen, but the power button doesn't work at all and the red led is still on when I press it.
Well i'm a begginer so there is probably something I'm doing wrong.

I also notice that with the safeshutdown from Retroflag ( wget -O - "https://raw.githubusercontent.com/RetroFlag/retroflag-picase/master/install.sh" | sudo bash ), if I want to turn off the pi, i have to switch the power button to off and then press reset. Switching th power button to off doesn't do anything on his own.

So yep, i'm lost ... :/

[cyperghost]

@pwn3d_ said in About the NESPi+ case! Surprise surprise.... It can cut off power!:

Hi,
I think I got it all right, the reset button work just as it should and reset to the ES loading screen, but the power button doesn't work at all and the red led is still on when I press it.
Well i'm a begginer so there is probably something I'm doing wrong.

I also notice that with the safeshutdown from Retroflag ( wget -O - "https://raw.githubusercontent.com/RetroFlag/retroflag-picase/master/install.sh" | sudo bash ), if I want to turn off the pi, i have to switch the power button to off and then press reset. Switching th power button to off doesn't do anything on his own.

So yep, i'm lost ... :/

Please install the "shutdown_fan" script... type:
cd /lib/systemd/system-shutdown/ && sudo wget https://raw.githubusercontent.com/crcerror/ES-generic-shutdown/master/shutdown_fan && sudo chmod +x shutdown_fan

This will cut power if you press power button.

The method the retroflag script provides works in most cases but it's a simple "killall" and it will fail if there is a emulator running in background.
But I'm a bit confused.... Reset works... Power on/off not? Did you set the NESPi-case switch to "ON"?

Please remove the retroflag script by editing sudo nano /etc/rc.local and remove the python entry.

[edmaul69]

@cyperghost im really confused. Retroflag says that their script does safe shutdown and safe reset. And to me it appears to be doing just that. How is this better?

[cyperghost]

@edmaul69 They do a safe shutdown by killing every instance of emulationstation binary but this method may fail if there is a emulator running in background. These may be a edge example but it's an improper way to terminate emulation station and is not clean way to save metadata.

Furthermore.... the reset button. It's just a waste of option with the original script as it just acts as a system reboot. The multi_switch script just resets the emulator (if there is one is running) and you turn back to ES main menu, or you restart just ES without performing a reboot (usefull if you changed metadata and want to save it, too).

All in all it doesn't matter which way you choose. Imho I would NOT use the original script but would stick to python and modify the original script like I've done here: Get text output from bash into you python script

In the end you decide ... I created the script to cover a lot of usecases and to make work to install switch to a Pie a bit more easier. Furthermore I learned a lot about handling command line parameters (used a uncommon method without shifting every single parameter).

In short why I don't rely on the retroflag script:

• Fixed shutdown timer (5 seconds in every case)
• The metadata may break in edge cases
• Reset button is useless (imho)
• (not related to the script itself) They change /boot/command to set UART for LED output
• The python libary (GPIOzero) is a real heavyweight (but very comfortable I must agree)
• I wanted to do something in bash ... as long as @meleu don't fixed the ES shutdown service (therefore I installed the --es-systemd parameter)

So I hope you are not confused anymore ;)

[PWN3D_]

@cyperghost

Ok, I've instaled the shutdown_fan script, but it appears as shutdown_fan.sh1 , so I guess it was already there.

Sorry for the confusion about the Power switch , I'll try to be clear :
(The Nespi case switch is turned to ON)

-With the retroflag script, the Power on/off only works to turn on the pi. When I press the Power button to "off", it doesn't do anything. If I want to trun off the pi, i also have to press the reset button, see the retroflag script rolling to the end until it finally turn off the pi.

-With your script, it is the story, the Power off doesn't do anything but as the reset button only restart ES, I can't turn off the pi.

So yes, the Reset button work perfectly, the Power button works only in one way, when I have to turn On the pi.

PS: Today I have tested with a fresh sd card without the retroflag script, but this ended with the same result unfortunatly

PSS: Also I should mention my what I am working with :
-Nespi Case+
-Raspberry Pi 3 B+
-Kitty for SHH
-San Disk Ultra 16GB

[cyperghost]

@pwn3d_
Then I guess there is something wrong with the case.

-With the retroflag script, the Power on/off only works to turn on the pi. When I press the Power button to "off", it doesn't do anything. If I want to trun off the pi, i also have to press the reset button, see the retroflag script rolling to the end until it finally turn off the pi.

That's very curious. Usually the power button initiates a full power cut off if the GPIO is detected.

-With your script, it is the story, the Power off doesn't do anything but as the reset button only restart ES, I can't turn off the pi.

The reset and and power button are initiated all the same way. As reset works as it should and power does not work. I think I now I understand what may happening. It seems GPIO3 is not proper connected to your PIN header. You may check if it is attached right to the GPIO header. You can also reattach it to a new GPIO if you use ./multi_switch.sh --nespi+ powerbtn=xy & argument.
XY is the GPIO header.....

Because no script works in your setup, the error lies in your case.

[PWN3D_]

@cyperghost I will check all the wires and connectors right now

Also, if the switch in the nespi case is set to "off" the power button work just fine when I turn off the pi, but as you know it just kill the power.