Since long ago I had it in my mind getting one remote presenter, but most presenters just had two buttons, and the ones that looked to be valid for my use case, required four and seems that only Rii had similar devices, but I didn’t went for it as it was not a huge need, so I ended up with a mini keyboard I had for Raspberry Pi and some debugging in case I had that need.

But yesterday I found in the recycling IT area, together with several really old computers, a Logitech R400 presentation remote. It has one of those rubber coatings that make it comfortable at hand when it’s new, but it’s sticky once it gets older (had similar experience with other stuff, even umbrellas…)

Some alcohol and a soft cloth helped removing that stickiness, so next step was to test it… plugged the receiver in the USB port, and put two batteries in… and it powered up, bot left and right buttons were working, and the laser pointer. Thing is that the remote has two additional buttons for starting presentation and going to blank screen that didn’t worked.

In a rush, I thought about opening it, thinking that the reason of having it discarded was that one, but nothing strange in the inside, everything was clean, no battery spill, etc, so I reassembled and started looking for information about it.

Using xev I was able to see that the key buttons were received on the computer, the one on the left, provided two different key codes and the one on the right just one, but was not mapped to anything.

After some search, I found this blog post, but a copy-paste didn’t worked… seems that the USB receiver had changed the identifier in the meantime so I had to update to match mines.

First of all, I did checked with lsusb the device ID and Vendor ID, which was 046D and C52D, so I used those values when filling the next two files.

First, I created /etc/udev/hwdb.d/99-logitech-r400.hwdb:

# The lower left button actually emits two
# different scancodes depending on the state of
# the "presentation".
# E.g. one code to start and one to stop.

This file is mapping the two events in the left button to be ‘up’ and the one on the right to be ‘down’… I did this because in the past I used to do some presentations using reveal.js and it was interesting to have those kind of several-level presentations, so that you could go in deep on a topic or move to next one depending on the time available

and /etc/udev/rules.d/99-logitech-r400.rules:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52d", IMPORT{builtin}="hwdb 'keyboard:usb:v046DpC52D'", RUN{builtin}+="keyboard"

The first file, defines the key mappings, so that the actual 4 buttons, work as I wanted, and the second one, ensures that when the device is plugged, the mappings will be loaded… after this, just unplug and replug, and voilà, the presenter was working perfectly… so nice finding, nice recycling via ‘reuse’ and new toy!.

Enjoy! (and if you do, you can Buy Me a Coffee )