Guy Lavoie

One test you could do is to cut the power to both your router and/or modem, and your eisy. Then power the router/modem back on, wait a couple of minutes, and then power on the eisy. If it comes up ok this time, then it could be a timing thing.

Sounds like some type of timing issue, such as the eisy tries to connect to the internet and portal faster than your internet connection recovers from the power failure. Did you upgrade or change anything with your internet service? Router?

Migrated from a ISY994i? If so, what release was it at? Followed the migration procedure with backup?

I know, we have heard rather little about Matter since the April updates. I haven't tried to see if there are updates beyond 5.9.1_18. It's not clear if they're actively working on it.

I don't have the Bond node server (or Bond device) but from reading the description, this is a device that sends out individual commands that you first learn into it. To do something like you're attempting to do, you would need to use program logic to calculate the time needed between two commands to achieve the same effect. For example if it takes 10 seconds for a shade to lower and you ask to close it 50%, then send the close command, wait 5 seconds, and send the stop command. I've done similar things, using a virtual device (there's a plugin called Virtual for this) and then a program that looks for the device getting set to a percentage, and send the needed commands with timing between them. For example I've automated ordinary 3 dim level night table touch lamps this way, though for the lamps it the number of "touches" that's counted.

So what's the status key value, and where do you go to see it? A variable? I have a similar program, though it sends distinct messages for each possible occurrence. I do get the odd missed heartbeat, once every few months.

As I like to say about backups: There are two groups of computer users, those who have lost data, and those who will.

Red would indicate that it's running the ELSE code in the program. You should post the whole program (right click, copy to clipboard). Could be some kind of logic condition causing it.

When you do a "replace", you normally start by adding the new device, as a standalone with a temporary name. Then you bring up the device you want to replace, right click, and select "Replace <device name> with" and select the new device you just added previous. IoX will normally edit all the links, scenes, and programs to use the new device. The old device will also be automatically removed. The new device will also get renamed to the name the old one had, so nothing will look different in your programs and scenes.

I've never created or edited programs from UD Mobile, but I know there are some things you can't do, that are only available from the admin console.

Wow, that's a detailed response that I'm bookmarking. Thank you! As you might already know from following this forum, I have an old Polisy coming that is "too old" for the usual upgrade procedure, so doing this will probably be part of the process of bringing it up to spec. Timely!

I was able to extract the link ok, thanks! So how does this work? UDI sends you a file that is a proper image of what a Polisy should be like, and you use this to write it to the SSD drive? Is a special software utility required to do this? Thanks.

What is this SSD imager you're mentioning? A hardware device?

The official route is with a ticket. The unofficial thing you can try (and seems to work for most) is to ssh into it and do a manual pkg install: scroll down to tokenworker's post Trying those various resets might have made not so easily recoverable, especially if you really cannot see it connected to your router.

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.