Techman

When you add a Zwave device to the eisy you'll most likely end up with extra nodes that you don't need. The reason being is that, unlike Insteon,  zwave devices are designed to work with various Zwave hubs, and each hub may require and/or support these extra nodes.
What most of us do is create a folder and move the nodes we don't use into that folder which will give you a cleaner device tree.
I've attached 2 files that may help explain associations. Being that the eisy already supports scenes you most likely won't need the associations or scenes nodes that the device installs
Z-Wave Association-Basics.pdf
Zwave Groups and Associations.pdf

Are you running tha latest version of PG3x (3.2.7)?
What is your Polisy firmware and UI version?
Are you obtaining your Weatherflow data locally from the Hub or remotely?
The Weatherflow data should automatically populate your Polisy after a reboot.

What you're experiencing is correct. The backup process was modified in the 5.8.4 firmware. It now takes about a second for the backup to write to your harddrive.

When you clear your java cache make sure that all 3 boxes are checked, then download the IoX Launcher from here:
https://isy.universal-devices.com/start.jnlp
This will then place the icon on your desktop

Attached are a couple of articles that may help you troubleshoot your issues.
Zwave repair terms.url Zwave comprehensive guide.url

Try removing power from the eisy for a few minutes then boot it up.
If that doesn't resolve the issue then it's best to submit a support ticket

@GHenry
It appears that the battery level may not be reported until the level changes. You can also try waking up the sensor by holding the set button down for 3 seconds then query the sensor.  If that doesn't work then contact Aeotec support, they're very responsive.
The folllowing is from Aeotec
Battery level will be checked every time the device wakes up. These includes the wake-up timer, motion trigger, button click. When the battery state changed, a battery report command will be sent to the controller
Engineering Spec - Aeotec TriSensor 8.pdf

@GHenry
Take a look at this thread
Support Thread: IoX v5.8.4 (June 27, 2024) - Page 2 - IoX Support - Universal Devices Forum (universal-devices.com)
 

Try bringing the devices closer to the the controller. 
On the tri sensor 8, click on write updates on your controller,  then hold the set button on the sensor down for 3 seconds, the led should then blink blue once, and the writes should take place.

If you're adding it with S2 authentication then it's is looking for an access code.
Try adding it using S0 (no security) which also draws less battery current over the life of the battery.

@bbuchanan99
It's best to send an email to:
            sales@universal-devices.com 

@TVC15
When you clear your java cache be sure to check all 3 boxes. 
Download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

Use HTML instead  of text
For line feeds insert <BR> at the end of the line.

On the bluetooth service select ENABLED, then click on the SERVICE button to the left. If that doesn't work then go into PG3 and restart the bluetooth service.
Once the service is enabled click on "Scan for Bluetooth Devices"

Clear your Java cache, checking all 3 boxes, then download the IoX Launcher from here
https://isy.universal-devices.com/start.jnlp

I think the only limitations you'll face are on the PLM which has a limit of about 1000 links. 

The data for the Zwave, Zmatter, and Zigbee devices is stored on the Zmatter dongle.  The question is if your remove the dongle how will the device tree respond to those devices that are no lonnger accessible. 
If your zmatter board is mounted in the external enclosure You could unplug it and see what happens. I would assume that the device tree would show those devices with a red exclamation mark.
If you mount an already populated zmatter dongle in a different controller the device tree, and associated programs probably won't show the data on the zmatter dongle. I'm not sure if there's a way to do a sync and update.
Probably best to open a ticket 

Clear you java cache, be sure to check all 3 boxes, then download the IoX Launcher from here:
https://isy.universal-devices.com/start.jnlp
You shouldn't be extracting any zip files associated with the ISY
 

There was an earlier firmware version bug that disabled the programs. it has since been fixed.

Probably best to submit a support ticket to see if the bios needs updating / replacing

$39 for two years

If you do a restore device. the link tables in the device will be rewritten with the link tables that are stored in the eisy.
You can check and/or verify your device link tables using the diagnostic option in the device's right click menu
i.e. show device links, after the table populates click on compare. That will compare the links stored in the eisy with the links stored in the device. If there's a link mismatch it will highlighted.

What error are you getting?
Not sure what you mean "upgrade the PLM from OTA"  There are two PLM models, a Serial and a USB. 
Did you follow the "replace PLM procedue"? (see attached file) Note: this is for the ISY994 but is basically the same for the Polisy and EISY
Replace Modem.pdf

If the address is unavailable your other option is to put the device into the linking mode, the controller will then see the address. You can do that without having to remove switch plates.

Why not have a program set variables, one for armed stay and one for armed away.
A program could look at the variables to determine the state of the system, and then reset the variable when the system is disarmed.