MrBill

@vbPhil oh sorry, i didn't realize you needed to know how to do that.... same as any other line powered Insteon device--hold the set button during powerup until the beep stops. (Since pulling the set button out on a switch air-gaps or de-powers the device, the instruction is essentially the same across the board).

did you do step 9 of the migration process? Does Alexa control anything else via eisy?

I think the mistake here is that the First thing you do with a new formatted card is load the appropriate firmware, the second thing that you do is restore backup. The ISY will boot with boot loader firmware when a new blank MicroSD card is installed. The problem is that firmware is both not complete, and it's ancient. Therefor the next thing to do is install full recent firmware, second thing to do is restore your backup. I'm not sure what happens when you perform factory reset on a new card, but components of whatever gets installed are likely ancient.

I don't think he's talking about the forum.... logging in for shopping, tickets, etc on universal-devices.com, AFAIK the forum still makes it option to use a portal account for login. www.universal-devices.com however only uses Portal login. Which makes sense because there are a number of web packages stitched together under the parent site, wordpress, a ticketing system plugin, a shopping cart plugin...etc After a hack a few years ago, they added the ability to use portal login for the forum. Everyone was to link their current forum account and to their portal account, and then after a period of time, users would only be able to use portal login... it's been years tho and they forgot about that detail and you can still use either type of login in the forum.

@rayg to post programs please RIGHT CLICK the program name in the Admin console Programs tree, choose the bottom item-- copy to clipboard. then Paste into a forum message. This is much easier to read and work with than screenshots. Are you saying the button is changed to non-toggle mode? (in non-toggle mode it will only send On or Off, whichever it's programed for, and each time the button is pushed it's repeating the same command. Toggle mode (which is default) alternates on, off, on, off, on, etc...).

Factory reset is what I would do.

There is a step in the migration process that migrates the portal including remaining paid subscriptions, and alexa setup, etc see Step 9 here, and here for additional information. I don't know if that's a typo, do you really mean Leviton? If so they have excellent documentation, if you know longer have the documentation that came with the switch you can simply google "Leviton <part number> Manual". Leviton has great Docs.

did you power off before messing with the SD card? If not, you probably trashed the SD card doing it with the file system live.

I agree with @kzboray UD is working towards Single Sign-on. The thing that's not clear is that portal accounts are free. Portal subscriptions have a very low fee. Portal Subscriptions allow you to access your device outside your local network.

or they asked the new Insteon for support documents. Insteon didn't say they would only support one 3rd party solution.... they indicated the door was open.

You need to upgrade v4 to v5 before you can migrate to eisy. You'll need to download the zip file to your computer. (you can find the link in the current releases, look for the thread 5.3.4 (ISY994) - Last release for ISY994 when you reach the appropriate step of the instructions there will be two firmware links, you have Insteon, so you have a PLM and want the first file (even if you don't have z-wave). (The second file is for those that do not have an Insteon PLM.). Do not unzip the downloaded file. (if you have a mac you may need to change something to get the file to save without MacOS automatically extracting it.) In the admin console Help > Manually upgrade, select the file you downloaded to your computer. when the ISY reboots, clear you java cache including installed applications and applets, also delete any files you have named start.jnlp and admin.jnlp re-download the launcher file name start.jnlp and double click it after it downloads. the credentials will be reset to admin/admin first in the admin console, Help > About to make sure your firmware and UI are both 5.3.4 second go to programs tab > Summary sub-tab... look for the color yellow... if you have any those programs need manual edits. If you have any purposely disabled programs, they will need to be disabled again. If you need to search the text backup of your programs I believe its "Not enabled" that you need to search for.

I seem to recall one of the benefits of PG3 was being able to run multiple copies of a nodeserver... Is that still true? and does it help this OP?

Try it with the variable ID number instead of the name. ${var.1.12} Or whatever number your is... According to the wiki, it should also work with variable name Substitution variables are available inside custom email definitions in the form ${<variable name>} which would seem to transalte to ${decGarageOpenTime} in your case, I've never used names in the substitutions tho, i've already recently become away of the name form.

