Saturday at 09:17 PM2 days In a large lot of devices that I bought last year, I got two of these, IRlinc Transmitter. I did some searching and found the discussions below on the forum, from 2017. The two units that I have are also release 4A. Now here's the interesting part: The guy I got them from (and a bunch of other Insteon devices) had a ISY994i, and he told me that these IR transmitters worked with it. The sticky tape on the ends of the emitters has been torn away, so these have clearly been used. Yet the discussions I see, including the discussion below, say that they need firmware 1.3 to work (with the ISY994i at the time). I'm trying it out on a test Polisy. I can link the module just fine, using either link method, and learning a IR command seems to go through ok, but the device nodes never appear.Seeing that the discussion from 2017 includes a few still active members here ( @Brian H and @larryllix ) , I thought I'd ask whatever became of it? Even more tantalizing is that @Chris Jahn and @stusviews say they got it working with v4A, though that was with a ISY994i. But all the prompts are there and look the same, even in 6.0.4 on the Polisy.
Saturday at 09:38 PM2 days The only thing I remember about those pieces of junk is the unit I received had the IR sender was wired in reverse polarity and I could never get it to work properly. I could not get passed the memorize the IR codes I tried to program it with, and then ISY would not recognize it properly.When I tried to send it back under Insteon's warranty, they replied, sure..not problem but the $50 CAD cost to return it for warranty services was almost the cost of a new unit. Poor warranty for a newly purchased device. Buh-bye old Insteon failure. (Glad to see new blood there)Garbage.As IR was dying very quickly I attempted to find other ways and other equipment that didn't use IR, or also supported WiFi control.
Sunday at 09:25 PM1 day Author I actually got this working...on a ISY994i at this point. If I can get this down to a procedure (instead of a few lucky breaks) I'll then try and see if I can reproduce it on the eisy. That would be interesting. My stubbornness has been motivated by what I said in my first post ( @Chris Jahn and @stusviews say they got it working with v4A). By trying it out with a ISY994i first, I figured I was closer to their configuration. That's my usual process: make it work first, then change one minimal thing and try again.
Yesterday at 02:16 AM1 day I've got a box of popcorn ready. I have both IRLinc devices (T&R) in storage. Never used them. Probably never will. Still, I'm dying to know how this turns out.-Tom
18 hours ago18 hr Author Well, this looks promising. I got it working on the eisy now. I don't know how "optimized" my routine is but it works. For example, I haven't tried learning two codes and then linking both, as the instructions suggest. That doesn't seem to work. Stick to one at a time...I'm doing this with my eisy at release 6.0.4 and IRLinc transmitter version 1.A as showing on the label (shows up as "IRLinc Transmitter v.4A" in IoX). If your IRLinc is a different version, this may or may not work. The UDI online documentation mentions needing version 1.3, but as I indicated in my first post, two people reported it working with 1.A, which is what kept me trying.First, I linked the module itself, just like any Insteon module. I started by doing a factory reset on the module (hold the link button pressed and plug it in, until the blue LED blinks off, takes a good 15 seconds). Then in IoX I went into Link Management and clicked on Start Linking. The Link in Progress pop-up box appeared and I selected the "remove existing links" option, and left the box open. Then I pressed the link button on the module and the module appeared quickly as to "be added". Once that appeared, I clicked on the "Finish" button in the Link in Progress box (which will close it), and a progress bar shows the module being added. Once that is finished you will see a new node in IoX, which is the module's Insteon address with a ".1" appended (eg: 33.51.B7.1).Now to learn a IR code.Make sure your patience is fully enabled! The instructions in the larger pop-up aren't quite what I experienced, so bear with me...Now on the IRLinc module "double click" the link button. This can be frustrating, and take many tries. Like a dozen tries... What you want to see is the blue LED start to blink slowly and steadily, which indicates it's in learning mode. Point your remote at the IR sensor on the bottom and press the button you want to learn. The slow blink will stop. Now press the link button once to see the IR emitter blink the code it just learned. You can do this repeatedly, and use the IR emitter to test the IR controlled device to see that the code was learned correctly (hold it close to the IR receiver on your TV or whatever).Once that is done, you now need to initiate linking, Under Link Management, click on "Add Button to IRLinc Transmitter". You'll get two pop-up windows, like this:In the Linking in Progress window, select the "Add devices found in links and keep existing links" option, which will cause a third pop-up window to appear, warning you that this operation may take some time. Click on "OK" which will close that new pop-up, but leave the other two open.Now hold the link button in, until the IRLinc beeps. This can take 10 or 15 seconds. Or not beep at all... You should also watch your admin console screen for a "device to be added" box. The beep doesn't always seem to happen, but the the "device to be added" window is the key here. Once you get it, release the link button, click on "Finish" in the "Linking in Progress" window. You should see a progress bar, as it creates the new node. The new node will have the last digit incremented, (eg: 33.51.B7.2).To learn more codes, redo the whole procedure, starting with the link button double click (as many tries as it takes). You should rename the new nodes as you create them. to reflect their IR function, digit, etc.Now to use the learned codes.If you look at one of the new device nodes, all you see are a Beep button, Write changes and a numerical select list. Those don't seem to do anything...! The only way you can use these nodes is by putting them in a scene. Create a scene for each button sequence you want to use in a program. So a channel change might have three nodes in the right order, a power on or off might be a single node scene, etc. If you need delays, then you'll use a program to add the delays, such as power on scene, wait 15 seconds, channel scene.That's it. This was all determined by experimentation, and is certainly open to improvement or clarification. So ask questions of make suggestions.And of course if you try it and it works for you, let me know! Edited 18 hours ago18 hr by Guy Lavoie
14 hours ago14 hr Author It's actually quite easy and consistent, once you get the hang of it. The hardest part is getting the "double click" on the link button, to put it in learning mode (slow blink). Then the routine is:point the remote and press the button you want to learnpress the link button to test the learned codeGo into Link Management -> Add button to IR transmitterclick the "keep existing links" optionpress and hold the link button on the module, until the "code to be added" box appearsClick on "Finish" to complete the link procedureTakes a couple of minutes per code.
Create an account or sign in to comment