Moonlight - No mapping available for /dev/input/event2 (030000005e040000a102000007010000)

[backstander]

I actually figured it out before I could submit this request but I will show you how I fixed it!

Iwan Timmer has made changes to the controller mapping for the most recent version of Moonlight:

"Main reason to switch to the SDL gamecontrollerdb.txt format is to be able to make gamepads work out-of-the-box. Unless someone use a custom controller configuration using xboxdrv. Beside SDL2, the format is also used by Gnome Games, Godot Engine. And therefore mappings from them...can easily be reused."

Source:
https://github.com/irtimmer/moonlight-embedded/issues/514#issuecomment-310039899

Instead of having a .map file for each unique controller (which meant having to add separate .sh launching files for each unique controller) by using the -mapping /path/to/controller.map options, now there is one file with all the various controller mappings located at /usr/share/moonlight/gamecontrollerdb.txt

If you want to update your gamecontrollerdb.txt with the newest revision, just type these two commands:

sudo cp /usr/share/moonlight/gamecontrollerdb.txt /usr/share/moonlight/gamecontrollerdb.txt.bak

sudo wget -O /usr/share/moonlight/gamecontrollerdb.txt https://raw.githubusercontent.com/irtimmer/moonlight-embedded/master/gamecontrollerdb.txt

The 1st command makes a backup (just in case!) and the 2nd command replaces gamecontrollerdb.txt with the newest version.

You can now remove any -mapping /blah/blah/blah.map from your Moonlight/Steam .sh files.

But after doing all this I was still receiving the No mapping available for /dev/input/event2 (030000005e040000a102000007010000) error. After searching through the gamecontrollerdb.txt file, I couldn't find 030000005e040000a102000007010000 (which I guess is kind of an ID or hash that represents my Wireless Xbox 360 controller).

I ran jstest /dev/input/js0to figure out what buttons did what and here are my findings!

Open up gamecontrollerdb.txt for editing (I used nano):

sudo nano /usr/share/moonlight/gamecontrollerdb.txt

If you're using the Xpad driver with a the same wireless Xbox 360 controller I'm using, then you'll want to add:

030000005e040000a102000007010000,X360 Wireless Controller,a:b0,b:b1,x:b2,y:b3,leftshoulder:b4,rightshoulder:b5,lefttrigger:b6,righttrigger:b7,back:b8,start:b9,guide:b10,leftstick:b11,rightstick:b12,dpleft:b13,dpright:b14,dpup:b15,dpdown:b16,leftx:a0,lefty:a1,rightx:a2,righty:a3,platform:Linux,

And if you're using the Xboxdrv drive with same wireless Xbox 360 controller (untested):

030000005e040000a102000007010000,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b14,dpleft:b11,dpright:b12,dpup:b13,guide:b8,leftshoulder:b4,leftstick:b9,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,platform:Linux,

I am hoping that others will be able to get their controllers working that may not work out-of-the-box and I'm sure we could submit Pull Requests to this address to get them added:
https://github.com/irtimmer/moonlight-embedded/blob/master/gamecontrollerdb.txt

[beankid]

I've only recently updated my system to the new moonlight-embedded package yet I am having the same error, different controller ID but the same error. I've followed the steps you outlined and cleared the controller configuration but still no dice. Each time I launch moonlight, it finds the controller, yet never loads the correct configuration. Only falls back to the default configuration at the top, which isn't correct. Any help?