Updated today and have the same issue.

sorry, but did you hit the Fn button with F4, because MS keyboard works like that.

Thank you very much caver01.

Pressing the "fn"+ "caps lock" is sufficient for me currently.
But maybe if one day I begin to be fed up with this, I know what to search for ;)

I have simply deleted the /dev/input/js* and /dev/input/event* link so that the system does not use it as Joypad.
I have made a little script that delets the links and put it into rc.local so the links get deleted every boot. Somehow a udevrule did not work for me.

This issue can be closed

to answer my own post, the dev of libretro-cap32 answered me on github. It's a simple matter of switching the virtual keyboard to gamepad emulation by using the SELECT key. Then you can use the virtual keyboard with the mouse. YEAH !

@dogeymon The default layout for the keyboad is GB, that's where the pound sign comes from. Edit the /etc/default/keyboard file and change the layout to us:

XKBMODEL="pc105" XKBLAYOUT="us" XKBVARIANT="" XKBOPTIONS=""

then reboot the system and try again.

@morrisav10
Yeah Its Nice this is the attachment https://www.xbox.com/en-US/xbox-one/accessories/communications/chatpad

The chatlad fits on 360/one controllers

I think the OP would like to choose some kind of low power sleep mode in ES to "shutdown" the Pi, but not completely turn it off. And then OP wants to be able to wake up the Pi simply by pressing a key on an attached keyboard, just like how you wake up a Windows computer or Mac.

I don't understand why a special hardware should be needed, but I am also confused why there seems to be no simple software option to enable such behavior? In fact such behavior should be the default to safe power with sleep, and allow easy wake-up by pressing space or any key or clicking the mouse, just like is has been on any PC or Laptop for a decade, and such is the default on pretty much all set-top boxes like Roku, and consoles like PS4 and Xbox One consoles, too. However, on those, it is a button on the remote or wireless controller that wakes up the device, not an attached keyboard. Using an attached keyboard should be simpler, since Bluetooth is not required to be kept on.

EDIT: Apparently, in order to save cost as much as possible, the Raspberry Pi board has no power management whatsoever, e.g. no sleep/suspend modes, no wake-up, nothing compared to what is found in most other modern hardware. There are a few add-on boards that provide such power management, such as sleepy-pi or witty-pi, but bottom line, there seems to be no easy way to do what the OP requested.

I have had some luck and some disappointment with various BT keyboards working properly with RetroPie. The first two I bought worked perfectly, so I ordered a couple more from the same vendor, while they did pair successfully, the function keys wouldn't work. I noticed even through they looked identical, the model numbers were different, so I requested the model numbers that I knew specifically worked. Long story short and 8 keyboards later, they were unable to deliver any fully functioning keyboards... so I widened the net and ordered eight more from various vendors, four of which provided me with compatible keyboards. Here they are on Amazon:

$14 CyberTech Bluetooth Ultra-Thin
$15 Fintie Ultra Slim Wireless Bluetooth
$20 Anker Bluetooth Ultra-Slim
$18 Jelly Comb Universal Backlit

Clearly most of these are the same models from China with company branding, but it seems the programming or on-board drivers are slightly different per company too.

Also, if you're having difficulty pairing your keyboards, here is a little CNET article on how to setup bluetooth directly in Linux (vs. the RetroPie setup GUI). The GUI method was spotty for me but the Linux method worked 100% of the time! (note: it was sometimes necessary to slip a "trust xx:xx:xx:xx:xx:xx" between the "pair" and "connect" commands)

My work/fail test was to be in EmulationStation and hit the F4 key. If it doesn't exit EmulationStation it was a fail. (some keyboards required a two key press of FN and F4). If you are already in the Linux shell you can type "showkey -a" and then press F4, compare the result with a USB wired keyboard press of F4. If they are not the same, fail the keyboard.

@cian Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first (and start a new topic please).

@arakash hotkeys/combos only work for player 1.

There has been some discussion on controller localisation settings for ES where you could choose what help icons you want per your controller but that also has similar issues with mappings/integration with libretro's configs

@geometrafilini open msx is not a retroarch emulator. If you want it to work as easy as other retroarch emulators, download lr-bluemsx. To use the keyboard you might have to add

input_player2_libretro_device = 2

to the msx retroarch.cfg

@golaat Yes and no. Since some of the emulators run inside retroarch, you are somewhat tied to that environment, but with lr-mame2003 you can actually work around it. You COULD go in and set all of your player 1 inputs to “nul” (don’t use curly quotes like I did here). This is unique for this version of mame because it still “listens” to RAW keyboard inputs. You then have to go into MAME and map keys using the ALL games menu as opposed to just THIS GAME and you will have a nice clean input setup which is what I already proposed above.

However, this doesn’t work for other libretro cores. Still, I

it's working after reinstallation retropie.