MrBill

Polyglot3 is the future.  At the moment both Polyglot 2 and 3 are available for use on Polisy.  Installing new tho, you should use Polyglot 3.
https://<IP.ADDR.OF.POLISY> will land you in the Polyglot 2 interface, perhaps what you are referring to generically as "polisy".
https://<IP.ADDR.OF.POLISY>:3000 will land you in Polyglot 3 interface.
of course in either of those examples <IP.ADDR.OF.POLISY> is a place holder, you need the actual IP address of your polisy on your local network, you can't literally type <IP.ADDR.OF.POLISY>  (it might be obvious to some, but I didn't use to include this disclaimer and someone said "It doesn't work").

Login via SSH and type "uname -a" then email the results to support@universal-devices.com and await explicit instructions.  You most likely need to run those commands in the wiki, but note that "Polisy OS versions below 13" refers to the FreeBSD version as supplied by uname -a, not "My polisy is running 2.2.13. "
It's confusing, therefor I suggest contacting support for the exact instructions needed for your case.
 

Or if it’s the 3 dots… there’s exactly one font size, I believe 14, that causes that, change the font size.

Are you running any node servers on Polisy?  The ISY's credentials should be stored in the PG2 and PG3 menu, so that Polisy can log into the ISY as a user.  
In PG2, Settings > Polyglot settings.  Should have the stored credentials of the ISY.
In PG3, it's in the "ISY's" menu, edit current ISY,  and the store the cedentials to the ISY there.

This should do what you want to do....
Schedule tree - [ID 00C8][Parent 00EF]
If
       From 7:00:00 PM
      to  03:00:00 AM (next day)
 
Then
     Enable Program Alternate Christmas Tree
     $s.Christmas = 1
 
Else
     Disable Program Alternate Christmas Tree
     $s.Christmas = -1
     Set 'Kasa Controller / Color Christmas tree lights' Off
     Set 'Kasa Controller / White Christmas tree lights' Off
       
Alternate Christmas Tree - [ID 00C2][Parent 00EF]
If
        $s.Christmas is 1
 
Then
        Set 'Kasa Controller / White Christmas tree lights' On
        Set 'Kasa Controller / Color Christmas tree lights' Off
        Wait 15 Min
        $s.Christmas = 0

Else
        Set 'Kasa Controller / Color Christmas tree lights' On
        Set 'Kasa Controller / White Christmas tree lights' Off
        Wait 15 Min
        $s.Christmas = 1
Disclaimer:  I didn't test it, If you have problems I'll set it up here and see where it goes wrong.

try this:
"Pump Failure":   If CW Backup Pump Alert-sensor is ON,
                           
                             Run program "Pump Failure 2" (then)
                              Else No Action
Pump Failure 2:  If (none)
                            then
                            disable program Pump failure
                            wait 2 minutes
                            run program "Pump Failure 3" (if)
                            else (none)
"Pump Failure 3":  (disabled)
                              If CW Backup Pump Alert-sensor is ON,
                              Then Set 'CW backup Alarm ON (this is lamp link with red warning bulb)
                               Send Notification to Brooke email content 'Cold Circ Pump Failure'
                               Wait 10 minutes
                               Send Notification to Brooke email content 'Cold Circ Pump Failure'
                               enable program Pump failure
                                Else
                               enable program Pump Failure
 
The problem with your version is that a retrigger of the sensor starts the 2 minute wait over again.
I may actually be wrong about needing 3 programs, I'm not sure if a program can disable itself, in that case just disable the first program before the wait, but have the last program enable it both at the end of THEN and in the ELSE.
Edit:  I tested... you will need 3 programs, when a program disables itself it stops running.
When a program is disabled, it prevents its IF statement from working automatically.  However it can be run by another program.  Therefor Program 3 is always disabled.  Technically it doesn't matter, because it doesn't have an IF statement, but i would also disable Program 2 always.   Program 1 will be disabled by Program 2 to protect the wait, and re-enabled by program 3 in both the THEN and ELSE so that the alarm doesn't end up getting left turned off.

