Thanks for the follow up, and I'm glad you got it working.
CraigM wrote:I can't stress enough how important it is to keep a spreadsheet listing EVERY program attempt [1,2,3...], Button name, IR code used, device controlled, etc. ... Imaging someday you want to create a trigger. How will you ever remember that the module you want to control via IR was program #47 ?
I don't know that you need to do that, unless I'm misunderstanding the complexity. This is what I would do:
1) Create a new IRLinc group/scene for every remote control button you want to use (this is the hard and time consuming part).
2) Press one of the buttons you just linked to the IRLinc. For this example, let's presume you pressed the button labeled "UP."
3) Check the Event Log to see which INSTEON group/scene number the IRLinc just sent.
4) Create a new Trigger Action for that group/scene number and give the Trigger Action the name, "Harmony UP Button Pressed."
That should do it, right? It doesn't matter that the UP button sends out the IR Command for button #3 and that the IRLinc assigned that to its internal INSTEON group/scene #8 as long as you get the end result that you want which is when that button is pressed you want Trigger Action "Harmony Up Button" to execute. You can us the Event Log to see what is being sent to Indigo when that button is pressed, which is INSTEON command you'll want to assign to the trigger.
CraigM wrote:Matt, is there any way for Indigo to 'dump' the data contained in the IRLinc to a text file or the Event Log?
Not currently. And I'm not sure how Indigo would show anything meaningful for the IR command assigned to each group/scene. It might be possible, I'm not sure.
Regards,
Matt