just be certain to have a current backup.

Portal Account: Yes, Portal Subscription: NO The portal login is free, just create an account. You are not charged unless you add an ISY and activate the 30 day free trial for a portal connection. UD is trying to use the portal as a single sign on (SSO), it's optional for signing in to the forum, after creating a portal account just link it from your forum account.

you should be able to swap the face of the new and existing keypads if it comes to that.

So the only two devices in your tree showing the 1011 icon are those two? I agree with @Techman try Factory Reseting the device, then do Restore Device. (Pull the set button out, wait 15 seconds, push set back in all the way and HOLD it all the way in until the long beep stops. Then from the admin console Restore Device.)

I received quite a few portal failure alerts early on, but none since 4/12... even tho I know my internet connection has died several times (for long enough to interrupt Music streaming via Alexa).

The reason I made the statement that I made is the same integration is used for the hub and the PLMs. While possible it's different I expect it's relatively the same experience regardless of controller. It got a lot better after Insteon went dark a year ago, they added a lot of functionality that didn't previously exist within HA. Personally I prefer the experience with the ISY, but you can at least adjust all the Insteon parameters from within HA now... in some cases prior to a year ago you were expected to do that within the Insteon app and just control the devices from HA. Having worked with both types of installation (my son's house being Hub -> HA integration), I would still keep ISY to run Insteon. I've moved many functions to HA, but I'll keep using ISY/IoX for Insteon.

Due to browser security you have about 2 choices now to get the admin console. One is the Launcher, and that is the preferred method in most cases. The second method is to go to http://IP.OF.THE.ISY/admin.jnlp and save admin.jnlp someplace handy like the desktop. The problem with this method is you absolutely have to remember to get a new admin.jnlp file anytime you update firmware, and it gets more confusing if you have multiple ISY's and need multiple admin.jnlp files. The browser page that opens an admin console is a thing of the past. If security level is decreased to allow it, other bad actors can take advantage and run their own java.... The Launcher didn't come along until like 2018, it was created in an effort to solve the browser security issue.

The only time the hardware address of the connected PLM is read into the ISY is during ISY startup. When you select File | Restore PLM the first thing that happens is Restore PLM compares the value of the currently connected hardware address is the value the PLM was before... this determines whether you are just trying to fix links in an existing PLM for which it only re-writes the PLMs link table. On the other hand if you're selecting this option File | Restore PLM because the PLM has changed, it will have a new Hardware Address.... in this case all the links in the entire system need to be update with the new PLM address. This means the PLMs link file is written AND all the link in devices all over the house need to be updated. In larger systems this can take awhile, and a module or two may not work correctly when it's done and for those you would want to try "restore device" to ask that the links in that individual device be re-written. Randomly plugging in other PLMs to see what works is confusing the situation. We don't know what ISY currently thinks is connected, or if it's new changed hardware.

I don't actually know anything about the default template. but I expect it's reporting things that might have been logged at a similar time, not knowing if they are related to each other. Keep in mind, node servers didn't exist when the default template was created... the last time anything in that section of the admin panel got any change was probably in V4. those were much simpler times, before node servers, the default template is apparently not behaving now according to what they thought should work fine back then.

did you FIle | Restore PLM after rebooting eisy?

Send "notification" to 'bob' in the program has the content dropdown set on Default. If Content is set it is added at the end of the line... I don't know what the "default" template is or how it decides what information to include. For most notifications you should create a custom template and specify it in the program. To specifically answer your question, you're getting whatever substitutions are on the Default template, but I'm not sure how to edit the "Default" template. You can read more about email notifications in the ISY cookbook starting on Page 62

@BCreekDave To clarify look a few posts up in this thread, it's looks like V4 firmware has certificate issues. Everyone with this problem need to open a ticket. UD will need to address this, it can't be fixed on the user side.