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.

Installed.  No apparent issues.  The first thing I did is exercise my Schlage Z-Wave lock from the AC, and it operated as designed.

EDIT: Are these new icons in the context menu in program details pane?  Maybe I didn't notice them before...

Edited March 8, 20214 yr by Bumbershoot

Installed with no issues and Z-Wave devices are reporting. 

Installed with no issues

Upgrade from 5.3.0 and any attempt to interact with any Z-wave device (hardwired or battery) results in many error messages.

 

Edit: Despite the errors, device status still is reporting back accurately and the action executes correctly on the Z-wave device.

 

Edited March 8, 20214 yr by MWoods329

22 minutes ago, MWoods329 said:

Upgrade from 5.3.0 and any attempt to interact with any Z-wave device (hardwired or battery) results in many error messages.

 

Edit: Despite the errors, device status still is reporting back accurately and the action executes correctly on the Z-wave device.

 

 

 

Sorry, one more edit - some of the devices are respond and reporting.  Not all.  Doesn't appear to be a pattern that I can see.

Updated from 5.3.2 without any issues.

Upgraded my mixed Insteon / Z-Wave system from ver. 5.3.2 without any issues.

Upgraded from 5.3.2 to 5.3.3 no issues.  I continue to have the Green "1011" tags on a few of my items, but understand that issue is still an open item.  

1 hour ago, blueman2 said:

I continue to have the Green "1011" tags on a few of my items, but understand that issue is still an open item.  

FWIW, they fixed this issue with Adjust Scene in 5.3.2, which has indeed worked with my battery powered scene controllers.  From the notes:

0000774 - Green icon appears on Insteon Controller Node after using Adjust Scene

 

4 hours ago, Bumbershoot said:

FWIW, they fixed this issue with Adjust Scene in 5.3.2, which has indeed worked with my battery powered scene controllers.  From the notes:

0000774 - Green icon appears on Insteon Controller Node after using Adjust Scene

 

Yup, that fixed it for my Schlage locks, but not for a couple other devices that are wired/always on.  For example, an Intermatic pool controller.   

 

An observation/perception with Z-Wave performance on 5.3.3: I'm perceiving that my ISY is handling Z-Wave device updates faster than it has in the past.  I don't know if this is true, as I don't have data to back this assertion up.  This is perceptible in a couple of device types in my installation: Z-Wave motion sensors, my single Z-Wave lock and the state changes in my garage doors.

None of my Z-Wave motion sensors are battery powered, but with this firmware, it very much seems that the ISY turns on the lights upon motion being sensed quicker than previously, which is nice.  Also, when I open/close my garage doors, I notice that the firmware shows the transition from closed/opening/open almost exactly when the tilt sensor changes state.  This has never been this quick or reliable.  Additionally, my single Schlage lock displays changes of state in the AC immediately instead of a few seconds later.

This just makes me think that UDI is getting their Z-Wave code optimized in their firmware.  Not a big deal (and maybe not even true), but I'm liking my Z-Wave devices a little more with this release.

@blueman2 is the controller for those devices an Insteon Wireless device?  If so, you may need to put the device into programming mode and let instructions that are currently in queue be written, after which new won't accumulate.   If not, ignore this.

Installed.  No apparent issues.  The first thing I did is exercise my 2 KwikSet Z-Wave locks from the AC, and it operated as designed.

I decided to finally try a test build and it appears to have resolved my ZWave lock issue. Everything seems to be functioning so far. Thanks for the hard work!

 

On 3/15/2021 at 10:47 PM, nathan said:

I decided to finally try a test build and it appears to have resolved my ZWave lock issue. Everything seems to be functioning so far. Thanks for the hard work!

 

It seems something still isn’t right with these locks and the new test builds. I used to be able to trigger programs on USRNUM but it seems like this is no longer triggering. Does anyone else have this issue?

Edit: After saving the program again, it works correctly.

Edited March 17, 20214 yr by nathan

Upgraded from 5.1.0 to 5.3.3 yesterday.

No issues.

Both older Schlage locks (BE369 and BE599)  work fine after a Zwave/Synchronize

Polyglot nodes work fine after restarting the nodes in Polyglot server.

 

I upgraded from 5.3.0 to 5.3.3 with only 1 minor glitch –  the PurpleAir node server doesn't populate field GV11 (EPA AQI Category) anymore (it's a string, versus all other fields are numbers).  It was working fine with 5.3.0.   I filed a bug report with the plugin author just in case.

On 3/10/2021 at 5:50 AM, Bumbershoot said:

An observation/perception with Z-Wave performance on 5.3.3: I'm perceiving that my ISY is handling Z-Wave device updates faster than it has in the past.  I don't know if this is true, as I don't have data to back this assertion up.  This is perceptible in a couple of device types in my installation: Z-Wave motion sensors, my single Z-Wave lock and the state changes in my garage doors.

None of my Z-Wave motion sensors are battery powered, but with this firmware, it very much seems that the ISY turns on the lights upon motion being sensed quicker than previously, which is nice.  Also, when I open/close my garage doors, I notice that the firmware shows the transition from closed/opening/open almost exactly when the tilt sensor changes state.  This has never been this quick or reliable.  Additionally, my single Schlage lock displays changes of state in the AC immediately instead of a few seconds later.

This just makes me think that UDI is getting their Z-Wave code optimized in their firmware.  Not a big deal (and maybe not even true), but I'm liking my Z-Wave devices a little more with this release.

This observation struck me as well.  Ever since I put my ISY in a media closet and have to rely on an intermediate Z-Wave device to relay pretty much all commands, I have routinely observed delays in the 30 to 60 second range (I'm thinking of moving back my ISY).  But so far, with this build, my lights are coming up right away.   I hope this change is real!

Upgraded from 5.3.2 to 5.3.3 and everything works perfectly fine. I can also say the response time is better (faster) for all devices, not only z-wave.

Not sure this is something added in this build, but I have noticed I am now able to query battery status on pretty much all of my devices that are wireless and rely on 'query when awake'.  In the past, battery percentage on all of my monoprice z-wave door sensors would not populate.  Now it does.  I just have to do nightly queries to get the data, but that is a simple program.  

Quote

 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)

I am confused about which link to use? I have 1 994i that has no Zwave at all, and 1 994i -ZW. It looks from the decsription that I could use either link for the ISY 994i ZW?

 

Edited April 5, 20214 yr by ronbo

48 minutes ago, ronbo said:

I am confused about which link to use? I have 1 994i that has no Zwave at all, and 1 994i -ZW. It looks from the decsription that I could use either link for the ISY 994i ZW?

 

The first version will refuse to load further if it does not find a PLM. Use it with any Insteon.

Edited April 5, 20214 yr by larryllix

Trying to migrate from 5.3.1 to 5.3.3 but after 20 seconds or so, during loading of /code/455/hex it stop giving error message:  "reported written size is invalid"

Suggestions?

1 hour ago, SHM said:

Trying to migrate from 5.3.1 to 5.3.3 but after 20 seconds or so, during loading of /code/455/hex it stop giving error message:  "reported written size is invalid"

Suggestions?

Did you Clear your Java cache, including all applications prior to the update?  

Did you click only on the unziped update file ( don't unzip it)