Techman

What else is, or supposed to be, linked to the device that now has less links. i.e. scenes, devices, etc. Are your scene tests now working? Take a look at any related programs. It's possible that some devices are not properly represented in the programs.

There are some known update bugs. See the July 21st post above.

Being that you used houselinc it's possible that it is somehow linked to your ISY and got migrated to the eisy. If you factory reset the PLM does it still show as houselinc prior to doing a restore PLM? If not then it's possible your ISY backup file may have some issues.

I'm using a USB PLM with the eisy and had no problems migrating. You should contact Insteon support for an explanation. HouseLinc is a discontinued product that was supported by Insteon. It sounds like you got a used PLM that was previously linked to a HouseLinc product. They should replace the PLM. They're very responsive. What's the 4-digit date code and version number on your USB PLM?

Try doing a restore device on all the devices in your scene, then do a scene test. Did that resolve the error? Most newer devices will not respond to an all on as that function has been removed. Are you using the same PLM that you had installed on the ISY? Your issues are not typical, and may be related to an incomplete migration.

The eisy only supports a PLM via one of its USB ports, thus the USB PLM would be the first choice. You can use a serial PLM (2413s) with the eisy if you use an USB to serial convertor. UD has a convertor kit available on their store site. If you factory reset the PLM it would have no effect on you name and password. Where did you purchase your USB PLM? Did you try factory resetting the PLM and then doing a restore Modem?

What controller and controller firmware version are you running? When you change the ON level you need to click on the ON Level button to the left of the level setting?

It appears that your USB modem was previously linked to another controller. Did you buy it directly from Insteon.? Try doing a factory reset on the PLM, then a restore Modem.

When you get the instructions from Zooz can you post them on the forum. Glad to hear you're close to getting it resolved.

Are you using the Zooz 700 USB controller on the Polisy, if so, is there a reset button on the stick? If not then read the link below. You'll may have to use the Silicon Labs Simplicity Studio software How to factory reset Zooz ZST10 Zwave stick? : r/homeassistant (reddit.com) or contact Zooz support: New Ticket - Zooz Support Center (getzooz.com)

@mikeorst The 5.6.3 firmware is still viable. Are you on a Polisy or eisy?

@bob123 When you restored your ISY backup to the Polisy, did you first backup the Zwave on your ISY? If not then it may have restored your older 300 series Zwave file to the eisy which is why it may not be working. It that's the case you may have to rebuild your Zwave from scratch on the Polisy.

The link tables look good, and your communication between the MS and the eisy is good being that you're able to read the link tables. Try deleting and recreating your program.

Your device link tables are corrupted. Did you try doing a restore device? Also do a show device link tables for the eisy. If the eisy link tables for the KPL are corrupted, then you you'll have to delete the KPL from the eisy and re-link it.

@MarcusD Support for the ISY994 ended on 6/1/2023. You can no longer add modules to the ISY. Your only option is to move up to the eisy.

@bob123 Did you check, and save, the Zwave box under the configuration tab? You should also update your Polisy firmware to 5.6.3 Once you get Zwave up and running be sure to do a zwave backup.

To put the MS into the linking mode you need to hold down the set button for 5 seconds. When it's in the linking mode its red led will steady blink. The MS will stay in the linking mode for 4 minutes or until you tap the set button twice. Once a MS is in the linking mode do a restore device. Note: The MS won't detect motion when in the linking mode.

The red ! means that the eisy is unable to communicate with the device. Try rebooting the eisy then do a restore device on each KPL. If you're still having problems then you may have something on your powerline that's causing interference.

I'm not sure what would be causing those errors. Try updating packages, and then a reboot. If you then still have those errors you should probably submit a support ticket. Also take a look at those two programs and make sure that there's no errors in the syntax.

5.6.3 is the current firmware version. Did you exactly follow the following migration instructions: Eisy:User Guide - Universal Devices, Inc. Wiki (universal-devices.com)

It's possible that during migration individual programs can get corrupted. Open each individual program associated with your devices and make sure that the program data is correct, then save the program. If everything looks OK then reboot the Polisy/EISY. Keep in mind that after a reboot the device status window may not display data until the device changes state.

What controller are you using. What's its firmware version? What did you migrate from and to? You can also try saving the associated programs and do a reboot of the controller.

If right clicking on the KPL, and then clicking on "write updates" doesn't resolve your problem you could try a factory reset on the KPL then a restore device.

It's possible that the eisy is updating its packages, which can sometimes take a while. At this point I would let it sit, with hands off, and update for an hour. What firmware version is the eisy on?

The MSII is the only Insteon motion sensor available. It's not that new, it has been out for several years. It works with the ISY but has some limitations. It runs on either batteries or 5v USB power. Currently the only other viable option is Zwave motion sensors.