As @lilyoyo1 mentions you need to know the version of z-wave board you have.   IF you have a z-wave menu at the top of the admin console: use it to check the z-wave version.
If 4.55.00 you need 5.0.16C  (you mentioned 5.01.16 without a letter, which is possible, there's also an A and possibly a B, but the current release for 994's with a z-wave version of 4.55.00 is 5.0.16C.
If there is NOT a z-wave menu, or the z-wave version is 6.81.00 proceed directly to 5.3.4
In either case the upgrade is simple and will only take you a few minutes, no major changes that require manual intervention from your current position.
When you get back in after the upgrade make sure to check Help > About and make certain that firmware and UI versions match EXACTLY.

you may have a minimized or one pixel sized admin console.  Try these instructions to delete the .state files.

@Ross My guess is tthat your IoP is too old to show the button you need.

But there's a screenshot guide in case it's there and you missed it.   if you don't have that section on the config tab the best thing to do is work with support.

No.  In the admin console, Help > Manually upgrade ISY     
There you can load any version of firmware you want, to upgrade, downgrade etc.   After an upgrade/downgrade always make certain via Help > About that the firmware and UI version match exactly.  
The relevant firmware versions can be found here:  https://forum.universal-devices.com/forum/339-current-release-announcements/
Download the correct firmware file which will be a .zip and DON'T unzip it.  Just turn right around and upload the firmware file to the ISY via Help > Manually Upgrade ISY
NOTE: for each release there are two versions of the firmware file.  One if you have an Insteon PLM and the other if you don't.  You have an Insteon PLM and I believe (without looking) that is always the first of the two choices in each post.
 
 
 

Depending how old "several years back" is you need to determine if the z-wave is 300 series or 500 series.  Look at the back of the  ISY next to Port A.  Is there a circle there?  If there is shine the flashlight from your phone on it... is that curcle a Blue LED?  if yes, that's 300 series.  A 300 series z-wave board is only compatible with firmaware up to and including 5.0.16C.   Since you're not using z-wave you could also remove the board (take out 4 case screws, one is under a label, slide the case apart and unplug the board with the blue LED next to port A, close it up and put the screws back).
I'm not familiar if anyone has restored a 4.9 backup in 5.xx, if you did that you should upgrade the firmware to the lastest first, then try to restore the backup.   However the procedure I've seen mentioned here in the forums is to downgrade the firmware on the new ISY to 4.9, restore your backup, Backup again for good measure then upgrade to the latest and greatest. 
Upgrading to 5 isn't hard... and there's really only a couple things to lookout for.  Programs that use adjust scene won't upgrade correctly and programs that are intentionally disabled will become enabled again. 
If you load 4.9 firmware and restore the 4.9 backup you can also make a text copy of your programs.  Right click the "My Programs" folder in the program tree, pick copy folder to clipboard (at the bottom of the list), then paste the clipboard into a notepad window, and Save As.   This give you a reference to what your program looked like before upgrading.
After opening Version 5's admin consoles do three things first....  Open Help > About and ensure that the Firmware and UI versions match exactly.  If they don't fix that before going forward.  Second, Go to the Programs tab > Summary subtab... look for the color yellow... if you find any that program needs manual help, it didn't upgrade correctly.   third, if you had any purposely disabled programs, disable them again.

the "Play" button changes the context of the drop-down box.  Setting to a variables value won't actually work for scene type "Insteon", because the ISY is not a middle man in controlling devices.  There is a discussion here, on the various scene types.
As previously mention copy scene no longer exists, and yes it's a pain point.  Fortunately once a scene is configured you rarely need to change it.
And before you get stuck or complain... the GUI has a function that is NOT intuitive.  When updating a device's properties, change the dropdown value, THEN push the button on the LEFT of the dropdown to write the change to the device:

"On", "Beep", "On Level", "Ramp Rate", "Backlight" are actually the Set button for the dropdown to it's right.  Set the value, then press the button on the left.

Are you using the default mail server? or do you have server details filled out?   If you have server details filled out, does the From box have  name:emailuser@example.com specifically that is two fields in one.... name, a colon, and an email address.
are you filling out FROM in the custom content?  if so, leave that field blank

@johnmsch there is a default server mail fix between 5.3.0 and 5.3.4 that's the first place to start.  report back after that.  it's an easy upgrade, nothing special to do, back up, load the new firmware and wait for the reboot.

yes

NodeLinc has a datalogger.  you'll need a pi to run it tho.
Home Assistant with the Universal-Devices integration does some logging automatically, I haven't yet figured out how hang onto it, like temperatures that I want to record long term.  (haven't spent much time on it yet, but do have it on a list of things to learn/figure out.)

