Techman

The "version" in your admin console is blank and it shouldn't be What controller are you using and what is its firmware version Try clearing your java cache, be sure to check all 3 boxes, then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp Also try removing power from the controller for about 30 seconds

The Zwave/Matter module supports up to the 700 series. It's supposed to support LR but I'm not sure if it has been implemented.

The zmatter module is supposed to support Zwave LR. However, when installing a zwave LR device I was never givren the option to use either LR or Mesh, so I believe they installed as mesh. Zwave LR by-passes the zwave mesh network and communicates directly with the Zwave controller and has a longer range than a non LR device Here's an article explaining LR All About Z-Wave Long Range - The Smartest House

Any zwave device that's zwave certified should work with the eisy. I have numerous Zooz devices and they are all compatible with the eisy. The ZSE50 is zwave certified.

@tracknut The eisy doesn't support a static address, only reserved addresses. Make sure DHCP is enabled on your router The PLM would be a non issue, so don't focus on it.

What controller are you using, and what's its firmware version?

@zorax2 After you get everything working and cleaned up do an eisy backup. Anytime you update firmware, devices, or programs always do a backup, it only takes a few seconds. You should also update to the current firmware which has bug fixes and program improvements

If the 2334 Switch added then your PLM and its connection is good. How old was the backup that you used to do your restore backup with? Was that backup made with your current PLM? If you backup is current then you can try doing a factory reset on the PLM, then a Restore PLM

In your browser enter https://eisy.local:8443/WEB/sysconfig.txt In your config settings, what are your versions for FreeBSD,UDX, and ISY

For the new 2477S you want to use "remove existing links. If you have the 6 digit device address, then in the linking window enter its address. The switch will then show up in your device tree with its address Right click on the old switch, then click on "replace with" and select the new switch. All your old switch data will be transferred to the new switch

What's the voltage and current rating on the failed power supplies?

The "failed to add device, reason 3" I believe that error 3 is "Device returned invalid node" Being that you have the correct device address 36.B9.BF, you should try removing power from the eisy then try installing again, but first do a factory reset again on the sensor. When the sensor is in the linking mode (slow flashing led) is the led bright? Also take a look at your device tree to make sure the device wasn't previously installed.

"Cannot determine Insteon Engine" usually indicates one of two issues, either the device is out of range of the PLM or you're inputting an incorrect device address when linking

Here's the manual for the leak sansor 2852-222 Leak Sensor.pdf

@GDavis01 You need to press the linking button on the leak sensor for 3 seconds then the led will start fast blinking which puts it into the leaking mode. To exit the linking mode you need to press the button, wait a second then press it again. The led should then turn off When the sensor detects water the sensor will stay in the wet mode until you press the button once.

Did you select the S2 security option in the eisy when you included/installed the device, otherwise it may install as S0 which is why it didn't ask for a pin. Each time you add a zwave device the eisy device id will increment by one number, i.e. zy002, zy003, etc. The SMCO410 will install several nodes, one for smoke, battery level, CO2, etc. When you first add the device the nodes in the eisy may be blank until you press the test button on the detector eisy config files cannot be edited.

Are you using the"TREND(CHART)" that's in the tools menu. if so, I don't think that it was ever perfected.

Is the time showing the eisy correct? What is the make and model of your Zwave sensors?

Is your latest controller a Polisy or an EISY? What is your PG3 version? If they're showing as unmanaged in your current controller that means that they're still being managed by your previous controller. Log into your ISY Portal : ISY portal Make sure your current controlle is there and active Re: the admin console issue, did you clear your java cache and reinstall the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

One last thing you can try. For each device that was in the scene, do a restore device on each of them, then try deleting the scene. Scenes operate independently from the ISY, you could remove the ISY and the scenes would still work as the link tables for scenes reside in the scene and the devices that are, or were, in the scene.

Here's the link to replacing the card. They do have a tendancy to fail over time. The contacts on the card can also oxidize so you should first try cleaning them with a soft eraser. ISY-99i/ISY-26 INSTEON:Replacing/Formatting an SD Card - Universal Devices, Inc. Wiki Many years ago X10 made a poweline signal monitor which also showed noise on the powerline. Here's a couple of options: Monterey Instruments X10 Powerline Signal Analyzer - FREE SHIPPING | eBay XTBM / XTBM-Pro X10 Signal Meters - JV Digital Engineering

By turning off the breakers you disrupted the Insteon powerline signals. Keep in mind that other Insteon powered devices also act as repeaters. The problem doesn't sound like it's with the PLM. Being that some of the buttons worked correctly on the KPL leads me to believe that you have some invalid links in either the ISY or the KPL. If you have the ISY994 then the issue could be with your SD Card. They have a tendency to fail. What you can try is to remove power from the ISY, then remove the SD Card and clean its contacts with a soft eraser, replace it and power up.

Yes, do a search for the files

One last thing you can try. Close the admin console and then delete the following files which are located in the windows temporary folder. They will be recreated the next time you open the admin console

Strange that it won't delete, it's possible that the scene is corrupted. Try renaming the scene then deleting.