Greetings;

 

Just upgraded my ISY with a new Z-Wave Dongle and at first sight, it seems to have migrated without an issue... (also upgraded to 5.3.0)

I was waiting for this to add a few motion sensors to the system and now I'm ready to do so... all my sensors are on V1.13, and V1.14 is available

AeoTec asks for this to be done with their own dongle, but according to a now closed post on OTA upgrades @Michel Kohanim mentions  that OTA is part of the 500 certification.

I have not been able to see any menu items indicating that ISY can do so? Can someone point me in the right direction, please?

Cheers

38 minutes ago, TriLife said:

Greetings;

 

Just upgraded my ISY with a new Z-Wave Dongle and at first sight, it seems to have migrated without an issue... (also upgraded to 5.3.0)

I was waiting for this to add a few motion sensors to the system and now I'm ready to do so... all my sensors are on V1.13, and V1.14 is available

AeoTec asks for this to be done with their own dongle, but according to a now closed post on OTA upgrades @Michel Kohanim mentions  that OTA is part of the 500 certification.

I have not been able to see any menu items indicating that ISY can do so? Can someone point me in the right direction, please?

Cheers

OTA is not available at this time

7 hours ago, lilyoyo1 said:

OTA is not available at this time

Rats, Don't want to clib to 20' ceilings with a recently operated knee. I guess they'll stay on 1.13 until a) OTA is available or b) my knee feels up to it... 

Thanks anyway lilyoyo1

I do have a follow up questions:

I pulled one of the multi-sensor units, which was paired with the ISY down from the ceiling. They are all paired in "secure" (blue light when activated)

I then "added" it to the AeoTec Z-Wave dongle to upgrade it from V1.13 to 1.14. Upon upgrade, and after power cycle, the light came up green, indicating a non-secure mode. It also wouldn't connect to the ISY anymore. I had to "remove" and then "add" again in "secure".

Obviously the programs now all need to be updated with the new ZWxx ID. And, non-critical, but irritating to an anal retentive person like me, there are now gaps in the numbering, since the old ZWbb is now defunct and the new ZWxx was added at the end of the units (now at ZW45). I deleted ZWbb from the list in MAIN, but when I do a ZWAVE->Synchronize-ALL, they all show back up again, including some stuff that is eons old...

So:

1- Is there a way to upgrade the firmware without the multi-sensor losing its pairing with the ISY? (or re-assign a new pairing to an existing one)

2- Is there a way of permanently deleting defunct pairing records, so they don't show up again?

3- Is there a way to re-number or otherwise "clean up" the ZWxx numbering? Mind you, I have added my own pre-fixes to the units "ZW13 Multilevel Sensor" is now "Guest Suite ZW13 Multilevel"...

 

Thanks

FWIW, I pair my multisensor 6s in non-secure mode. They seem to respond a little quicker this way.

20 minutes ago, gviliunas said:

FWIW, I pair my multisensor 6s in non-secure mode. They seem to respond a little quicker this way.

Non secure is faster since encryption isn't involved

1 hour ago, TriLife said:

I do have a follow up questions:

I pulled one of the multi-sensor units, which was paired with the ISY down from the ceiling. They are all paired in "secure" (blue light when activated)

I then "added" it to the AeoTec Z-Wave dongle to upgrade it from V1.13 to 1.14. Upon upgrade, and after power cycle, the light came up green, indicating a non-secure mode. It also wouldn't connect to the ISY anymore. I had to "remove" and then "add" again in "secure".

Obviously the programs now all need to be updated with the new ZWxx ID. And, non-critical, but irritating to an anal retentive person like me, there are now gaps in the numbering, since the old ZWbb is now defunct and the new ZWxx was added at the end of the units (now at ZW45). I deleted ZWbb from the list in MAIN, but when I do a ZWAVE->Synchronize-ALL, they all show back up again, including some stuff that is eons old...

So:

1- Is there a way to upgrade the firmware without the multi-sensor losing its pairing with the ISY? (or re-assign a new pairing to an existing one)

2- Is there a way of permanently deleting defunct pairing records, so they don't show up again?

3- Is there a way to re-number or otherwise "clean up" the ZWxx numbering? Mind you, I have added my own pre-fixes to the units "ZW13 Multilevel Sensor" is now "Guest Suite ZW13 Multilevel"...

 

 

Zwave assigns numbers as devices are added. Unfortunately there's nothing the isy can do about it. You can synchronize your nodes, which will open that slot for the future. However, zwave will still start with the next number available. If it's that important, you'll have to factory reset the board and start clean

35 minutes ago, gviliunas said:

FWIW, I pair my multisensor 6s in non-secure mode. They seem to respond a little quicker this way.

Thanks for that bit of info. I'll give that a try.

Any input the other questions?

Cheers.

16 minutes ago, lilyoyo1 said:

