Techman

@Michaelco Try doing a "restore devices". This will write the all the device link tables to the plm. If you have any battery operated devices then disable automatic write to battery devices before you do the restore.

I'm not aware of any way to clean the internal contacts in the ISY994. Have you tried rebooting the ISY. The problem you're having might be related to an issue with one of the configuration files on the SD card.. The eisy uses solid state memory, the specs are attched

It's possible that your SD card is failing. One thing you can try is removing the card and cleaning its contacts with a soft eraser. If that doesn't help then you may want to replace the card. The configuration is stored on the SD card. Make sure you have a recent and viable backup. What is your ISY firmware version. How old is the ISY?

Clear your java cache, be sure to check all 3 boxes, the download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp This will place the IoX Launcher icon on your desktop

I'm running the exact configuration on my eisy and all the weatherflow data shows up after a reboot. I have the Tempest, firmware 181. The hub is firmware 194 Weatherflow node server is version 3.0.30

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.

@twired I just took a look at my open/close sensor and noticed that the heartbeat status was also blank, so I replaced the battery and it was still blank. I put the sensor into the linking mode and did a restore device. Now all the sensor nodes are reporting. For some reason, prior to the restore, the admin console was not seeing the device status but UD Mobile correctly displayed the device status after the restore.

@twired Yes, you should update your firmware and UI 5.8.4. It contains bug fixes and improvements. If you're not getting a heartbeat signal then it's possible the battery needs to be replaced.

The light module and the keypad should both be a controller in the scene. You might also try doing a restore device on both the module and the keypad. Is the module included in any programs or just the one scene? If you're still having issues you may want to try deleting the scene and then recreate it.

When using a serial PLM with either the Polisy or EISY it requires a serial to USB convertor cable (see link below). The USB PLM uses a standard USB cable. Serial PLM Kit - Universal Devices (universal-devices.com)

As of 6/01/2023 modules can no longer be added to the ISY, however you may be able to transfer your modules for a fee. Contact UD Support Final Goodbye to ISY994 Series - Universal Devices - News (universal-devices.com)

@terrylund You can add a stock USB extension cable to the convertor cable if you want to increase the distance between the Dongle and the EISY.

Restoring a PLM uses the plm address information from the backup. Your backup contained the address of your old PLM When replacing a PLM you need to follow the Replace PLM Procedure. See attached. Replace Modem (eisy_polisy).pdf

"Cannot determine Insteon Engine" means that the PLM is unable to communicate with the device. If you're adding a device it could be that you entered an incorrect device address, or you have poor communications between the device and the PLM. Take a look at the following article(s) INSTEON: Troubleshooting Communications Errors - Universal Devices, Inc. Wiki (universal-devices.com) INSTEON: Troubleshooting Communications Errors - Universal Devices, Inc. Wiki (universal-devices.com) Can't Determine INSTEON engine (youtube.com)

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.

@arzoo Make sure all your variables are STATE and not INTEGER Also verify that all your variables in the programs are correct, and their state is correctly shown in the variable setup

@awzulich You can also try clearing your java cache, be sure to check all 3 boxes, then download the IoX Launcher: https://isy.universal-devices.com/start.jnlp If that doesn't resolve the problem then try clicking on FILE | RESTORE DEVICES.

It sounds like the PLM isn't communicating with the Eisy. In the admin console, under TOOLS | DIAGNOSTICS | PLM INFO, does it show the PLM as connected? Is the green LED on the PLM lit? Are you using a serial or USB PLM?

It appears to be one of your programs that runs hourly that's causing your issues, there's no other explanation. Take a close look at each of your programs for your alarm

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

It's difficult to diagnose your problem not knowing what you did or didn't do both before and after you replaced the PLM. Your ISY firmware and UI are not current, but for now I don't think you should update. If you click on TOOLS | DIAGNOSTICS | PLM INFO, does the plm address match that of your current PLM? Clear you java cache, including checking all 3 boxes, then download the current IoX Launcher (the admin console) from here: https://isy.universal-devices.com/start.jnlp You can also try clicking on file, then RESTORE DEVICES.

Hi eric In order to help you please answer the following questions What is your firmware and UI versions Do you have a current ISY backup that was made prior to replacing your current PLM Are the devices that you mention died the older single band or newer dual band devices. How old is your ISY and have you ever replaced its SD card Did you exactly follow the replace PLM instructions ( see attached). It's highly unusual to have the numerous PLM failures that you're experiencing. Replace PLM.pdf

In the admin console, under HELP | ABOUT

It really appears to be a program that's causing your problem. Before you start replacing anything you should disable blocks of programs to try to narrow down the possible offending program. Keep in mind that if a program is disabled and another program calls up a statement in the disabled program, that statement will run even though the program is disabled.

What is your Polisy firmware and UI version?