@All,
Joshua is completely right and I have made some small changes to the library to make them consistent with the keynames used by Corona. However, I’m sticking with the native key codes because, I wanted to do something a little different from the normal onKey() processing.
- My lib extends the default onKey() processing and doesn’t override or replace it.
- My lib makes a small change from onKey(). Instead of the phases: “up” and “down”, I’ve remapped to the “began” and “ended”. I figured folks would be used to these as they are two of the the standard ‘touch’ phases.
- My lib only listens for these FireTV keys: menu, back, mediaFastForward, mediaRewind, mediaPlayPause, left, right, up, down, select
- My lib remaps these keys on Windows and OS X machines to produce FireTV input (like) events to enable FireTV app testing in the simulator:
- m - menu
- b - back
- f - mediaFastForward
- r - mediaRewind
- p - mediaPlayPause
- left - left
- right - right
- up - up
- down - down
- s - select
Note: If the above seems at all defensive, please don’t think of it that way. It’s always hard to read tone in forums and what-not. I am simply elaborating on the reasoning and differences between a standard onKey() approach vs. mine.
Actually, Joshua guessed correctly. OS X was the trouble maker for easy mapping and I borrowed from an old remapping lib of mine (RGEasyKeys) to make this lib. Just goes to show the Corona staff are smart and can often guess why we developers do weird things. 
On a last note, in addition to the keyName corrections,I’ve added a Composer Framework example that uses the Fire TV liband touch inputs to navigate.
https://www.youtube.com/watch?v=I7zmYTqNULU&feature=youtu.be&hd=1
(First half of video is ‘verify’ app, second half is composer framework with Fire TV inputs, tested in simulator.)
Cheers!