I don't know if anyone out there has a similar setup, I've been pulling my hair out for the past few months trying to get the power macro working.

For some unknown reason, the 'up' IR command (which has to be send after a long PS, and several downs), inconsistently registers as a double press. Changing pauses does nothing. I have just run out of ideas, and hoping that someone might have figured this out, or have some suggestions??

Try a different version of the code? In fact, which codeset are you using?

Hey Daniel,

Thanks for the response. I've used this code for years (I also downloaded another PCF that had the IR2BT PS3 codes, and it's the same one). It's really really weird -- I have the code mapped to the hard button. Just sends a single command when pressed. However when I add these in a macro, will get either one or two presses. Even tried things like putting a second delay between IR codes, even inserting an IR code (left) before and after just to ensure that the multiple commands weren't being misinterpreted.

Up
0000 0067 0000 0015 0060 0018 0030 0018
0018 0018 0018 0018 0030 0018 0030 0018
0030 0018 0030 0018 0018 0018 0030 0018
0018 0018 0030 0018 0030 0018 0030 0018
0018 0018 0018 0018 0030 0018 0018 0018
0018 0018 0030 0018 0018 01D9

So I've tried both the IR2BT and Harmony BT adapter and both give similar results.

Pressing a button that just has the up or down IR code on it. Single press, no issue.

Create a macro with an up or down, and it may or may not be sent twice.

Must be the RF->IR->BT translation.

Maybe use jumps? Any other ideas?

One other thought I had was to pick up PS3 USB IR dongle to cut out Bluetooth translation.

The IR2BT and Harmony adapters would use very different codesets. Don't see anything wrong with that code, however the usual issue with this sort of thing is the code being sent for too long (macros repeat a code for a particular duration, while manual presses only do so for as long as you hold the button). You could try a broken version of the code - a single press rather than repeatable code.

Thanks Daniel. What do you mean by 'broken version'? I'm just linking to a button that has the IR code.

So I'm trying to tackle this another way. With a rasberry PI and an old USB-UIRT I have lying around I managed to get the USB-UIRT to send the up/down codes consistently. Which is great. However (nothing is ever easy), I can't get the USB-UIRT to send the long PS code. The pronto has a 'long PS' button which is simply the PS code with a duration of 2.5 seconds. Any idea on how to actually craft an IR code in pronto format that is 2.5 seconds long?