This unit is a little tougher for a lot reasons. Being a combo device, it is already a challenge for integration and control, unless it a manufacture like Sony who is really good at generally always giving you discretes.

The other major problem is that I was starting without an OEM, and I do not have the same model number unit as you. I was working with an LG LHB335.

1. I loaded up a Harmony with codes for the HX-952 and fired them at my LHB335 to confirm they were using the code set. -confirmed-

2. Then I did some x-learning of about half the codes into my pronto to get their hex and learn more about them. This is where things get more complicated.

3. Using IRScrutinizer to help ID the codes, we find that Protocol=NECx and d=44/sd=44 AND d=45/sd=45. Fun stuff. Now I have over 500 codes to fire at this unit because it accepts codes from two different device sets.

4. Using MakeHex, I generate the 255 codes for d=44/sd=44. IRPanels makes it a pronto file, and prontoedit to dump it in.

5. Fire codes and notate the response.

6. Using MakeHex, I generate the 255 codes for d=44/sd=44. IRPanels and ProntoEdit gets it into the remote.

7. Fire codes and notate.

8. 1.5 hours later we have some codes!

________

I see you were already using a harmony. The harmony db gave us the optical discrete. Well, it is discriete in the sense that it goes to optical 1/ optical 2. Not very useful, though it gives us an anchor.