Release 5.3.0 - 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.0 Official Release is now available.

There are no functional changes in this build when compared to 5.2.0.  The only change is related to the ISY product ID reported through the Manufacturer Specific Command class for Z-Wave.

This is the first of our official 500 Series Z-Wave Plus certified builds.  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

---

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.0/admin.jnlp

  Note: MAC 10.6.x users must use the following links instead

  -  http://isy.universal-devices.com/994i/5.3.0/admin16.jnlp (Admin Console)

  -  http://isy.universal-devices.com/994i/5.3.0/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.

 

[Derek Atkins]

Thanks, Chris.

Any chance someone might look at this bug which was in 5.1 and 5.2 (and I presume 5.3 as you say no changes were made)?  It causes bogus XML to be sent from the ISY which buggers any compliant implementation because the data sent from the ISY is not UTF-8.

 

[asbril]

upgraded to 5.3 (from 5.2) without problems.

I assume that control vs status issue will be addressed later.

[Bumbershoot]

Congratulation on reaching certified status with Z-Wave!  The one issue I was having (Schlage Z-Wave lock showing pending writes) appears to be now resolved, at least for now...

[blueman2]

Congratulations on z-wave certification and on 5.x Official Release.  

[Michel Kohanim]

@asbril, yes.

With kind regards,
Michel

[JCPVAZ]

I know you put a lot of work into this, so congrats on a job well done. I only had very minor teething problems such as DST being turned back on but problems were few, minor, fairly obvious and easily remedied. Connection to the ISY with Agave seems a lot snappier now. Upgraded from 4.8 to 5.3. 

[blueman2]

21 hours ago, Chris Jahn said:

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

Thanks @Chris Jahn and @Michel Kohanim for updating the guides too.  I had not noticed these until now.  

Edited October 7, 2020 by blueman2

[n_sievers]

I have upgraded to 5.3.0 and have the new 500 series z-wave module installed with my configuration of 2 Schlage deadbolts and 1 Kwikset keypad lever set with everything working properly.  I am tired of the poor overall quality and degrading finish of the Kwikset lever and additionally want to be keyed the same as all other locks so have installed a Schlage fe599 keypad lever set in replacement and have successfully added to my isy.  The problem is that the status of the Schlage lever set is not updating whenever it is locked/unlocked with either the admin console or the lock/unlock buttons on the lock itself.  It will show correct status if I run a query but will not update on its own.  Any thoughts or insight on this?

[io_guy]

Is there a way to include a device that supports S0/S2 as insecure?

[larryllix]

@Chris Jahn@Michel Kohanim

New error for me during v5.3.0 save of a new program. I never found a way out and had to refresh my programs losing many edits. Hasn't done it since.

Edited October 7, 2020 by larryllix

[Chris Jahn]

On 10/6/2020 at 12:34 PM, Derek Atkins said:

Thanks, Chris.

Any chance someone might look at this bug which was in 5.1 and 5.2 (and I presume 5.3 as you say no changes were made)?  It causes bogus XML to be sent from the ISY which buggers any compliant implementation because the data sent from the ISY is not UTF-8.

 

Yes, we'll fix this in the next build.

[Chris Jahn]

On 10/6/2020 at 12:51 PM, asbril said:

upgraded to 5.3 (from 5.2) without problems.

I assume that control vs status issue will be addressed later.

We are going to address this problem along with the others that have been found in 5.2.0.

[Chris Jahn]

23 hours ago, Bumbershoot said:

Congratulation ...

 

23 hours ago, blueman2 said:

Congratulations on z-wave certification and on 5.x Official Release.  

 

6 hours ago, JCPVAZ said:

I know you put a lot of work into this, so congrats on a job well done. I only had very minor teething problems such as DST being turned back on but problems were few, minor, fairly obvious and easily remedied. Connection to the ISY with Agave seems a lot snappier now. Upgraded from 4.8 to 5.3. 

Thanks!

[blueman2]

