MrBill

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.

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).

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.

There's two upgrades, and yes you should do both of them. V4 to V5 on the 994i hardware is the first step. V5 is a prerequisite for migration to eisy. It's fairly straight forward now, especially if your system is currently Insteon and doesn't contain z-wave. If your "Programs" use the command "adjust scene", those won't be automatically translated and require manual attention. If you do have Z-wave and it's the older 300 series board, stop at version 5.0.16c. No z-wave, or an newer 500 series board go directly to v5.3.4. In addition to a "File backup ISY", I would also suggest a text backup of programs (copy root program folder to clipboard and paste into notepad and save as whatevername.txt), upload the still zipped new firmware file to the ISY and the ISY reboots itself during the upgrade. Clear Java including installed applications and applets, get rid of any files you have named admin.jnlp or start.jnlp and reinstall the launcher. Once the admin console is opended again first check Help > About for matching firmware and UI versions, then check Programs tab > Summary sub-tab, look for the color yellow... if you see any that program needs human help, probably because it contained "adjust-scene" (that text backup of programs come in handy here).. also if you had any intentionally disabled programs they will need to be re-disabled. This has been the "nutshell version" there are more detailed versions of that process... actually a recent one of @Geddy's post is more complete than any I've done. You also gain the ability to use UD mobile after this upgrade. The ability to use node servers also exists but unless you have a Polisy or eisy you're not going to have anywhere to run the node servers themselves. After upgrading to V5, the second upgrade is migration to eisy. There are also many posts on the pro's of doing so, but the nutshell version, it's much faster, it will be supported by UD for the longest in the future going forward. You could always put this one off for awhile if there's little interest is expanding your automations beyond what they are today, but if this is your path, always be sure to have a good current backup of your ISY994 on hand. There will come a day you will need it because the hardware has failed and UD is no longer supporting it, if you have a current backup at that point you can still migrate, but without a current backup you will be starting over. I would get the upgrade to V5 completed because there will come a time soon that UD won't fix things like "V4 certificate issues" that appears to be a problem for you at this point. I think they'll at least support migration from V5 to eisy for a long time to come... as long as you already have the current V5 backup or can still make one.

Disclaimer: I'm speaking of another system, I do not have iAqualink. The Salinity sensor on my salt cell itself has read 0 for years. Upon asking questions in many places, it turns out that Pentair salinity sensors are well known for such failure. I don't know if that trickles over into salinity sensors in general or not. Fortunately unless you're refilling inches a day due to a leak, salinity doesn't change much. Refill from evaporation doesn't change salinity because salt is left behind during evaporation, so only splash-out and leaks cause salt to exit and an entire season of splash-out probably isn't even 5 pounds of salt. I find that once every few years I might need a bag of salt.

You should contact UD support... https://www.universal-devices.com/my-tickets/

I agree. However 5.3.0 to 5.3.4 shouldn't add any mysteries and/or issues. Have you tried Restore PLM a second time?

Steve and others running V4, You should probably think about upgrading sometime soon, not only to v5, but also to newer hardware, support ends 6/1/23 for the ISY994 https://www.universal-devices.com/byebye994/

It's interesting to note that you are both still using v4 firmware. I wonder if something like a certificate expired. or something happened with UD. You might try downloading the admin console directly from the ISY and not using the launcher. http://IP.OF.THE.ISY/admin.jnlp save it to your downloads folder or desktop then double click it.... any change? IP.OF.THE.ISY should be changed to the IP for the ISY that you see in your finder window.

I don't know, hopefully someone will have another thought, the only thing i can think of is kinda of nuclear... uninstall java poke around AppData and get rid of leftovers with folder names like sun, java etc reinstall Java 8, update 361 from https://www.java.com with that in mind I have no further suggestions. To be honest I'm not sure what you mean first you say you can't get in then you say you can.... I note you're on version 4, do you have plans for your system, or it doing everything you want and need and have no plans to upgrade. The ISY994 is discontinued, and won't be supported at all by UD in the future. (there's an announcement somewhere that says when support drops)

you only had 2 .state files? that count seems low... not all of them always exist but usually more than 2 I'm no expert but these are the 4 I usually have

try deleting your .state files... if that doesn't work, clear your java cache, including installed applets and then reinstall launcher.

Are you seeing something like this? if so, click the isy line to get the selector window that's overlaid. then choose Admin Console (Cloud)