HP IR Receiver Options - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: Hardware for XBMC (/forumdisplay.php?fid=112)
+--- Thread: HP IR Receiver Options (/showthread.php?tid=91058)
- boyo - 2011-02-10 20:45
bmcclure937 Wrote:Alright!! My Harmony One finally arrived last evening (after shipping was delayed due to bad weather)
Is LIRCD running? irw wont run without it.
- boyo - 2011-02-10 20:54
Interesting thread as i honestly though i had a dud when i started reading this but hopefully it should be fine (OVU400103/00).
It doesnt respond to irw at all though - any ideas? Ive tried two different harmony one profiles and both yeald nothing.
I tried irrecord and its definitely picking up a signal but when i get to the second part of irrecord where i enter buttons it returns an error of "Something went wrong" WEIRD!
- maxinc - 2011-02-11 10:07
Anyone got one of these receivers in the UK?
- pedr0 - 2011-03-11 14:32
bmcclure937 Wrote:I was hoping someone could graciously point me in the right direction for mapping and configuring my Harmony One with the HP IR receiver.
Hi bmcclure937 - Did you ever figure this out? Please could you share what you learnt.
- bmcclure937 - 2011-03-11 14:35
pedr0 Wrote:Hi bmcclure937 - Did you ever figure this out? Please could you share what you learnt.
I am using OpenELEC and I did figure this out... and I actually started writing a complete guide to the process I took on the OpenELEC forum.
You can check out this guide. Most of the concepts will apply directly to configuring the remote for XBMC.
Let me know what you think! It walks through from the beginning (configuring Harmony Remote using Logitech Software) to the end... but it is still a work in progress and I need to add more information for tweaking remote settings and adding custom actions.
Harmony One Complete Configuration Guide [OpenELEC]
- pedr0 - 2011-03-11 15:42
I actually just saw your horror story in this thread (http://forum.xbmc.org/showthread.php?tid=93849)
I'll check out the guide you've written on OpenElec forums and let you know of any thoughts. However, I'm only just buying the bits and pieces for my HTPC now, so won't have any real life experience for another week or so.
One headache that I've almost definitely got coming my way is with the HP receiver. Can't find one on ebay.co.uk for the OVU400103/00 5188-1667. Even though some are advertised as such, I've contacted the sellers and they invariably say that it's actually the OVU400102/71 that they stock . However, I have found a couple of threads on here that detail how to add that model to the various files used by lirc so that it will work. Fingers crossed .
I'm planning on going with Live rather than Open Elec (getting an ION Zbox so no need for GT430 drivers etc) because I want to add some other applications and functionality and my very limited understanding leads me to believe this will be easier on the Ubuntu-based Live rather than the stripped down OpenElec.
- pedr0 - 2011-03-11 15:50
Just one other quick question. You have on other threads said that you do not recommend adding the Harmony remote as a Keyboard _as well as_ an MCE remote, which would allow key presses to be assigned to buttons within the harmony software. Why do you recommend against this method?
- bmcclure937 - 2011-03-11 16:02
pedr0 Wrote:Just one other quick question. You have on other threads said that you do not recommend adding the Harmony remote as a Keyboard _as well as_ an MCE remote, which would allow key presses to be assigned to buttons within the harmony software. Why do you recommend against this method?
This is unneeded. you do not need to assign keyboard key presses to buttons within the Logitech Harmony Software!
You simply configure the Harmony as an MCE remote. Doing this step will allow your Harmony to perform the core functions for XBMC without any further configuration.
If you desire to change button layout then you can change which commands/functions are mapped to certain buttons from within the Harmony software. You can also add custom buttons by assigning unused commands to buttons on your remote and then modifying the keymap.xml file to assign an action to that remote command. Doing this, you can assign any XBMC function to any button on your remote.
For example, I have a button to mark shows as watched, go straight to the weather screen, toggle subtitles... etc. The possibilities are endless.
You can create a button to adjust audio delay, view new movies/shows... you get the point!
The only possible reason for people configuring the remote as a keyboard would be to allow for more buttons... but I have never run into issues with the MCE remote running out of commands. There are plenty of extra buttons not in use that can be customized.
List of Built In Functions
- pedr0 - 2011-03-11 16:09
Cool - thanks. Though I only half get it at the moment. It's the concept of modifying of the keymap.xml where I start getting confused. I'm sure it'll make more sense once I get the hardware and have the software in front of me.
- bmcclure937 - 2011-03-11 16:32
Yes. I was confused about the mapping process at first... but it is much easier to comprehend once you are able to dive in and try things out.
The keymap.xml simply takes the button and assigns it an action in XBMC. This action can be any of the functions in the links I provided above. For example, I could map the Left button on my remote to navigate Left... but I could just as easily map it to navigate Right by changing the button assignment/mapping in the keymap.xml
This is dependent on your Logitech Harmony Software configurations. If you properly set up the remote as an MCE device (as detailed in my guide that I linked above) then the remote should work out-of-the-box with the core functions. So, for example, the left button would be mapped properly to navigate left within the default keymap.xml without needing any modification.
The only reason you need to use the keymap.xml is to tweak buttons to your preference. You can use the Logitech Software and the keymap.xml together to fully customize and tweak your remote to work as you desire. With this combination, you have full control of the actions each button performs on your remote.
My advice is to not touch the keymap.xml at first and tweak the Logitech Software mappings to perform the correct actions for the buttons (or the actions that seem logical for the buttons)... if they are not doing so by default. The settings I use are included as screenshots in my guide!
Once you have done this, then you can tinker with the keymap.xml and change the functionality of buttons, add custom buttons, etc...
I have been meaning to finish my guide to include my full keymap.xml file (which includes custom buttons meeting my needs).