2 hours ago, n_sievers said:

I have upgraded to 5.3.0 and have the new 500 series z-wave module installed with my configuration of 2 Schlage deadbolts and 1 Kwikset keypad lever set with everything working properly.  I am tired of the poor overall quality and degrading finish of the Kwikset lever and additionally want to be keyed the same as all other locks so have installed a Schlage fe599 keypad lever set in replacement and have successfully added to my isy.  The problem is that the status of the Schlage lever set is not updating whenever it is locked/unlocked with either the admin console or the lock/unlock buttons on the lock itself.  It will show correct status if I run a query but will not update on its own.  Any thoughts or insight on this?

Try doing z-wave | update links.  It might have a bad association, which will cause the lock not to send data to the ISY by itself.  But Query will still work.  

[Chris Jahn]

2 hours ago, n_sievers said:

I have upgraded to 5.3.0 and have the new 500 series z-wave module installed with my configuration of 2 Schlage deadbolts and 1 Kwikset keypad lever set with everything working properly.  I am tired of the poor overall quality and degrading finish of the Kwikset lever and additionally want to be keyed the same as all other locks so have installed a Schlage fe599 keypad lever set in replacement and have successfully added to my isy.  The problem is that the status of the Schlage lever set is not updating whenever it is locked/unlocked with either the admin console or the lock/unlock buttons on the lock itself.  It will show correct status if I run a query but will not update on its own.  Any thoughts or insight on this?

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.

[Chris Jahn]

1 minute ago, blueman2 said:

Try doing z-wave | update links.  It might have a bad association, which will cause the lock not to send data to the ISY by itself.  But Query will still work.  

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).

[Chris Jahn]

1 hour ago, io_guy said:

Is there a way to include a device that supports S0/S2 as insecure?

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.

[Chris Jahn]

49 minutes ago, larryllix said:

@Chris Jahn@Michel Kohanim

New error for me during v5.3.0 save of a new program. I never found a way out and had to refresh my programs losing many edits. Hasn't done it since.

"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.

[larryllix]

9 minutes ago, Chris Jahn said:

"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.

Thanks. That is what I did eventually, after trying to copy, rename programs, and re-update/edit  every line. Perhaps I thought a Save failed before. MY ISY is now so busy with constant battery device writes and there doesn't seem to be a way out of it since it keeps turning itself back on and the scene modifying hits on the battery device now every program line.

It would be nice to see this battery write dilemma/logical error  fixed.

Edited October 7, 2020 by larryllix

[n_sievers]

29 minutes ago, blueman2 said:

Try doing z-wave | update links.  It might have a bad association, which will cause the lock not to send data to the ISY by itself.  But Query will still work.  

Thank you for the response.  I tried this without success.

 

[n_sievers]

41 minutes ago, Chris Jahn said:

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.

I ended up going this direction for the lever set to stay brand/style consistent with my other Schlage locks and keying even though it is not Z-Wave Plus but may just go the Yale route with their key free lever set (or get a Schalge retrofit cylinder for the Yale lock) which will similarly match my other lever handles.  Any thoughts or suggestions on Yale?

[DaveStLou]

 

On 10/6/2020 at 2:14 PM, Chris Jahn said:

The 5.3.0 Official Release is now available.

This is the first of our official 500 Series Z-Wave Plus certified builds. 

Upgraded from RC without any issues. Congratulations @Michel Kohanim, @Chris Jahn and the whole UDI team!

Edited October 7, 2020 by DaveStLou

[io_guy]

3 hours ago, Chris Jahn said:

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.

Any chance this could be added?

Homeseer has this feature and it's been great for upping reliability.  I couldn't care less if my dimmers add as insecure and as insecure they have a much easier time pairing and meshing with various other devices.  

[TrojanHorse]

We are going to address this problem along with the others that have been found in 5.2.0.

Will that hopefully also include the Elk zone status at restart issue noted previously, please : - )

Thanks.


Sent from my iPhone using Tapatalk