Release 5.3.2 Test Build - OUTDATED

[Chris Jahn]

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.

[asbril]

I upgraded without any apparent issue.?

[Bumbershoot]

No apparent issues here, either. 

[Whitehambone]

Upgraded without issues and Z-Wave devices are reporting as normal.

[dbuss]

The update to 5.3.2 appears to be flawless. Thank you for the update!

[lilyoyo1]

@Chris Jahndoes this address the issues with locks that many of us has had with 5.3+?

[RLawson]

New to the forum - where do you find the firmware download links for version 5.3.2?

[Screw Loose Dan]

 

1 hour ago, RLawson said:

New to the forum - where do you find the firmware download links for version 5.3.2?

@RLawson - Step three under Install section in the first post:

On 1/24/2021 at 7:50 PM, Chris Jahn said:

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)

[RLawson]

Thank You

[gviliunas]

Updated from 5.3.1 without any issues. Everything is working properly.

Thank you Chris and the UDI team!

[wrj0]

Another successful upgrade to 5.3.2 from 5.3.1 without any apparent issues. Two older Schlage locks (BE469NX and BE369) seem to be controlled, reporting and working fine.

[RLawson]

Initially tried migrating from 4.8 to 5.3.2 - multiple issues with my zwave devices and propgrams . Eventually decided to upgrade and rebuild my zwave system.  Upgrade went well and system is running fine - no issues.  Also default  mail server is back running on this version.   I have a question - how do you heal you zwave system after adding new devices  in this version?

[sdynak]

On 1/25/2021 at 4:01 PM, lilyoyo1 said:

@Chris Jahndoes this address the issues with locks that many of us has had with 5.3+?

 

I have the same question. Initially my Schlage lock seemed ok but the status updates are flaky and unreliable. I have done a remove & add along with a factory reset and got some strange stuff including a bunch of new nodes I never had and communications issues. If I move the lock to another folder I get a synchronize icon that does not go away. It seems to be ok if I leave it at top level. After 2 days of frustrations removing, factory resetting and adding back in I am back to square 1 with flaky status updates but at least it seems to be communicating with flaky status updated although not sure for how long. 

At this point I'm wondering if it is worth moving to a Yale. I really don't want to just for the cost alone as my Schlage is not that old and really not looking to replace it but this is getting frustrating. I have to reset all my programs every time which is not that big of a deal but with the issues removing & adding back in not going well and several times it gets tiring :). 

So do we need to purchase new Z-Wave hardware on top of the upgraded 500 board? 

 

Never had these before:

 

 

[sdynak]

9 hours ago, wrj0 said:

Another successful upgrade to 5.3.2 from 5.3.1 without any apparent issues. Two older Schlage locks (BE469NX and BE369) seem to be controlled, reporting and working fine.

Were you having status update issues before this with your Schlage locks? 

[sdynak]

I went ahead and tried to upgrade to 5.3.2 in hope of sorting my Schlage lock status issues and got this after I logged back in. Any thoughts what to check?

 EDIT: Schlage coming up with unknown status now so didn't seem to help there either. It was at least working somewhat in 5.3.0 after a lot of work. 

Going to drop back to 5.3.0 for now. Never had errors like this in my past upgrades up to 5.3.0. 

 

[DennisC]

2 hours ago, sdynak said:

I went ahead and tried to upgrade to 5.3.2 in hope of sorting my Schlage lock status issues and got this after I logged back in. Any thoughts what to check?

 EDIT: Schlage coming up with unknown status now so didn't seem to help there either. It was at least working somewhat in 5.3.0 after a lot of work. 

Going to drop back to 5.3.0 for now. Never had errors like this in my past upgrades up to 5.3.0. 

 

Maybe you should open a support ticket with UD.

[sdynak]

7 hours ago, DennisC said:

Maybe you should open a support ticket with UD.

I contemplated it.. my concern is how busy they are and don't want to bog them down with this. I'm going to try a Yale lock and I'll wait until 5.3.2 is refined. I'm thinking I won't be the only one with the error hopefully so it will get sorted out in the refinements. If the error is still there when it is official I'll open a ticket. Thanks..

[lilyoyo1]

28 minutes ago, sdynak said:

I contemplated it.. my concern is how busy they are and don't want to bog them down with this. I'm going to try a Yale lock and I'll wait until 5.3.2 is refined. I'm thinking I won't be the only one with the error hopefully so it will get sorted out in the refinements. If the error is still there when it is official I'll open a ticket. Thanks..

Yale has the same issues

[sdynak]

3 hours ago, lilyoyo1 said:

Yale has the same issues

 

 Great.. do you know if there any locks that are working well? Back on 5.3.0 and Schlage is still struggling with proper status. I do not have the Yale yet. It is not a distance issue.. I am 20ft with a clear line of sight from my ISY to my lock. 

[wrj0]

Were you having status update issues before this with your Schlage locks? 

I was indeed having some communications errors with the BE469 before upgrading to the series 500 Zwave board. After installing that board, I factory reset the locks and the other installed Zwave devices, and added two new gen 7 Aoetec repeaters. Took most of a day to get everything setup again, and had to modify several programs to use the new Zwave device ID's, but everything is working much better now, even the BE469 that previously caused frequent errors. Resetting all the Zwave devices was a real pain in the seat, but seems to have been worth the effort.

[oberkc]

While I have upgraded to numerous versions over the years, it is suddenly unclear to me which file is the one to choose.  Is it the "DEF.zip"?  Has something changed in the naming convention?  I thought they used to be called "insteon_X.X.X.zip" or something similar.

 

 

[sdynak]

21 minutes ago, wrj0 said:

I was indeed having some communications errors with the BE469 before upgrading to the series 500 Zwave board. After installing that board, I factory reset the locks and the other installed Zwave devices, and added two new gen 7 Aoetec repeaters. Took most of a day to get everything setup again, and had to modify several programs to use the new Zwave device ID's, but everything is working much better now, even the BE469 that previously caused frequent errors. Resetting all the Zwave devices was a real pain in the seat, but seems to have been worth the effort.

 

 Thanks for that.. I only have 2 zwave devices.. My Schlage Lock and my Dome water valve. The water valve is working fine and I never had to do anything to it.

I have factory rest my Schlage a few times now with varied results where it looked good but still hit or miss on status updates. 

I have not factory reset the 500 board. I only did the upgrade path with backing up & restoring. Initially it looked ok but had the status issues with Schlage. I did have some random issues before but this is significantly worse it seems. 

Did you factory reset the 500 board?

[larryllix]

29 minutes ago, oberkc said:

While I have upgraded to numerous versions over the years, it is suddenly unclear to me which file is the one to choose.  Is it the "DEF.zip"?  Has something changed in the naming convention?  I thought they used to be called "insteon_X.X.X.zip" or something similar.

 

 

I see two different naming conventions now, both ending in 5.3.2.zip. Hover your cursor over the link for the file name at the bottom of the browser on mouse based O/Ses.

[lilyoyo1]

1 hour ago, sdynak said:

 

 Great.. do you know if there any locks that are working well? Back on 5.3.0 and Schlage is still struggling with proper status. I do not have the Yale yet. It is not a distance issue.. I am 20ft with a clear line of sight from my ISY to my lock. 

No. All I install are yale. Have had nothing but issues with all since 5.3

[sdynak]

3 minutes ago, lilyoyo1 said:

No. All I install are yale. Have had nothing but issues with all since 5.3

 Got it.. good to know. I thought the upgrades and 500 board would have helped and be ready for moving forward. Thanks