Just a quick thought as I personally find the layout of evdev terminally confusing but given evdev likes to have lots and lots of events numbers for every device it does seem likely that your keyboard / mouse wouldn't be event1/event2 as something else would beat them to it. Do you have a /dev/input/by-id directory as I do on my debian/arch systems? I find it gives readable names that don't change randomly all the time and are links to the concisely . They are still confusing though.
ls -l /dev/input/by-id/
lrwxrwxrwx 1 root root 9 Apr 10 20:29 usb-Areson_USB_Device-event-mouse -> ../event3
lrwxrwxrwx 1 root root 9 Apr 10 20:29 usb-Areson_USB_Device-if01-event-kbd -> ../event4
lrwxrwxrwx 1 root root 9 Apr 10 20:29 usb-Areson_USB_Device-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 Apr 11 00:54 usb-Logitech_USB_Keyboard-event-if01 -> ../event7
lrwxrwxrwx 1 root root 9 Apr 11 00:54 usb-Logitech_USB_Keyboard-event-kbd -> ../event6
In this case event4 is particularly confusing as it is a mouse in "media keys," clothing.
To double check type cat /proc/bus/input/devices and look for the Handlers lines as these should match the above. It should say things like kbd event7 (and it matches) and you can pick up the device names/sysfs fields from the structure and prod them further to be sure
It's 1:30 am ... so if you get stuck send me a direct mail with
ls -l /dev/input/by-id
xinput list --long
And I'll tell you precisely about why I don't know what the hell is going on. I have done it before ... just seemed a long tim ago. It's really not that bad either .. I'm pretty sure it just got tidied up recently hence my personal trauma as nothing tht used to work does anymore.