kendals
If you are using v7.5 of the Harmony Software [HS] you don't need to worry about that NEC stuff anymore.
When you create a new device in [HS] ADD DEVICE, you tell it via drop-down menu selections:
Device = Home Automation > Light Controller [yes light controller, I know it makes no sense]
Manufactuer = Smarthome
Model = [type in] 2411R
* Factoid* Just to prove that the device is really in their database, type in 2411 in the previous step, and it will prompt you "did you mean 2411R ?"
The fact that the IRLinc is in their DB means that the device codes you will given to use are tested to work with the IRLinc or in other words NEC.
Also, Matt's comment on how to test for compatibility is right. Point ANY remote at the IRLinc sensor and if the green light on the bottom [next to the mini jack plug] lights your good. *BEWARE, if your eyeball isn't right next to the green LED you will never see it. Shame on Smarthome for such poor design.
If you read many posts regarding this topic, look at their date, they are old [pre HS 7.5] Back then you did have to waste a lot of time finding the magic codes.
*WARNING* restrain yourself from calling Logitech's support line. They barely know their own products and know NOTHING about home automation devices. I spent over an hour with a senior tech trying to convince him that 'home automation modules' don't come with remotes!!
These people live in an AV world [TV's, VCR's...] they think all devices come with remotes. His final comment was "All devices come with remotes, if you can't find the remote that came with your device I can't help you" !clueless!
The whole point of using a Universal Remote with home automation is that we get to make our own custom remote buttons [the ones next to the LCD section of the Harmony880, sorry I've never seen an 890]. As long as it is programmed correctly you could have a button named FRED that sends command 7 that turns on a ApplianceLinc to which your blender is plugged in. The devices are dumb, as long as they know Button X is associated with module Z your good.
I can save everyone a lot of the pain that I have gone through in the last month in trying to get modules to talk to modules directly. After over 100 hours of troubleshooting I finally gave up. It should work, it must work, but it just doesn't.
The superior way [suggested by Matt] is to let a device transmit a command, set up a trigger in Indigo to 'listen' for that command, and then let Indigo handle the logic. My life has improved greatly since letting Indigo be the brain. Thanks Matt
I hope that clears some confusion.
Matt,
Back to my problem.
As per your last post.
What happens when you send the code for button 2 (labeled DOWN)?
Nothing, the IRLinc shows no indication that the signal was received and the Indigo log is blank.
When walking through all the steps to program the IRLinc, does the LED on the IRLinc behave differently for button #2?
No, the visual clues [LEDS] involved were identical for 1,2,3. No indication of anything other than success.
Lastly, when you press button 2, what does the LED on the IRLinc do AND what does the LED on the PowerLinc do? Do they behave differently than when button 1 is pressed?
2414U
- button 1 & 3 = Blink-Blink-Off-On Solid
- button 2 = sometimes nothing, sometimes one blink
IRLinc
same as 2414U
FYI: Green LED always flashes on IRLinc
The most puzzling thing is that if I go back and program #2 again [as in 1,2,3,2] it sticks, but shows up as button 4 [4th programing attempt] in Indigo's log??
I just can't seem to get 2 = 2