paulbates

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:
 

Yes, that looks right. 
There's a catch-22 with the PLM restore.... you have to be connected to do it.
Try
powering down the eISY Unplug the the plm Unplug and firmly replug the plm's cable to the eISY on both ends plug the plm back in wait 10 seconds, the start eisy back up

Isy can take a max of 16GB. You'll need to buy a new 16GB
No. Create a fresh file set on your PC by copying the contents of the old card there. For the files it can't copy, take note of file name and directory.
Then unzip the backup on to your PC in a different location. Use the list you created to repair the file set on your PC by copying from the unzipped backup location on the PC.
Then copy the results onto the fresh card.

The address is printed on the front, bottom right of the faceplate mount as you face the outlet. Small type, with a qr code you can scan.. It's meant for scanning it into an insteon hub, but it will come up and you can read it on your phone
You can also put the eisy in linking mode, press the set button and have the eisy find it

You can add a new eisy to your renewed account @ my.isy.io

You're almost there.... under
Else
Set "Missouri Christmas Lights" Off

Yes... You've documented several symptoms, especially the restore that works temporarily

You want to be in linking mode first, so that the PLM/ISY catches the Insteon traffic from the device(s) being put into linking mode.

Since I've had eisy, this has behaved differently at different times and versions. Now, it sometimes can take 20 - 30 seconds to come up.... others right away.

You need to know how to log when you have an plugin issue and developer asks you to send them a log. What's important to know about that is:
you go to the dashboard in pg3x go into the individual plugin itself click details Click log Click "debug" from the list Do the steps that recreate the error you are seeing Click download log package Send that zip file in a message to the developer
 
There's a new wrinkle in the Session and Session Verbose options. I'm going to not select those unless instructed to by the developer.

Do not buy another license. Submit a ticket and it will get fixed.

Take a look at the solution, here
 

Right click on Deck Lights and pick "Restore Device". Compare and test again
An additional method is to factory reset Deck Lights, that will clear all links, and then "Restore Device".

It does... plugin = polyglot pg3.  You posted under eisy so I assume you have that, if so you already have polyglot installed.
There is a learning curve for sure
Another option: if you have the UD portal, use the UDM mobile app and notifications can be sent to it relatively easily, probably not a big leap from your att texting, making some mods to programs. You won't need polyglot. This may be the place to start.

I don't believe there is a time out, per se. It's not designed to be left running, when you're done working, close it down. 
Having said that, I forgot to shut it down sometimes and it will run for days before I notice. But I try to remember to shut it down

You don't have a ton of devices so starting over is do-able. Give this a read first and use it as a guide
I'd print out yourf programs you have for a reference.
One at a time, delete each device from the ISY, making a list of them as you go so none are forgotten. WRITE DOWN THE INSTEON ADDRESS FOR EACH BEFORE YOU DELETE - 11.22.33 format Reset the PLM Pick delete Modem (PLM) from the File menu and complete prompts Reset the PLM - Un plug, wait 5 seconds, replug while holding the set button until it beeps Unplug the PLM wait 5 seconds and plug in Unplug and replug the eisy, log back in to iox Go to Tools/Diagnostics/PLM info status, look for it to say connected Repeat 3 and 4 above again, even a few times, until it says connected Do not try to add the PLM as a device to your eisy, iox does that on its own One at a time add non-battery devices Go to each non-battery device, unplug, replug while holding the set button For switches, pull out the air gap, wait 5 seconds, then press in and hold In both of the above cases, Wait for the beep  Pick New Insteon Device from the linking menu be sure to pick "remove all existing links" One at a time add battery devices Go to each battery device, press and hold the set button until it beeps In both of the above cases, Wait for the beep  Pick Link a sensor from the linking menu be sure to pick "remove all existing links" If you get stuck on one, move on to the next.
Test everything out. 
You will have to update programs

It would be the same approach as your other servers and Rpis. SSH in to the eisy, create python or other method to detect the UPS's mode and issue command line to shut it down. I google searched "shut down freebsd" and specific command line examples were returned. 

Go to the My Programs folder and right-click on it. Pick Find/Replace near the bottom and select the device to find instances of it. 

I didn't read the entire thread, so if you haven't tried, in this order:
Unplug / replug PLM. Restart eisy, check again Factory reset PLM, check again, if connected, restore modem  
 

(2) Haven't tried it on the eisy, but give this thread a try. Looks like variable substitution might break it. 
I used HAD pages served from my ISY's web server and accessed them through the portal, but many years ago.
 

So... reread...  You'll want to do it this way
New Program - [ID 0045][Parent 0001]
If
   - No Conditions - (To add one, press 'Schedule' or 'Condition')
 
Then
        Repeat Every  1 hour 
           Set 'ERV'  On
           Wait  20 minutes 
           Set 'ERV' off
 
And set it so it runs at startup