Guy Lavoie

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 learn press the link button to test the learned code Go into Link Management -> Add button to IR transmitter click the "keep existing links" option press and hold the link button on the module, until the "code to be added" box appears Click on "Finish" to complete the link procedure Takes a couple of minutes per code.

Another possibility is if you now have Alexa+, which is known to have issues with automation.

Yes, a scene is a scene, whether it's triggered by Alexa, a program, or even in admin console.

So your issue is that you can't access eisy-ui. Try accessing it directly with it's IP address, like this: http://192.168.0.123 If connects and you get a blank screen, do a browser screen refresh.

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!

I have a Watercop valve, that I got as used, locally. It uses Zwave and has worked very reliably, even though it's a model that has been said to be a problematic early version. Maybe the fact that it's literally 24 inches away from my Zwave dongle helps. The previous owner had used it for irrigation.

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.

So no emails are getting through at all?

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.

Yup, this has become an expensive sport.

You mean emails sent by your programs? Working fine here. I'm using the default email settings (using UDI's mail server).

I was just browsing the aartech site (official distributor for UDI products in Canada). The price really shot up with the new eisy r2. It's $589 in Canadian dollars. Ouch.

I was just experimenting a bit more with the Ping plugin. You can use it to make a graduated approach, to find out where your IP chain seems to be broken and take appropriate action. Ping the loopback address (127.0.0.1), and reboot the eisy if needed. Ping the router, restart if needed. If possible ping the modem's public address and restart that if needed. Ping outside destinations, both specific needed ones and general sites, to distinguish if it's the internet of a specific destination. Looks like there are many possibilities.

Just to add more detail, a failed ping will give a "In Fault", but 5 missed pings will then change the status to "Off Network". This can help avoid temporary hiccups. You could ping both a common site like the cnn site I tested with, and a site you depend on, such as the portal, and determine (using an "And" condition) if it's just the portal that's down, or your actual internet access. I'd increase the poll interval to something like every 10 minutes.

I have a suggestion for that: there is a free plugin called Ping, which does exactly what you need. You define a device name, and a URL to ping (you can define several). It pings it every ShortPoll time (default every 60 seconds). The status of the device will either be "On Network" or "In Fault". I just tested it with www.cnn.com as an address that should respond, and a jibberish url to get a fault response. Works great.

Because that will open polyglot instead... 😄

I always "save" the list of controllers in IoX finder. Then whenever a java update or whatever causes something to go missing, I reload the IoX file I saved earlier, and I'm back in business. I also list the controllers by IP address, not by name. Also (in regards to the discussion above about multicast DNS), what happens if you have two or more eisys on your network? They can't both be eisy.local.

I did things the old fashioned way, adding my controllers to my PC's local hosts file. There is never any confusion as to which one is eisy, polisy, polisy2

Yes, that's exactly what I do too. One button for the ground floor, another one for the basement. I actually have two programs: one that turns on the button if any light is on (or, or, or), and a second program that turns it off if they're all off (and, and, and).

I don't see a way to sort them in any other way than in alphabetical (ASCII) order in the main list. You can arrange favorites in any way you like. You can decide to hide nodes, and unhide them from a menu option.

Yes, UD Mobile supports turning devices on and off, etc. You can also create a "favorites" folder for the most often used ones. You can view and edit variable values. There is some limited program editing supported. You can have devices display different icons and colors based on status. You can set up geofencing, to trigger commands or set variables based on entering or leaving defined geographical areas. You can add devices of all types (Insteon, zwave, zigbee, Matter) to your controller. You can access your controller through local network and also remotely if you have a portal subscription.

I have a program that watches the status of the light(s) in question, and have the program turn on the KPL appropriate LED.

Maybe they meant editing variables, vs displaying them. One can hope they'll add them, the dashboard being a new feature. The best suggestions come from actual users 🙂

Thing is, eisy-ui only displays nodes.Variables aren't nodes. It would be a nice addition to eisy-ui if it could display individual veriables on the dashboard (hint hint UDI...). Just the variable name and the value.

Virtual offers several types of virtual devices, but "virtual variable" isn't among them. The closest thing might be a dimmer, where you can see the On level. But that limits you to a range of 0 to 100 which may or may not suit your purpose. To create one, add a custom parameter with the desired node number as the key, and a value of "dimmer". Save your changes, and exit end log back into admin console. Have a program set the On Level to the value of the variable you want to see.