Chris Jahn

If you are up for some low-level debugging ... I'm not sure if you are able to use ssh and scp to get to Polisy, but if so, please do the following: 1) From ssh > tail -f /var/isy/FILES/LOG/ZWAY.LOG > mylog.txt 2) Restart ISY 3) Open the Admin Console 4) Exclude a device 5) Add a device 6) wait for it to finish, hit ctl-c in ssh, and then send me mylog.txt

Did you get a similar message for all the devices you added? Please do the following from a browser and send me the output: http://<yourIsy>:8080/rest/zmatter/zwave/dh/node/2/cc/0

Just reproduced the bug .. apologies, it was introduced in this build. Will be fixed for the next one. As a workaround, you can use a programs to change them until the fix is available.

Thanks, we reproduced the bugs and fixed them for the next build.

I think by accident one of the source file changes we made for this didn't get put back in time for this build. When you click 'Show Native Links', you should see a popup window containing all the possible links (not the event viewer). Apologies, it will be available in the next build.

It allows you to quickly see all the native links available for one or all of your Z-Wave controllers. Normally you have to create a scene and then look at the link options between a Z-Wave controller and a Z-Wave responder to see if a native link is available.

It depends on the use of the configuration parameter by the device and is really just for ease of use. Using unsigned (positive only) numbers is only really needed when you have to supply a very large value.

Technically 3 is not valid in Z-Wave, but I'll put it back because there are obviously some devices using it.

The steps to create a native link if ISY detects that an association is allowed: 1) Add the Z-Wave responder DEVICE A to the scene (may be added as a controller or responder) 2) Add the Z-Wave controller DEVICE B to the scene (must be added as a controller) 3) In the Device tree under the Scene, select DEVICE B 4) In the table of responders select DEVICE A 5) If an association is available between DEVICE A and DEVICE B then you will see a 'Z-Wave' entry as one of the link options.

In this case, you are specifying the scene itself as the controller (i.e. "Scene test") and thus it represents the ISY which already has associations set up so you won't see the 'Z-Wave' entries in the list. In the device tree, you must select the actual Z-Wave controller inside the scene (e.g. "ZW 005 Binary Switch"), and then select the responder from the list of responders (e.g. "ZW 006 Binary Switch"). If the ISY has detected they are association compatible you will see the 'Z-Wave' entry in the link types available.

The ISY will create one or more 'Z-Wave' entries in the link types for nodes that the ISY see's as compatible for association. This means: 1) The controller node sends either Basic Set, Binary Switch Set, or Multilevel Switch set command 2) The responder node supports the type of command the controller sends it (i.e. Basic Set, etc.) 3) Both the controller and responder are linked to the ISY at the same security level (i.e S0 security or no security) You may have to create a Basic Node (right+click node, Z-Wave | Add/Refresh Basic Node) for a device and use it as the responder.

Haven't been able to reproduce the problem, but, if you have Insteon Enabled with no PLM, it may take a couple of minutes or more before Z-Wave is detected and available.

The query button only queries the device status, not the configuration parameters. To see and query the configuration parameters, right+click on the node in the device tree and select Z-Wave | Set Configuration Parameter. A popup will appear allowing you to set or query a configuration parameter. More info: Z-Wave node submenu

Hello, The maximum number of programs + folders is 2048, and the maximum number of conditions/actions for all programs combined is roughly 10000-12000 (this can vary depending on type of conditions/actions used).

Could be one of a few possibilities .. it looks like there is no event occuring that is causing the program to run (i.e. manually doing a 'Run Then'), or, for some reason we are not properly storing the event with the program, or, the event gets cleared from the program prior to the NR being used. We'll take a look at it, and hopefully reproduce the problem here.

