Techman

@Sparks Press the button on the front of the eisy once. That will update the eisy and pg3x. Wait about 10 minutes then log into the admin console and click on reboot in the configuration tab.

The ISY doesn't have an internal PLM, it uses the 2413S PLM which is connected to the ISY via the cable that was included with the ISY. The eisy doesn't have built-in Zwave, you would need the external Zmatter card and enclosure sold by UD. ZMatter USB: Z-Wave+ & Matter Module for eisy (Beta) - Universal Devices (universal-devices.com) The migration process is dependent upon your current hardware and firmware, i.e. do you currently have zwave, what is your current ISY firmware? When you get ready to migrate there are detailed migration instructions available.

HTTPS is more secure than HTTP because it uses encryption to protect information as it is being sent between clients and servers. If you were to use the cloud access rather than local, https provides better security

Updates from Ken - May 24 — Insteon

You could try uninstalling it, factory resetting it, and then reinstalling. What is the hardware device you installed, make and model?

The range extender, or any dual band plug in module, will relay the Insteon signal using both RF and powerline. It will also act as a powerline bridge if it's on the opposite leg of your powerline from another dual band device that's within range of the extender/module Note: any plug-in module is more effective than an embedded module because the antenna is free of obstructions compared to switches which have the antenna located in the rear of the switch.

Do you have the 300 or 500 series Zwave board in your ISY? Is your ISY firmware and UI the same version? Did you wake up the leak detectors before you tried Synchronize?

@vmastros Take a look at this wiki article regarding communication issues. https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors

@geddy I stand corrected. The node names, which had a prefix of ZW didn't change, but if I look at the actual node it changed to ZY

When I migrated from the ISY to the EISY all my Zwave nodes maintained their ZW prefix in the eisy except for a few nodes that didn't exist in the ISY but appeared in the eisy, such as "Scene Responder"

Are you still on a Polisy? What are your firmware and UI versions If a Z-wave node is blank or unresponsive, right click on the node, click on Z-wave | Synchronize | Update with interview. All the active Z-wave nodes should have migrated as ZW nodes. The ZY nodes either need to be updated, or are nodes that aren't being used, in which case you can create a folder called unused nodes,and move the unused nodes into it.

@dex Did your previous system have a Z-wave dongle installed?

@smokegrub Here's the link and instructions for the update. This assumes that you do not have Z-wave installed. Be sure to carefully read the release notes. After this update you'll be able to easily migrate to the eisy. 5.3.4 (ISY994) - Last release for ISY994 - Current Release Announcements - Universal Devices Forum (universal-devices.com)

5.6.0 is the current firmware for the eisy. If you can access the eisy from the admin console then the update has completed.

@BigMojo Thanks for the input. I've been running the ZRTSI on the eisy for several months without any issues. I noticed that your Binary Switch nodes are populated, mine are completely blank, not sure why UPDATE: I ran Update with Interview on the Binary Switch nodes and now they're populated.

eisy 5.6.0 When I run a scene test, some of my test results show "Link for xx.xx.xx Responder not Found" All the devices in the scene are included in the scene as controllers. Occasionally, one of the devices, a KPL button, fails to respond to the scene on or off command. The link table diagnostics for all the devices all show correctly. All the "not found" messages belong to KPLs Any thoughts on the "not found" message?

@TheA2Z Once the issue gets resolved, could you post the findings and resolution.

I've also noticed that some of my eisy battery operated devices are triggering programs, that email me their device status, when they shouldn't.

@MrBill I agree, probably needs a firmware tweak.

The 17001 are not errors but are informational messages. You can ignore them. My error log has them also.

If there is such a device, you could probably track it down from this site Catalog of Certified Z-Wave Products for U.S. / Canada / Mexico (z-wavealliance.org)

The parts you mentioned are all that's needed. I believe that the enclosure for the Zmatter board is currently out of stock. Instead of buying the cable kit you might want to buy a USB PLM, which is currently in stock at Insteon, either way is workable.

During zwave migration some zwave device nodes get either renamed or reconfigured. The Aeotec Multisensor 6 Humidity, which normally displayed in the main node window, got moved to its own node called Weather sensor. It's possible that your STATUS may have moved to its own node and /or got renamed.

If the battery level is displayed in a node, then all you need is a program and an email customization, to notify you when the battery level drops to a certain value. IF Door Window sensor Battery Level <60% THEN Send notification to Mobile content 'Low Battery'

You will have to manually wake up each of your battery-operated devices, in order to include/link them, as they go to sleep in order to preserve the battery. Your location should populate without any user input, if not there's a drop down menu. During migration the SMTP settings go to "default", you'll have to manually enter any custom settings.