Techman

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?

What is your EISY firmware and UI version

If you run the Topology report, The scenes, along with their scene number and the members of the scene can be found at the bottom of the report

It could be a combination of the low battery in the motion sensor and one or more running programs. You should disable all the running programs in an effort to narrow things down

@arzoo Not sure if this has been previously mentioned, but in the program summary tab look for programs that ran or finished about 52 minutes past the hour. My guess is that it's one of your heartbeat prorgrams that runs hourly.

@bconen Your PG3x and eisy firmware are all current. It probably best to open a support ticket and attach the debug log . https://www.universal-devices.com/my-tickets

The log show that the Audio Player is trying to load a missing module, "pyaudio". From the PG3 window, delete the audio player, reboot you eisy, then reinstall the audio player Let me know if that resolves the problem.

Usually rebooting the EISY should resolve the connection issue. What is your audioplayer output connected to? Download the audioplayer debug log and post it in the forum What are your eisy firmware and UI versions?

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

@62vetteefp Here's the link for the IoX Launcher (admin console) https://isy.universal-devices.com/start.jnlp

@paulw Verify that you're connected to the internet. Try accessing the admin console via the cloud to verify that you're connected. I believe the from field needs to be populated The from field format should be: ISY:(your email)@gmail.com

The format the IOLinc uses is not a bug. It's most likely built around the alarm system format which uses NO (normally open) contacts. When the alarm system is armed all the contacts are closed. If a contact is opened or the wire to the contact is cut, the contact reverts to the NO state thus triggering the alarm. This is the protocol (NO) the IOLinc uses. I'm not familiar with Home Assistant but they may not follow that protocol. With UD controllers, nothing has changed over the years, why you didn't experience this with your Polisy may be the way your program was set up, or maybe you used trigger reverse and didn't run the 3 am query.

Your motion sensor (14 72 B6) appears in almost every log entry, so chances are this is the device that's causing you problems. Disabling the device does not stop it from sending spurious data into the Insteon network. You need to remove its battery in order to completely disable it. You should also look for a program that may be running around the time of your issues

It's possible that the default mail server is down. It's probably best to use Gmail. For Gmail setup take a look at this wiki article: https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings

If you use a Normally Open reed switch, and don't enable trigger reverse, then the green led on the IOLinc will be on when the door is closed (when the magnet is in contact with the reed switch), the 3AM query won't then affect the status. This is the way it has always been with UD controllers.. There hasn't been any changes in the IOLinc or the controller firmware that would affect the device status.

Are you using a reed switch and magnet to trigger the IOLinc, if so is the switch normally open or normally closed?

Can you expand on what you mean by synchronizing them. What is it that you want to do with the KPL?

I just took a look at one of my programs that has a 15 minute wait and the LAST RUN TIME and the LAST FINISH TIME show the 15 minute difference. Not sure why you're not displaying the correct finish time. Are there any other conditions in your program? What controler and firmware are you running?

What version of PG3 were you running prior to the upgrade

Are you currently running PG3x 3.2.27 and IoX 5.8.4

A restore would not transfer Zwave to the new controller, migrate does. If your Polisy is running a different firmware version than the Polisy, the Polisy firmware could be downgraded by using the ISY994 firmware which may not be compatible with the Polisy. There are probably additional factors, but these are two that come to mind.