Correct.
From the wiki documentation for Google Home:
For Programs:
Turn On: “Ok Google, turn on the kitchen light” - runs Then Turn Off: “Ok Google, turn off the kitchen light” - runs Else However, if you wish to test a condition just link to another program.
For example make the Then body that google home Runs simply be a single line:
AAAADelete - [ID 0135][Parent 0001]
If
   - No Conditions - (To add one, press 'Schedule' or 'Condition')
 
Then
        Run Program 'BarnOHD' (If)
 
Else
   - No Actions - (To add one, press 'Action')
You'll actually need to create the second program first, so that it can be included in the Then. 
Also the second program can be disabled, so that it won't run from any condition in it's IF statement.  Disabled programs still run when run by another program.
 
 

Looks like he was migrating from V2 of the skill to V3... but he's really late to the party as V3 has been around at least 5 years from my memory.
 
Was the new voice entry made after the devices appeared in the app?  if so you need to tell her again "Alexa, Discover Devices" to have the new entry discovered.
But if the error is the title, then it's something else.  In the portal click "my profile" in the top right corner and make certain the correct ISY is selected in the dropdown, and that the UUID entry for preferred is correct.

You cant pick your own colors, only choose between a few theme's under File > Theme's
the pink/purple color is complained about a lot, but sadly it's still used.  On thing that Improves it's readability greatly is to increase the font size, but don't use font size 14... it doesn't format drop-downs in Programs correctly (the others work tho).

Try deleting these temp files and see if that resolves your issue, probably just the 2nd and/or 3rd would do it, I usually just search udi_* in that Temp directory and nuke em all.
find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.* file patterns:
udi_tree.state udi_frame.state udi_pgm.state udi_finder.state udi_launcher.state

the current version of locative still works fine with the portal.  I'm using it.
 
out of date info.  you don't need IFTTT
---
it sounds like you have locative set up correctly if you are seeing Enter and Exit events in the portal.  Have you restarted the admin console?   It requires a restart after the portal node server adds nodes to the ISY.  Do you see your portal Node server nodes? 
The look like this in the device tree: (white background because I'm not using the default admin console theme).
in the admin console.   "Home" is whatever you named the node in Step 4
 

Create scenes.  For example, my outside lights operate using 4 scenes:  Day, Evening, Late night, Bright
Each scene contains the same devices, AND the KPL buttons for the other 3 scenes. The button to turn the scene ON is a controller, the other scene buttons are responders.  Set the KPL buttons as "non-toggle On"  When I press Bright for example the other 3 buttons will be turned off as the actual lighting devices are set for bright mode.  
("day" is known as day and not known as off, because there's an outdoor outlet that turns on in the daytime.)

Late night is a repeat of the above with the last node as the controller. 
(note: It's an admin console screenshot, just without the blue background.)

Did you download a new copy, that's what you should do:  https://isy.universal-devices.com/start.jnlp
Of course official Java 8 must be installed first:  https://www.java.com
 
Finder not found is misleading?  start.jnlp installs the ISY Launcher, the first thing that Launcher launches is ISY Finder, If the ISY Finder window is opening but but saying not found, it's suggesting that perhaps the ISY is not on the same network as that computer.   This is often caused by people plugging in old routers in other parts of the house without changing the old router to an access point first.  Doing as such results in 2 networks in the home, one behind the other.  There are also other networking mistakes that can cause problems, but that's the most common and easiest to describe.

Study the ISY Cookbook--- a 692 page pdf of the examples you seek!

It looks like the node name changed.   ${sys.node.n004_temperature.ST} replace the RED portion with the white text from your screenshot n004_78633 (if I'm correctly reading the screenshot)