paulbates

You press the button next to whatever feature your are tweaking after you change it. You should not need to write updates to devices, unless the little green 0101 icon is next to the device

I would declare this one to be in ticket land, let UDI help:
https://www.universal-devices.com/my-tickets/

Yes.. factory reset then restore device. It also must be in linking mode first. 
The "running then" is normal for the typical battery monitoring programs

I found your other post. The center button is used for linking. Take a look here
https://support.insteon.com/support-knowledgebase/tag/2473SWH

If the conditions of the program changes to false, the program will stop executing in its tracks during the Wait.
Since you turn off pool/waterfall, that kills the program in the first then statement
What you need to do is have 2 programs:
Reset Waterfall -
If
     Time is 2:00:00AM
     And 'Outside / Pool Waterfall' Status is On
Then
    Run Program Reset Waterfall 2 Then
 
Reset Waterfall 2
If
   (No condition)
Then
    Set 'Outside / Pool Waterfall 3way' Off
    Wait 10 seconds
    Set 'Outside / Pool Waterfall 3way' On

What you could do (psuedo code)
program 1
If sump pump activated 
Then:
  Send notification
   Run program 2
 
Program 2
(No if)
Then
   Disable program 1
   Wait 1 hour
   Enable program 1
 
  

Guessing "no". The forums indicate that they haven't logged in since August 14, 2022. 

It will take to statements to get the total in the variable:
$TempGradient = $inside temp
$TempGradient -= $outside temp
The -= means subtract $outside temp from $Tempgradient.
$Tempgradient has to be a state variable, as is any variable that is used in an If statement

To keep it simple, would you consider email > email?  My guess is that most mobile providers are headed down the path of no more email > text
One way would be to set up a separate email account just for this purpose and make sure it can send priority notifications on the phone.
That way, the eisy notifications won't get lost in her regular emails, and as a new account just for this purpose shouldn't see spam. The ios email client allows for an manages multiple mailboxes within the app. 

The notification plugin is recommended with 2 ways to go based on how complex your notification needs are:
You can start with the free versions and have notifications come through UD Mobile. The UD Mobile template is the first on the list and handles simple messages... simply.
  If that doesn't fit your need, you can upgrade to the pay for version of the notification plugin and send notifications through notification plugins through the pushover app. You'll have to touch up all of your notification programs, shouldn't be too bad and you can likely use your existing notifications with variable substitution

You'll want to read through the notification section of the forums to see some examples

Yes, this is now how it works. Static IP addressing is a support headache for UDI when routers are switched out and the local NAT subnet changes.
The right way to do it is log into you router and use DHCP address assignment. It will give you a consistent IP address, owned by the router's DHCP.

Ok, you'll need 2 programs
<Program 1> Computer Cabinet once an hour
If
   <no statement>

Then
   Repeat every 1 hour
        Run If Program Computer cabinet

<Program 2> Computer Cabinet
    <your current program>

Notes:
Set the first program to run on start up Disable program 2 so it does not run automatically What this will do is the the ISY will run program 1 when its started Program 1 will run once an hour Program one will call program 2 Program 2 is disabled so it will only run when program 1 calls it
 

Chances are your ISY 99 has a local ip address subnet that is different than your new router. Example some use 192.168.0.x and some use 10.10.1.x  etc.
Do you have the old router still and able to turn it on and attach to it to see what IP subnet it uses? Many router/modems allow you to pick what subnet you use.
An alternative is to:
Power off the ISY-99. Press and hold the "Reset" button (usually near the power input) for 10 seconds while powering it on. This should reset the network settings and allow you to reconfigure the connection. But it might also rest the ISY, do you have a backup handy?

I had it to and I think it updated from 1.2.2 on its own. Once I clicked the X on the side of the message, its not come back, even after closing and logging back in

It's the switch that's responding inappropriately, so an unwanted link to repsond to the remote is likely there.
Factory reset the switch and perform a restore device

I've not seen Insteon update the infamous "white paper", but online discussions have suggested that, while backwards compatible, i3 devices are supposed to have improved communications and security. However insteon is unfortunately mysterious on their own site about i3; you can read about each product and the director app references them as being incompatible with their old hub.
IMO the 2413 PLM is still i2, so these improvements would be realized through i3 to i3 devices only, not eisy> 2413 > i3 devices. However, that assumes they didn't make changes to it and I don't have a way to know that. It seems there would be a versioning with marketing hooha and sell it as a feature. There isn't.
To look at it qualitatively, I'm into my second year at a new house, new eisy and i3 devices, my observation is that the handful of any individual insteon false "ons" (no "all ons") have been on microdimmer modules and lamp modules, which I believe to be i2. Speaking of all ons, we proved here on the forums that the "all on" reponse has been removed from i3 devices,, they are immune.
A suggestion is to go to the insteon forums and ask directly for insteon to answer, or use Insteon's sales site and use the pre-sales button to ask them directly.

Variable substitution, I believe it works in NRs too:
https://wiki.universal-devices.com/ISY-994i_Series:EMail_and_Networking_Substitution_Variables
 

Once you create a scene in the ISY, you turn the scene on and off, not the device.  This includes iox programs.But if you turn any one of the devices on at the switch, they'll all go on and off

If that didn't fix it, sometimes java needs more memory to run the admin console / iox:
-     Close the admin console / iox
-      Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following:   -Xmx512m
-      Press Ok to close the window, then Press Apply to save the changes
 

All great questions that don't have answers yet. The link you provided is all that can be known at this time. When they're certain its good to roll out, we'll get a post with all the answers.

The portal can support multiple devices. Add the eisy and maintain both as long as you need to.

Two suggestions:
When using the scenes and devices are not turning back off, either remove the load (unscrew bulb,etc) or pull the bottom tab out on the switch. Keep repeating until everything else functions. Either the load is the culprit or, see 2. 
  Sometimes insteon devices that have run in place for many years need to have their data refreshed. If there are switches that are more likely the culprit to the problem, factory reset them and then right click in iox and restore device. In my experience it's been these devices in this order: keypadlincs, togglincs, any device that's the most remote from the eisy in terms of wire feet. Unrelated info, I grew up in Woodlawn, just south of you!

As an appliance that info is not available on the surface of the eisy. I believe you'd need to use an SSH client to log in and use FreeBSD command line to see what it is. Pretty sure everyone but developers would be on the same version as eisy is an appliance, and in general it's not important for us to know unless wanting more capability that someone with developer skills would need.
I think I read its 12.something but don't remember and never looked. I'm counting on the UDI team to come out with instructions or a link or something for us to follow sometime this month.

A PLM with only 2 links is a broken PLM, there should be at least dozens of links. 1622 means week 22 of 2016, a period when PLMs had the bad capacitor issue.
I don't disagree with @Techman on aligning FW/UI versions, but your PLM is on borrowed time.

Give this post a read: