There were indeed no events when I tested with evtest.
I completely removed the keyboard again, rebooted and started Pixel. I again paired the keyboard, and made sure it worked in Pixel. Then I rebooted into ES again, again no keyboard..... some kind of weird inspiration made me go to the Retropie Config (you know, where the setup.sh is started) and, much to my surprise, I found that after a few button pushes the keyboard started working! I have no idea what went on and why it worked, because apart from opening setup I did nothing differently from the first time. After leaving the config I started evtest again (via the remote console) and actually this time around the events were showing up! The keyboard actually started to work!
Soooo happy now, as after adding the proper event source to the moonlight config I actually have full keyboard support there as well!!!
Thank you again for your help and patience @mitu !
@zacho95 Also another thing you can try is powering off the console, pulling the power cord/power supply, press the power button on the Xbone a couple of times to drain it, and then reboot and retry.
I used to get paid to do this shit for Microsoft :)
When you connect a controller to an XBONE via wired or wireless, it saves the ID of the console in the controller's memory, so if it is not connecting to it after all of these steps, it is probably the wireless functionality on the controller that is dead (in all my years of working we have not had the wireless adapter on the console side break). I have seen a lot of those original controllers break over the years :)
Also if you have a friend with an XBONE, try to pair it to that console
The PS3 controller can only be synced to one device at a time. It remembers the Mac address of the device it's synced to. Nice thing is once synced to a pi, all you have to do is plug it in via USB on the pi, press the ps button and then unplug. To go back to PS3, plug the USB into the PS3, press the ps button then unplug.