OUTDATED - This version has been updated and is obsolete. Please see the current release found in the Current Release area of the forums. Please note: As part of Z-Wave Certification, the ISY-994 5.x series no longer supports the 300 Series Z-Wave board. Please check your upgrade discount eligibility and ordering instructions. If you have any other questions, please submit a support ticket Hello, The 5.3.3 *Test Build* is now available. As part of Z-Wave Plus certification, some incompatible changes were made that may cause issues when migrating from older versions of the ISY. We are looking at mitigating these issues in future builds. If you have a stable working system, you may want to wait before migrating. Guides Z-Wave Plus for ISY-994 Getting Started Z-Wave Plus for ISY-994 User Guide Z-Wave Plus for ISY-994 Advanced User Guide Notes - Upgrading to this version may require a lot of manual intervention including verifying scenes, programs and program settings are correct. In some cases it will be easier to rebuild your network. - If you are rebuilding your Z-Wave network, it is recommended that you Factory Reset the Z-Wave dongle prior to adding devices back into your Z-Wave network. - If you are upgrading from version 5.0.10 or earlier then Devices and programs are migrated in the current version. After upgrading: o Please ensure your device nodes and programs are correct; in some cases you may need to update them. o Wakeup your battery devices after the ISY has restarted and the initial query has finished - If you are upgrading from version 5.0.8 or earlier, you will have to manually update the Adjust Scene entries in all of your programs. - Starting in version 5.0.15A, the event value for the Low status of Insteon FanLinc Motor changed from 63 to 64 - If you have the climate module, please go here to choose a new weather service. Important User/Password changes: - If your current version is 5.0.7 or earlier, then after installing 5.0.8 or later your userid and password will be reset back to the system default. - If you restore a backup created from 5.0.7 or earlier, your userid and password will be reset back to the system default. - If you downgrade from version 5.0.8 or later to version 5.0.7 or earlier then after installing version 5.0.7 or earlier, you will have to Factory Reset the ISY and optionally install a backup taken in that version or earlier. Java runtime memory (when Admin Console is very slow to respond) - If the admin console is slow to respond, it is likely you need to increase the amount of memory allocated to the Java runtime (JRE). - Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following: o -Xmx512m - Press Ok to close the window, then Press Apply to save the changes Fixes in this build: 0000778 - Admin Console fails to start in rare cases 0000779 - Additional logging to see when programs become enabled/disabled Notes: - SSLv3 is now disabled. All models now support TLS1.2 and high grade cipher suites - 4.1.1 backups may corrupt Z-Wave configuration in case they are restored. 4.1.2 and above releases fix this issue - See our Wiki for additional information (e.g. Program Variables) Prerequisites: - If your ISY version is currently 4.x.x then it must be version 4.6.2 or higher (upgrade if necessary) before upgrading to 5.3.2 - The latest release of Java must be installed - If you are using MAC Yosemite and Java 1.8.40, please follow these instructions Install: 1. Backup your ISY (File | Backup ISY) - Do not backup from a version 3.1.6, or 4.1.1 system (there were bugs in those versions that caused the backup to be corrupted) 2. Make sure you have done everything in the Prerequisites section 3. Download firmware - ISY 994i Series including Z-Wave support - ISY 994i ZW, Z, or ZS Series (Z-Wave/Zigbee and/or if you do NOT have a PLM) 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file downloaded in step 3 6. After the upgrade, You must clear your Java Cache 7. Launch the 5.3.0 Admin Console and/or Dashboard by going to the following link: - https://isy.universal-devices.com/start.jnlp Note: If you have version 5.0.8 or lower installed on your ISY, then use this link instead: - http://isy.universal-devices.com/994i/5.3.3/admin.jnlp Note: MAC 10.6.x users must use the following links instead - http://isy.universal-devices.com/994i/5.3.3/admin16.jnlp (Admin Console) - http://isy.universal-devices.com/994i/5.3.3/dashboard16.jnlp (Dashboard) 8. To launch the Admin Console directly from your ISY, go to the following link: - http://your.isy.ip.address/admin.jnlp 9. If you are using Z-Wave and upgrading from a 4.x.x or earlier version of the ISY, see Z-Wave migration from 4.x.x branch below 10. Backup your ISY (File | Backup ISY) Z-Wave migration from 4.x.x branch All Z-Wave nodes will be recreated when migrating from 4.x.x. Some nodes will have different addresses, and some devices will have a different set of nodes. In some cases, it is easier to rebuild your network rather than migrate. 1. Before moving to 5.3.0, in 4.x.x, Backup your Z-Wave Dongle and then Backup your ISY. 2. Replace the 300 Series Z-Wave board in your ISY with a 500 Series Board 3. Install 5.3.3 4. Start the Admin Console and Restore the Z-Wave dongle (will take the Z-Wave network you backed up in step 1, and writes it to the new 500 series board) 5. Do Z-Wave -> Synchronize Nodes -> All - Do not open ‘Programs’ tab until step 6. - This will add back all of the ISY nodes that were deleted at startup. - If you have multichannel devices, you will see more nodes added - After sync is complete, restart the Admin Console and go to step 6. 6. Open the programs tab - Most old Z-Wave device actions/conditions are automatically converted to the 5.3.0 framework - Make sure to visually check all programs that contain Z-Wave device actions or conditions. - Programs containing nodes from multichannel devices will have to updated - Node addresses for multichannel devices change from ZW003_143 style to ZW003_002_143 (where _002_ is channel number) - If everything looks good, save the program changes made by the migration. 7. Make an ISY Backup 8. If you are missing any Z-Wave devices you may have to exclude/include them again. For battery devices, make sure they have communications turned on and try doing a synchronize again.

