[MaestroDD]

Hi there, just wanted to add my two cents. I have it working on my harmony remote... for the most part. But, it seems to act as if it has two different modes, which I'll call "universal" and "regular". Hitting a universal button while in regular mode causes that specific button to fail (the menu_hold is not recognized but it's followup commands are) but it will then put it in "universal" mode. While in universal mode, universal commands will work but if I hit a non universal button (say, the center play button), that button will not work but then put it back in "regular" mode.
[...]
I guess my first question would be, what that specific "Unknown button for cookie string" error is. Searching through these forums, I found a cookie string error starting with 280_ but not one for this 22_ code. Any ideas or clues? This is really not a deal breaker or anything, I'm just trying to make it as "wife proof" as I can, because she does not share my enjoyment of bleeding edge technologies (as well as the beta-level tweaking that goes with it)

I'm not sure what causes this but as a workaround, you could add another button press at the end of each sequence, ofc with a pause >500ms in between. Say you want a macro with MENU_H, Play,Play, you program this into you Harmony but add another Play press after a timeframe > 500ms. From what I understand, this should bring your Hamony back to "regular" mode. Maybe others with a working Harmony setup can comment?

About the "Unknown button for cookie string":
We're extracting raw ir cookies when in MultiFinder mode and if the remote sends something which isn't understood by xbmchelper it logs those errors. This happens e.g. with paired as well as learned remotes.
With Launcher 3.0beta, Universal-Mode is fixed inside, so no need for external xbmchelper. In that case we rely on IR-cookie decoding from the ATV, and this, ofc, supports learned remotes etc.

One last thing that might be purely coincidental but probably worth mentioning. I found that putting my Keymap.xml in the URL listed earlier in this thread (~/Library/Application Support/XBMC/userdata/) did not seem to work. Instead, I modified the existing Keymap.xml in /Applications/XBMC.app/Contents/Resources/XBMC/system/Keymap.xml and added the universal commands found in the atv-xbmc-launcher wiki. I was able to verify it was reading the Keymap.xml from there because I temporarily changed my up arrow to go down instead, and it behaved as expected.

xbmc.log should mention if Keymap.xml gets picked up or not.