@cnoto For the ONOFFSHIM I used the default setup, proposed by Pimoroni. For the complete powercut you either need a systemd file or you set a dtoverlay to /boot/config.txt

You can take a look here to this tutorial

@rtarroyo BTW

The internal switch is turned on to safe shutdown and im running the latest version of Retropie, installed it today

@cnoto Cool! Glad it worked for you. It's always nice when you can keep plugging away at those pesky little buggers.

@Dinsdale ah got it! Well glad it works now sounds like a really neat set up. On the other hand I would have never thought to use an Alexa powered outlet so I guess teamwork!

@robertybob Check out @cyperghost's shutdown script - https://retropie.org.uk/forum/topic/17415/ - it supports multiple switches and can be adapted to work like you want w.r.t the reset switch.

@mitu @cyperghost

I sent an e-mail to RetroFlag the other day describing the issue and from looking at the photo of the wires I sent, they said the colored wires were in the wrong position. They apologized then gave some directions on how to take the wires out and what the proper color order is.

I tried taking them out of the black plug but it seemed a bit of a hassle. Fortunately a replacement case arrived from Amazon today and the colored wires in the replacement case are in the correct position. I rebuilt my RetroPie and the shutdown and reset worked right away :). Thanks again for the help.

tldr: Original case wires were messed up, replacement worked.

I am having the exact same issue with my Kintaro Kuma 9000. I'm using a retropie image that I downloaded from arcade punks. I had originally used another image which did not have these power issues and booted up fine with the power buttons and showed the red LED light. But then I switched to another image and now have this exact same problem. It starts up and then right when the splash screen ends, it shuts down. Did you ever get a fix for this issue?

@mitu said in Pi overheating and scripts not working:

@MisterMints Most likely something hardware, try to return it and get another.

Wish it was that simple! My Pi3 is over a year old and was a gift - I treated myself to a new 3B+ and was going to donate the broken one (obviously before it was broken!) to a retro gaming present for my little brother.

At least now he gets the same present but with a brand new 3B+ instead

@de_jean125 Something like that, yes. :)

My first guess was that it was for your kid(s), by the way.

You could even let it get nastier … "Stop or I'll hack into your bank account and send all of your money to homes for retired game programmers!"

@mitu
Ho right, 3rd party! Yes that sound fair.
Ok thanks!

@sano Bingo!, just never saw the runtime error before. I went into raspi-config and set it to autologin to console and it boots normally into Retropie, thanks!

I had the same issues using my Mausberry switch I had the blue and white cable mixed up.

On resetting games with the reset button I'm getting the following error:
/home/pi/RetroPie/scripts/multi_switch.sh: line 63: kill: (####) - No Such Process

Where #### is the process number.

It also producses the following message on closing the process:
Killed

As it looks messy having persistant messages like these show between screens is there a clean way to hide them?

I don't want to completely prevent error messages showing as sometimes I do screw up so just these ones specifically. If it's all or nothing though I'll just have to accept that.

@drakaen391 About your posted codings.... Does the wait command works in your case? @mediamogul and his while-loop by monitoring PID status is imho better ...

wait can only be used on child processes out of the own subshell

@psb The poster hasn't been on this forum for 1 year and bumping old topics is bad forum etiquette. If you have a question, then open a new topic and ask away - don't re-open years old topics.

OK bought everything and built it and it works great. 2tb harddrive would not fit but the 1 tb one does : )
whats words without pics. so here ya go.
0_1523061807508_image9.jpg

0_1523061725394_image10.jpg

0_1523062119332_image5.jpg

0_1523062151644_image3.jpg

0_1523062182808_image4.jpg

0_1523062209688_image6.jpg

0_1523062237514_image8.jpg

deleted case ethernet port,case door hinges came out for room, glued closed. had to put dedicated power to the hd to spin right so extra usb port grafted to the drives power wires while data wires go to pie. runs cool enough 50 degrees-ish so far. case closes tighter than pics when screwed together. just took some quick snaps to share. think it turned out pretty good.

@cyperghost ok I figured it out :)
it's a little bit of a bug but totally fixable.

ES uses both gamelist.xml found at /opt/retropie/configs/all/emulationstation/gamelists/"console"/ and /home/pi/RetroPie/roms/"console"/

so if there's no gamelist.xml in the console folder under roms, it will use the one found in configs. for some reason it doesn't remove entries, only adds them.

it will also not untag favorites if you DO have a gamelist.xml in your roms but DON'T have an entry in your gamelist.xml for the tagged favorite game.

Best word of advice: scrape like you've never scraped before lol

@matalog I'm not very firm in python.
But take a look to this link
https://raw.githubusercontent.com/LowPowerLab/ATX-Raspi/master/shutdownchecksetup.sh

and to this link
https://lowpowerlab.com/guide/atxraspi/assembly-install/

shows how to use a timer to differ button event between shutdown and reboot in accordance of button press time. I think that is your demand....