The documentation in the Wiki was actually incorrect. I have updated it https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables#Elk_Variables The variable is actually elk.area.1.alarmState

Please do right+click on the node and select Z-Wave | Z-Wave Options | Custom Sensor/Button Press detection | Update Device Status Select No for the option, indicating that a button press for this node does not also mean its status changed. Here's the help text for it to give you a better idea of what is happening: Whenever a sensor has been triggered or a button has been pressed, the Z-Wave device sends out a message to the ISY, and possibly to other Z-Wave devices as well. For most switches and sensors the message also indicates the current status of the device. For example, if a switch sends an Off message then the local load on the device (e.g. a lamp) is also switched off. This option allows you to specify whether or not to use this value for the current status of the device.

OUTDATED - This version has been updated and is obsolete. Please see the current release found in the Current Release area of the forums. Please note: As part of Z-Wave Certification, the ISY-994 5.x series no longer supports the 300 Series Z-Wave board. Please check your upgrade discount eligibility and ordering instructions. If you have any other questions, please submit a support ticket Hello, The 5.3.2 *Test Build* is now available. As part of Z-Wave Plus certification, some incompatible changes were made that may cause issues when migrating from older versions of the ISY. We are looking at mitigating these issues in future builds. If you have a stable working system, you may want to wait before migrating. Guides Z-Wave Plus for ISY-994 Getting Started Z-Wave Plus for ISY-994 User Guide Z-Wave Plus for ISY-994 Advanced User Guide Notes - Upgrading to this version may require a lot of manual intervention including verifying scenes, programs and program settings are correct. In some cases it will be easier to rebuild your network. - If you are rebuilding your Z-Wave network, it is recommended that you Factory Reset the Z-Wave dongle prior to adding devices back into your Z-Wave network. - If you are upgrading from version 5.0.10 or earlier then Devices and programs are migrated in the current version. After upgrading: o Please ensure your device nodes and programs are correct; in some cases you may need to update them. o Wakeup your battery devices after the ISY has restarted and the initial query has finished - If you are upgrading from version 5.0.8 or earlier, you will have to manually update the Adjust Scene entries in all of your programs. - Starting in version 5.0.15A, the event value for the Low status of Insteon FanLinc Motor changed from 63 to 64 - If you have the climate module, please go here to choose a new weather service. Important User/Password changes: - If your current version is 5.0.7 or earlier, then after installing 5.0.8 or later your userid and password will be reset back to the system default. - If you restore a backup created from 5.0.7 or earlier, your userid and password will be reset back to the system default. - If you downgrade from version 5.0.8 or later to version 5.0.7 or earlier then after installing version 5.0.7 or earlier, you will have to Factory Reset the ISY and optionally install a backup taken in that version or earlier. Java runtime memory (when Admin Console is very slow to respond) - If the admin console is slow to respond, it is likely you need to increase the amount of memory allocated to the Java runtime (JRE). - Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following: o -Xmx512m - Press Ok to close the window, then Press Apply to save the changes Fixes in this build: 0000765 - alert.event in notifications is not formatted properly 0000774 - Green icon appears on Insteon Controller Node after using Adjust Scene 0000775 - Scene activation from node server controller node uses wrong responder attributes 0000776 - Update SMTP default settings 0000777 - Z-Wave button press control & status updates for switches Notes: - SSLv3 is now disabled. All models now support TLS1.2 and high grade cipher suites - 4.1.1 backups may corrupt Z-Wave configuration in case they are restored. 4.1.2 and above releases fix this issue - See our Wiki for additional information (e.g. Program Variables) Prerequisites: - If your ISY version is currently 4.x.x then it must be version 4.6.2 or higher (upgrade if necessary) before upgrading to 5.3.2 - The latest release of Java must be installed - If you are using MAC Yosemite and Java 1.8.40, please follow these instructions Install: 1. Backup your ISY (File | Backup ISY) - Do not backup from a version 3.1.6, or 4.1.1 system (there were bugs in those versions that caused the backup to be corrupted) 2. Make sure you have done everything in the Prerequisites section 3. Download firmware - ISY 994i Series including Z-Wave support - ISY 994i ZW, Z, or ZS Series (Z-Wave/Zigbee and/or if you do NOT have a PLM) 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file downloaded in step 3 6. After the upgrade, You must clear your Java Cache 7. Launch the 5.3.0 Admin Console and/or Dashboard by going to the following link: - https://isy.universal-devices.com/start.jnlp Note: If you have version 5.0.8 or lower installed on your ISY, then use this link instead: - http://isy.universal-devices.com/994i/5.3.2/admin.jnlp Note: MAC 10.6.x users must use the following links instead - http://isy.universal-devices.com/994i/5.3.2/admin16.jnlp (Admin Console) - http://isy.universal-devices.com/994i/5.3.2/dashboard16.jnlp (Dashboard) 8. To launch the Admin Console directly from your ISY, go to the following link: - http://your.isy.ip.address/admin.jnlp 9. If you are using Z-Wave and upgrading from a 4.x.x or earlier version of the ISY, see Z-Wave migration from 4.x.x branch below 10. Backup your ISY (File | Backup ISY) Z-Wave migration from 4.x.x branch All Z-Wave nodes will be recreated when migrating from 4.x.x. Some nodes will have different addresses, and some devices will have a different set of nodes. In some cases, it is easier to rebuild your network rather than migrate. 1. Before moving to 5.3.0, in 4.x.x, Backup your Z-Wave Dongle and then Backup your ISY. 2. Replace the 300 Series Z-Wave board in your ISY with a 500 Series Board 3. Install 5.3.2 4. Start the Admin Console and Restore the Z-Wave dongle (will take the Z-Wave network you backed up in step 1, and writes it to the new 500 series board) 5. Do Z-Wave -> Synchronize Nodes -> All - Do not open ‘Programs’ tab until step 6. - This will add back all of the ISY nodes that were deleted at startup. - If you have multichannel devices, you will see more nodes added - After sync is complete, restart the Admin Console and go to step 6. 6. Open the programs tab - Most old Z-Wave device actions/conditions are automatically converted to the 5.3.0 framework - Make sure to visually check all programs that contain Z-Wave device actions or conditions. - Programs containing nodes from multichannel devices will have to updated - Node addresses for multichannel devices change from ZW003_143 style to ZW003_002_143 (where _002_ is channel number) - If everything looks good, save the program changes made by the migration. 7. Make an ISY Backup 8. If you are missing any Z-Wave devices you may have to exclude/include them again. For battery devices, make sure they have communications turned on and try doing a synchronize again.