Zwave assigns numbers as devices are added. Unfortunately there's nothing the isy can do about it. You can synchronize your nodes, which will open that slot for the future. However, zwave will still start with the next number available. If it's that important, you'll have to factory reset the board and start clean

Thanks @lilyoyo1.

not that important as to resetting the board, no.

Any idea on #1, firmware update without losing my spot on the ISY? 

Cheers

I don't upgrade firmware once added to the Isy so I can't say for certain what would happen with devices in secure mode (I suspect the encryption will cause issues).

Generally however, your other controller should be made a secondary controller in the Isy, and control moved over to that. Update, then moved back to Isy. @Michel Kohanimshould be able to confirm if this is still the case. 

20 hours ago, lilyoyo1 said:

I don't upgrade firmware once added to the Isy so I can't say for certain what would happen with devices in secure mode (I suspect the encryption will cause issues).

Generally however, your other controller should be made a secondary controller in the Isy, and control moved over to that. Update, then moved back to Isy. @Michel Kohanimshould be able to confirm if this is still the case. 

Greetings;

So, it appears that ISY Z-Wave doesn't support S2 Security, which is probably why when trying to add a multi-sensor with V1.14 firmware in Secure mode it gives an error...

I now have to remove all 10 units and add them again, in non-secure mode (seems like this will speed the response a bit, and I haven't installed them in the ceilings yet). But I now have even bigger gaps and I'm thinking of doing Dongle reset...

I'd also like to add the AeoTec Dongle as a secondary controller as you suggest, but the Z-wave menu in my 5.3.0 with Z-wave 6.82.01 doesn't include any option for shifting control as indicated it the manual https://wiki.universal-devices.com/index.php?title=ISY_Z-Wave_GenII_-_Instructions.

I also noticed that options like Heal- Z-Wave Network and Repair links have disappeared. I have a rather large home which is more linear in layout. The Z-waves are all USB powered so they can mesh together. This Heal network function was rather useful... I hope I didn't just shoot myself in the foot by upgrading to the new 500 dongle...

 

Cheers;

 

3 hours ago, TriLife said:

Greetings;

So, it appears that ISY Z-Wave doesn't support S2 Security, which is probably why when trying to add a multi-sensor with V1.14 firmware in Secure mode it gives an error...

I now have to remove all 10 units and add them again, in non-secure mode (seems like this will speed the response a bit, and I haven't installed them in the ceilings yet). But I now have even bigger gaps and I'm thinking of doing Dongle reset...

I'd also like to add the AeoTec Dongle as a secondary controller as you suggest, but the Z-wave menu in my 5.3.0 with Z-wave 6.82.01 doesn't include any option for shifting control as indicated it the manual https://wiki.universal-devices.com/index.php?title=ISY_Z-Wave_GenII_-_Instructions.

I also noticed that options like Heal- Z-Wave Network and Repair links have disappeared. I have a rather large home which is more linear in layout. The Z-waves are all USB powered so they can mesh together. This Heal network function was rather useful... I hope I didn't just shoot myself in the foot by upgrading to the new 500 dongle...

 

Cheers;

 

The network heal wasnt and isn't the best way to manage a network which is part of the reason zwave alliance removed it. Since zwave is self healing, your devices will do it themselves. Its better to update a single problem device vs all together. Using update neighbors on a device that has problems communicating will update the path for that device. 

11 minutes ago, lilyoyo1 said:

The network heal wasnt and isn't the best way to manage a network which is part of the reason zwave alliance removed it. Since zwave is self healing, your devices will do it themselves. Its better to update a single problem device vs all together. Using update neighbors on a device that has problems communicating will update the path for that device. 

Thanks. did they also remove the ability to add/move Secondary controllers?

One "trick" you can use when your device has somehow become disconnected from the isy zwave and you want to add it back with the same zwave ID is to select the original zwave node (that has the desired ID) in the admin console and then use the zwave device menu option the replace a defective/dead device

It basically let's you add a device back in reusing the same zwave ID. 

 

Ive used this a few times when I've replaced a bad device or had to move it to my zwave stick for firmware updates.

 

 

 

6 hours ago, gduprey said:

One "trick" you can use when your device has somehow become disconnected from the isy zwave and you want to add it back with the same zwave ID is to select the original zwave node (that has the desired ID) in the admin console and then use the zwave device menu option the replace a defective/dead device

It basically let's you add a device back in reusing the same zwave ID. 

 

Ive used this a few times when I've replaced a bad device or had to move it to my zwave stick for firmware updates.

 

 

 

Awesome! Thanks G.

This is exactly what I was looking for all this time. I did a complete reset of my ISY and started from scratch,  but as luck would have it, the 5th and node didn't sync up correctly and I had to redo it, assigning node21 the second time around. I will delete 21 and follow your instructions on repopulate node5.

Made my day!