Cool. BTW, let me ask -- are you just exposing a "clicked()" interface to the buttons, or are "pressed()" and "released()" also available? (I guess I should take a look for myself... ) Many CIR remotes have special behaviors when a button is held down (particularly useful for things like volume controls).

For least bloat, you'd probably do best by avoiding both LIRC and Pierogi. The LIRC server has been designed as a one-size-fits-all mechanism, trying to support every possible combination of on and off pulses in every protocol in one single massive code path. Pierogi goes the other way, creating a custom method for each CIR protocol, so the hardware driver is much simpler (and far more efficient). On the other hand, I'm also trying to store every keyset of every device in the entire known universe. I guess maybe something like grabbing the Pierogi protocol engine and leaving the keyset data behind might make the most sense for a MultiMote backend...

Very cool. I've been taking a look at the bluetooth stuff myself (particularly as many devices are moving to bluetooth for remote purposes, and I'd like to get that into Pierogi as well), but I haven't gotten very far with it...