Open the Admin Console Event Viewer to Level 1, clear it, and then right+click on the device and select Z-Wave | Show Information in Event Viewer | Link Details You should see something like the following. If you don't see [This ISY] then it is not associated with the ISY and the ISY will not be automatically updated with status .. in this case, try installing isy version 5.3.1 because it has a fix related to Associations that may fix this problem. After installing 5.3.1, do right+click on the device and select Z-Wave | Repair Links Wed 12/02/2020 11:16:46 AM : [ZW-SHOW ] ---------------------------------------------- Wed 12/02/2020 11:16:46 AM : [ZW-SHOW ] Node 2 - ZW 002 Remote has 1 association group Wed 12/02/2020 11:16:46 AM : [ZW-SHOW ] Associations for group 001 of ZW002_147 ZW 002 Binary Switch 1 Wed 12/02/2020 11:16:46 AM : [ZW-SHOW ] Max Associations = 5 Wed 12/02/2020 11:16:46 AM : [ZW-SHOW ] - Node 1 - [This ISY] Wed 12/02/2020 11:16:46 AM : [ZW-SHOW ] Wed 12/02/2020 11:16:46 AM : [ZW-SHOW ] ----------------------------------------------

Please note: As part of Z-Wave Certification, the ISY-994 5.x series no longer supports the 300 Series Z-Wave board. Please check your upgrade discount eligibility and ordering instructions. If you have any other questions, please submit a support ticket Hello, The 5.3.1 *Test Build* is now available. As part of Z-Wave Plus certification, some incompatible changes were made that may cause issues when migrating from older versions of the ISY. We are looking at mitigating these issues in future builds. If you have a stable working system, you may want to wait before migrating. Guides Z-Wave Plus for ISY-994 Getting Started Z-Wave Plus for ISY-994 User Guide Z-Wave Plus for ISY-994 Advanced User Guide Notes - Upgrading to this version may require a lot of manual intervention including verifying scenes, programs and program settings are correct. In some cases it will be easier to rebuild your network. - If you are rebuilding your Z-Wave network, it is recommended that you Factory Reset the Z-Wave dongle prior to adding devices back into your Z-Wave network. - If you are upgrading from version 5.0.10 or earlier then Devices and programs are migrated in the current version. After upgrading: o Please ensure your device nodes and programs are correct; in some cases you may need to update them. o Wakeup your battery devices after the ISY has restarted and the initial query has finished - If you are upgrading from version 5.0.8 or earlier, you will have to manually update the Adjust Scene entries in all of your programs. - Starting in version 5.0.15A, the event value for the Low status of Insteon FanLinc Motor changed from 63 to 64 - If you have the climate module, please go here to choose a new weather service. Important User/Password changes: - If your current version is 5.0.7 or earlier, then after installing 5.0.8 or later your userid and password will be reset back to the system default. - If you restore a backup created from 5.0.7 or earlier, your userid and password will be reset back to the system default. - If you downgrade from version 5.0.8 or later to version 5.0.7 or earlier then after installing version 5.0.7 or earlier, you will have to Factory Reset the ISY and optionally install a backup taken in that version or earlier. Java runtime memory (when Admin Console is very slow to respond) - If the admin console is slow to respond, it is likely you need to increase the amount of memory allocated to the Java runtime (JRE). - Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following: o -Xmx512m - Press Ok to close the window, then Press Apply to save the changes Fixes in this build: 0000773 - Some 300 Series Z-Wave backups cannot be restored on 500 Series 0000772 - Elk turns Insteon Lamp to 50% instead of 100% 0000770 - Support old lock notification values 0000769 - Insteon NLS missing some nodedef names 0000767 - Fix invalid UTF-8 special characters in some units of measure 0000766 - Associations not allowed for some older devices Notes: - SSLv3 is now disabled. All models now support TLS1.2 and high grade cipher suites - 4.1.1 backups may corrupt Z-Wave configuration in case they are restored. 4.1.2 and above releases fix this issue - See our Wiki for additional information (e.g. Program Variables) Prerequisites: - You must use the 5.0.9 Admin Console or greater to upgrade to this release (5.3.0). - If you are migrating from 5.0.8 or older than in the Admin Console, you will have to manually close the Initialization progress bar - The latest release of Java must be installed - If you are using MAC Yosemite and Java 1.8.40, please follow these instructions Install: 1. Backup your ISY (File | Backup ISY) - Do not backup from a version 3.1.6, or 4.1.1 system (there were bugs in those versions that caused the backup to be corrupted) 2. Make sure you have done everything in the Prerequisites section 3. Download firmware - ISY 994i Series including Z-Wave support - ISY 994i ZW, Z, or ZS Series (Z-Wave/Zigbee and/or if you do NOT have a PLM) 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file downloaded in step 3 6. After the upgrade, You must clear your Java Cache 7. Launch the 5.3.0 Admin Console and/or Dashboard by going to the following link: - https://isy.universal-devices.com/start.jnlp Note: If you have version 5.0.8 or lower installed on your ISY, then use this link instead: - http://isy.universal-devices.com/994i/5.3.1/admin.jnlp Note: MAC 10.6.x users must use the following links instead - http://isy.universal-devices.com/994i/5.3.1/admin16.jnlp (Admin Console) - http://isy.universal-devices.com/994i/5.3.1/dashboard16.jnlp (Dashboard) 8. To launch the Admin Console directly from your ISY, go to the following link: - http://your.isy.ip.address/admin.jnlp 9. If you are using Z-Wave and upgrading from a 4.x.x or earlier version of the ISY, see Z-Wave migration from 4.x.x branch below 10. Backup your ISY (File | Backup ISY) Z-Wave migration from 4.x.x branch All Z-Wave nodes will be recreated when migrating from 4.x.x. Some nodes will have different addresses, and some devices will have a different set of nodes. In some cases, it is easier to rebuild your network rather than migrate. 1. Before moving to 5.3.0, in 4.x.x, Backup your Z-Wave Dongle and then Backup your ISY. 2. Replace the 300 Series Z-Wave board in your ISY with a 500 Series Board 3. Install 5.3.0 4. Start the Admin Console and Restore the Z-Wave dongle (will take the Z-Wave network you backed up in step 1, and writes it to the new 500 series board) 5. Do Z-Wave -> Synchronize Nodes -> All - Do not open ‘Programs’ tab until step 6. - This will add back all of the ISY nodes that were deleted at startup. - If you have multichannel devices, you will see more nodes added - After sync is complete, restart the Admin Console and go to step 6. 6. Open the programs tab - Most old Z-Wave device actions/conditions are automatically converted to the 5.3.0 framework - Make sure to visually check all programs that contain Z-Wave device actions or conditions. - Programs containing nodes from multichannel devices will have to updated - Node addresses for multichannel devices change from ZW003_143 style to ZW003_002_143 (where _002_ is channel number) - If everything looks good, save the program changes made by the migration. 7. Make an ISY Backup 8. If you are missing any Z-Wave devices you may have to exclude/include them again. For battery devices, make sure they have communications turned on and try doing a synchronize again.

"Invalid/Incorrect program key" generally only happens if something updated your programs while you were editting them in the Admin Console (i.e. something else saved/deleted programs and changed the key). If this happens again, try "undo changes" to reload them with the updated key.

Not in the ISY but some devices will allow you to do that. For example, I think the Aeotec Wallmote can be added securely or non-securely depending on whether you single press or double press the action button when adding it to the Z-Wave network.

Good point! There is an association issue with some older locks as well, and that could be the problem (basically some of the older locks don't follow the mandatory Z-Wave plus rules for association).

Some of the older locks do not use the Z-Wave defined Notifications for unlock/lock etc.. The main reason is when these locks were created, there was no standard set of notifications so they all used their own custom values. We've opened a problem report for this, and hopefully we can provide a solution to it in an upcoming build.