Techman

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.

1. No 2. Yes, and you also need to save the configuration 3. S2 would be between the extender and the eisy. Not sure if the extender would communicate with a S1 or S0 device. Yopu can give it a try. 4. You can leave it on when adding S0 devices If you migrated from an ISY994 with an existing 500 Zwave board then both your Insteon and existing Zwave devices would migrate to the eisy assuming you followed the migration procedure.

@JTsao press the button on the front of the eisy once. That will update you to 3.1.26. After the update is complete, you'll need to reboot the eisy.

PLM link counts can vary due to system activity and other factors. You most likely won't see the same count between the ISY and the EISY

I rebooted after the first time it happened. I just tried a package update and reboot, so I'll see what happens going forward. The last time it happened it triggered my siren program at 3:00 am UPDATE: I traced the problem back to an 8 button KPL. The link tables were mismatched/corrupted. I did a factory reset and restore which seems to have fixed the problem.

Over the last couple of days, when my query all program runs at 3:00am, some of my programs get triggered without any logical reason. I'm curious if anyone else has experienced anomalies when the query all program runs.

You're on the right track, assuming you don't have Z-wave Your ISY must have the latest the latest firmware, 5.3.4 and have a current backup Update the packages on your eisy prior to migration and follow the migration guide below. Eisy:User Guide - Universal Devices, Inc. Wiki (universal-devices.com)

@JSylvia007 The Multisensor 6 is fully compatible with the Zmatter board. I tried the Multisensor 7 and had issues including it, so I'm staying with the MS6 When you use the zmatter board with the MS6 the humidity displays in a separate node so you may have to modify any programs that use humidity.

@SSS You can't have two controllers running in parallel. A device can only be linked to one controller at any one time. When you migrated to the eisy the address of the new USB PLM replaced the serial PLM address in all of your devices.

First, Backup up your ISY Z-wave, make sure your ISY has the latest firmware, 5.3.4. then do an ISY backup Prior to migrating to the eisy, update the eisy firmware. If you follow the migration procedures below, everything should go smoothly. Eisy:User Guide - Universal Devices, Inc. Wiki (universal-devices.com)

Take a look at this thread ISY User Manual for Motion Sensor II (2844-222) - ISY994 - Universal Devices Forum (universal-devices.com)

I currently don't have an ISY994 hooked up. Here's the instructions from the ISY Cookbook: Manually Upgrading Your Firmware • The downloaded firmware MUST remain zipped. DO NOT unzip the downloaded file. • Please ensure you have a good backup before attempting a firmware update. • Disable all anti-virus and firewall software before attempting a firmware update. • Be sure to run firmware updates from a stable and, if possible, hardwired network connection. Avoid running firmware upgrades from marginal wifi connections or off-site locations if possible. • Once downloaded, click the HELP pull-down menu, then MANUALLY UPGRADE, and browse to the firmware file you have downloaded. • After upgrading your firmware, please close all browser windows and clear your Java cache as outlined in section 23.6 Clearing Java Cache

@oamber The 5.3.4 update will download as a folder, which you should place on your desktop and do not remove any files from it. When you select manually update from your ISY994 you should point to that folder. You should also do a factory reset on the eisy as you may have loaded incompatible data in your previous attempt to migrate.

@oamber Here's the link for the firmware, The update from 4.9.0 to 5.3.4 requires some user intervention. Be sure to read and follow the release notes. 5.3.4 (ISY994) - Last release for ISY994 - Current Release Announcements - Universal Devices Forum (universal-devices.com)

Did you update your ISY to the 5.3.4 firmware and UI prior to the migration, it's a must. You also need to update the eisy firmware If you're using your serial PLM did you connect it using the serial to USB conversion cables?

Be sure to check, and save, the Z-wave support box in the admin console system tab. To add a Z-wave dsvice to the eisy, in the admin console click on z-wave | add a Z-wave device, then put your device into the linking (wakeup) mode by short pressing the action button. Once it's linked the device led will remain lit. The include (z-wave interview) process can take some time depending on the device.

On your PROGRAMS tab, click on SUMMARY. there you'll find a column titled RUN AT STARTUP. Right click on the program and click on ENABLE RUN AT STARTUP

Other than the documentation that came with the MS, I haven't seen anything additional. Once the MS is linked the only options are what show up in the admin console. Basically, what you see is what you get.

@mdarcy If the above suggestions don't work, try putting one of the leak sensors in the linking mode, then do a restore device.

@boonest In windows If you go to control panel, programs and features, do you see Java? If so, uninstall it. then download the 32 bit version from the Java site. I had a similar issue after updating Java, and the above resolved it.