@backstander said in Connecting to "Open" Wifi:

When I saw the subject line I thought of you @mediamogul lol

Better this than "Local hoarder crushed to death by avalanche of 'Far Side' calendars. Survived his by 47 cats".

Actually, have a look at this document:
https://retropie.org.uk/docs/Wifi/#hidden-ssid

I think you need to add wpa-scan-ssid 1

Thank you. Answers my question perfectly.

@Bender2k no bt problems here. Do you have a heatsink on your processor? If so it could be causing issues. You could try turning the heatsink 90 degrees so the heatsink fins are facing another direction. The heatsink can act like an antenna and cause issues. Other than that not sure what to tell you to help you.

AlexMurphy is right, check out that link. It very well could be (as the link states) that your power supply isn't providing enough current. Also, if you are running a pi 3, if my memory serves me, wifi is built in. You not giving us any base information to work with makes things difficult to help.

Also, if a better power supply doesn't work, I'm guessing that it's a hardware issue, not software, in which case, this is probably the wrong place to ask.

This seems to be my exact problem. My WiFi is down until I pair (press a + b) my wiimote. As soon as the pairing is complete WiFi connects. I manually configured WiFi setting right out of the gate in /etc/network/interfaces. I then tried setting a static IP in /etc/dhcpcd.conf. Still problem persists.

Any thought on how to resolve this?

@Flavor Yeah I was able to install Raspian Lite with NOOBS and it worked fine. I am building this for a friend and would prefer the RetroPie, so it will just boot into it for him.

@Nelbrenn Is you're router set up to give out dhcp addresses? You can check if the Pi has an ip address through the Retropie menu. It shouldn't start 169 as this is the default address it'll use if it can't get a dhcp.

How fast is your network, and how many people use it?

@nickgash
If there some special characters in your PW then try to hash the password. Read here ... HowTo

@smiler79 It shouldn't be. Is the PSU ~2.5Amps? Is it a hardwired dedicated PSU or a plug and USB cable combo? Some USB cables just cannot transfer enough power as they are designed for phones and tablets that draw a lot less juice.

@millertv79 Happy to report that the EW-7811UN works out of the box for RetroPie, and I used the PINN version of NOOBS with success as well, using a Pi Zero and a passive USB hub.

https://www.amazon.com/Edimax-EW-7811Un-150Mbps-Raspberry-Supports/dp/B003MTTJOY/ref=pd_cp_147_1?_encoding=UTF8&psc=1&refRID=AK8AZ89FD0NDE1BA6WV7

Hello,

I have this same issue and after some research i have determined that it is a problem with how wminput uses the blue-tooth adapter.

Here is an old Ticket for wminput that explains the problem a little better.
http://abstrakraft.org/cwiid/ticket/71

Using -d appears to be what causes the issue.

When I remove the -d flag I can ssh into my raspberry pi however with -d enabled I cannot.

HOWEVER:

By removing -d you cannot add a wiimote after the system has started.

You can connect them when the retropie screen appears by pressing 1 and 2.

I have now narrowed the steps to reproducing this issue on a newly flashed USB and boot Micro SD.

Use this guide to enable wiimote connections. Install the "old format hiscore.dat" in the mame2003 bios as explained in the high scores section here. Enable Root Login over SSH by doing the following: sudo nano /etc/ssh/sshd_config Change PermitRootLogin to "PermitRootLogin yes" Enter "sudo passwd root" then enter in the root password. Restart for changes to take effect

I'm still trying to narrow it down even farther.

So far, finishing with the Wiimote steps has triggered the issue and finishing with the hiscore.dat has triggered the issue (which is really strange).

Edit: Upon narrowing it even further. You don't need to be running off USB for this to occur. All you have to do is follow the wiimote connection guide to cause this issue.

Based on this info I can assume that it's also inconsistent when the issue will first occur after following these steps, as one reboot often wasn't enough to cause it.

I've now narrowed down the cause to the following line in "/home/pi/bin/attachwii.sh".

wminput -d -q -c /home/pi/mywminput 00:1C:BE:F2:D8:64 > /dev/null 2>&1 &

The '&' at the very end of the line is the cause of this. Removing the '&' and then running it does not cause the same issue.

Now the problem seems to be that removing the '&' at the end will not allow your system to finish booting if you have "/home/pi/bin/attachwii.sh" run on startup. Now the question is getting a little more specific as what to fix so I'll create a new post and link it below:

https://retropie.org.uk/forum/topic/7296/wminput-command-with-on-the-end-breaks-wifi