Guy Lavoie

You should try progressive troubleshooting steps. First off, try and see if the eisy is receiving the button presses from the keypad. View the button's status in Admin Console and press the button. Does the status update on the screen? If not, do a restore device on the keypadlinc. If the status updates ok, then create a test program that simply writes or increments a test variable. If that works but your existing program doesn't, then it could the device links in the program that didn't migrate correctly (it happens). If that seems to be the case, edit the non working program and re-select the keypad button from the device list, and click on update (as if you were modifying the program). This updates the internal reference to that device. Then save the program and try it again.

As @oberkc referred to, there was no mention of whether the PLM will be the one that was used with the now dead ISY994i or if it's the one that has been with the used eisy. I would certainly try the one that was already in that house first. In that case, it would be just like doing a ISY994i to eisy upgrade. Another thing: the ISY had release 5.0.16, which is the last version (5.0.16C actually) that supports the Zwave 300 board. Do you have Zwave devices too? If so, those won't migrate, and you'd need to reinstall them (and have the needed Zwave 700 series dongle or Zmatter dongle on your eisy).

I also have Alexa extensively implemented (mostly for the wife) but I also have an alternate way of doing everything without it. Whether it be seldom used mini controllers, alternate app (like the Hue app), etc. I just don't want to be stalled by an internet outage. Local control is king, everything else is just icing on top.

Yes, that's what I meant. The idea is to remove any links in the PLM that don't belong there, which would be all of them if it's being moved to a different home with different devices. Since a migration might be assuming that you're updating an existing system, it might not automatically restore the PLM (since the links would already be there). If that comes up, then a Restore PLM might also be needed after the migration. A few people have run into some issues with the Upgrade Packages process. Though I have yet to hear of one that wasn't recoverable by UDI support. The fact that you're not upgrading a live system should give you a bit more piece of mind if something happens and you require support.

The two versions seem close enough, so upgrading beforehand would seem like a good idea. I'm not sure what you mean by restoring the PLM. Restoring a PLM is something you normally do when replacing a PLM on an existing system, or if you have communications issues and you think some links might be missing. The migration process says to connect the PLM to the new controller and run the upgrade, though that assumes that the PLM was being used with the same devices, on the controller you are upgrading from. What you might need to do instead is "Delete Modem (PLM)" to erase the links from the previous devices, before doing the migration. This would be like installing a new PLM, and then migrating.

Great idea, a WAN automation setup 😉 Hah, we're hooked on UDI controllers because we eat and sleep local control!

It will depend on how the hub is added. For example If it's by manually defining it's IP address as a parameter, then you could probably define two hubs in two instances of the plugin. If however it's by an automated discovery process, then the plugin would need to be able to handle finding more than one.

If no one else is interested, I'd take it. I'm in Canada, if that's an issue.

If you're comfortable woth replacing an ordinary switch or outlet, then this is just as easy. Just make sure you properly turn off the breaker first. Wire colors are the same on the old and new Insteon switches.

Yes, open the box by removing the screws underneath.

When you say that you can access it from the cloud, do you mean when you select "Admin Console (cloud)" in IoX Finder? That's accessing the Admin Console program from the cloud, downloading it. If this is the case, then it could still be a SD card issue, that's preventing you from loading the Admin console program from your ISY controller.

Try right clicking on it and do a restore. Sometimes it's just a link that gets corrupted.

Now, you need to reverse engineer your own house!

In the launcher try this: Click on "Add" and for the URL, put: https://192.168.0.13:8443/desc Then try that.

The Repeat statement, with the While option, allows you to repeat a command (such as a Wait) the number of times that the variable referenced in the While condition is true.

Well you cannot technically migrate two active controllers into a single new one. You'll have to decide which one has the most customized configuration, and migrate that one. Then manually recreate the features of the other, simpler one.

If you're referring to Somfy shades using the RTS protocol, the way to do it is by timing, in a program. That's also how the Somfy plugin for the URTSII does it. You configure a parameter telling it how many seconds a full open requires, and it will then convert any percentage command (such as with Alexa) to a time value between the open and stop commands. Because RTS is one-way, you have no way to know if it's starting out as closed or not, so use this to the best of your knowledge on how the shades are used by the owner.

Looks like things aren't getting eisyer... Sounds like a trade war related issue. But an answer from the source would certainly be good.

In IoX launcher, click on "Admin Console (cloud)"

Ah yes, garage doors and KPL. This is one area where we really want to use the KPL LED as a position status indicator. I messed around a lot with it to get that functionality, no matter how the garage door opener is activated (including it's own RF remotes). I think I restarted the programming project 3 times. I did get it working as I wanted it, with one KPL button/LED for open and another one for closed. The end result is 14 separate programs. This includes proper status indication in UD Mobile too. The door activation hardware is one IOLinc (for input and output). The trick was getting to sense position change when not done by automation, and still update status, without triggering any events. To do that, I needed to use a disabled program that only gets run once. Fun stuff.

Use the search function to look for variable usage in your programs. Right click on "My Programs" at the top and then on "Find/Replace". In the pop up window, select the type of search from the select list, and then the value that you want to look for, and then "Find".

Dual band sounds nice, but if your setup isn't working anywhere except in that room, then it sounds like something is really wrong, which dual band modules might only make things work marginally. Have you tried the opposite: put your PLM and modules in any another location except that office? What else do you have in the office that might be creating noise?

The first thing I would suspect is electrical noise issues. Have you tried the devices in more than those two locations? Are the devices dual band?

Do you remember when you last updated it? Within the past couple of months, or much longer before that?

You could try a factory reset on the switch, then try the linking again. Factory reset is done by pulling out the link button for 10 seconds, then pushing and holding it in (as when you link it) until it beeps.