Release 5.2.0 (RC3) - OUTDATED

[blueman2]

I too am having the issue of the dreaded Green 1011 icon showing up on some of my devices/nodes.  All of them are plug in / always on devices.  So not a battery device issue.  Normally, I would not worry too much, but this goes beyond aesthetics.  I am getting constant attempts by the ISY to force write the device.  No matter what I do by trying to write it myself, it always does nothing.  Here is what Event Viewer shows, and this forced write attempt appears to happen quite a bit and slows down my system.  No, I did not do a node sync, as the log implies.  The ISY is doing this all on its own.  Getting rather annoying.  

 

Sun 09/06/2020 09:17:31 PM : [ZWAVE-NODE-SYNC] Processing Z-Wave Node 44 (0x2C) Failed, node ignored
Sun 09/06/2020 09:17:31 PM : [ZWAVE-NODE-SYNC] -- Finished -- ISY/Z-Wave Node Sync --
Sun 09/06/2020 09:17:31 PM : [All         ] Writing 0 bytes to devices
Sun 09/06/2020 09:17:31 PM : [All         ] Writing 0 bytes to devices
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:31 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:32 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1
Sun 09/06/2020 09:17:32 PM : [ZWAVE-WAKEUP  44] Force writes to ZW044_1

 

[mink]

I trying to add an 

Ecolink Z-Wave Plus Rare Earth Magnets Door & Window Sensor, White & Brown (DWZWAVE2.5-ECO).

The ISY 994i IR/Pro 5.2.0 with the new 500 Zwave is a SECONDARY Controller

A Honeywell/Ademco TUXWIFI Zwave 6280i zwave Keypad is the PRIMARY controller

wjith a Honeywell Zwave Thermostat. 

The only way this seemed to work was to remove the ISY from the TUXWIFI's network, learn. Then add the Sensor to the TUXWIFI (actually, the sensor could be already added to the TUXWIFI). Then add the ISY back as a SECONDARY controller, LEARN and then synchronize the nodes. Rather scary, but the previously added Thermostat nodes all came back. 

Unfortunately it seemed the sensor status would not update and then a "cannot communicate with device error".

This showed the green 0101 but, but now just RED exclamation points.

I tried adding the Ecolink Window sensor directly to the ISY when it was not associated with the TUXWIFI , but that did not work either.

any ideas anyone? 

Thanks

ZW 009 Notify Sensor	Error	0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000	Mon 2020/09/07 01:04:44 AM	System	Log	
ZW 009 Notify Sensor	 	 	Mon 2020/09/07 01:04:44 AM	System	-2	
Sync Full	ZWave	All	Mon 2020/09/07 01:06:37 AM	System	Log	
Get NodeDef	ZWave	ZW001_1	Mon 2020/09/07 01:07:42 AM	System	Log	
Get NodeDef	ZWave	ZW001_111	Mon 2020/09/07 01:07:42 AM	System	Log	

 

[whywork]

Hi,

I use and enjoy my ISY every day.

After upgrading to 5.2.0 (RC3)  Z Wave "heal network" option is missing from Z Wave menu.  

Cleared Java cash, UI and firmware 5.2. Cold boot of ISY 994i Pro. No change.

Also can't find shift primary z wave controller or upgrade z wave firmware.

 

Did "heal" get moved?

Suggestions?

 

 

 

 

[lilyoyo1]

There is no upgrade to the zwave firmware.

It's been posted a few times on this forum that he'll has been removed and replaced with update neighbors

[whywork]

Hi,

Thanks for reply.

Ah! Have to select one particular z wave device first, then can heal entire network.   

 

 

 

[asbril]

5 minutes ago, whywork said:

Hi,

Thanks for reply.

Ah! Have to select one particular z wave device first, then can heal entire network.   

 

 

 

How do you do that ? I don't see the heal network anymore.

[blueman2]

23 minutes ago, whywork said:

Hi,

Thanks for reply.

Ah! Have to select one particular z wave device first, then can heal entire network.   

Not quite.  The "Heal" was removed because with 500 series (aka Gen 5) controllers, heal is no longer needed (in theory!).  Instead, the devices adjust their paths themselves based on their list of neighbors and last working pathway(s).  At least, that was the intention of the z-wave consortium (which UDI does not control).  However, when you move a particular device from one location to another, it helps to use the device "Update Neighbors" so that it knows there are new neighbors around.  

I think there might still be some issues with the ISY implementation that need fixing, but I just wanted to share my understanding of why "Heal" went away.  Not UDI's decision so much as how Z-wave wants to work for Gen 5.  I personally think there does still need to be something that triggers the entire network to recheck for neighbors and re-establish working pathways, but I am not sure how that works with Gen 5.  Perhaps if there was a way to manually trigger the explorer frame process which finds new routes between associated devices, that might help.  

Bottom line is that I think UDI is working for Z-wave compliance, and they are making changes towards that end.

[asbril]

30 minutes ago, blueman2 said:

Instead, the devices adjust their paths themselves based on their list of neighbors and last working pathway(s).

Thanks @blueman2 but does this not assume that all the devices must be Gen5 ?

[blueman2]

36 minutes ago, asbril said:

Thanks @blueman2 but does this not assume that all the devices must be Gen5 ?

That is what I still do not understand.  This transition from Gen 3 to Gen 5 (not to mention that fact that Gen 7 is now out!) confuses the heck out of me.  I think if you have a 100% Gen 5 or greater network, things work well.  But in the real world where most of us have some < Gen 5 devices, I think things are more complex.  

Right now, however, I have my mix of Gen 3 and Gen 5 devices (about 25 of them active) working just fine after:

1. Moving to Series 500 Dongle
2. synchronizing each device, one by one, by bringing them near the ISY
3. "Repair Links" to ensure the correct association between the device and the ISY 
4. "Update Neighbors" once I have placed the device where I want it.  

After doing that with most of my devices, all is well.  I did not remove any of my door locks (4 of them, all Gen 3) but after doing all of the above, I was able to synchronize, repair links, and update neighbors where they were without removing them (which is a real pain in the a$$ to do).

I think there still might be an issue with Explorer Frames, which as I understand it is how Gen 5 controllers send out requests to find new pathways for devices to use.  I have found in the past the some devices simply cannot find a working pathway, even though they have a good list of neighbors, and those neighbors list that device as well.  Explorer Frames I think is supposed to find working pathways when needed but does not seem to be working just right.  

[asbril]

1 hour ago, blueman2 said:

That is what I still do not understand.  This transition from Gen 3 to Gen 5 (not to mention that fact that Gen 7 is now out!) confuses the heck out of me.  I think if you have a 100% Gen 5 or greater network, things work well.  But in the real world where most of us have some < Gen 5 devices, I think things are more complex.  

Right now, however, I have my mix of Gen 3 and Gen 5 devices (about 25 of them active) working just fine after:

1. Moving to Series 500 Dongle
2. synchronizing each device, one by one, by bringing them near the ISY
3. "Repair Links" to ensure the correct association between the device and the ISY 
4. "Update Neighbors" once I have placed the device where I want it.  

After doing that with most of my devices, all is well.  I did not remove any of my door locks (4 of them, all Gen 3) but after doing all of the above, I was able to synchronize, repair links, and update neighbors where they were without removing them (which is a real pain in the a$$ to do).

I think there still might be an issue with Explorer Frames, which as I understand it is how Gen 5 controllers send out requests to find new pathways for devices to use.  I have found in the past the some devices simply cannot find a working pathway, even though they have a good list of neighbors, and those neighbors list that device as well.  Explorer Frames I think is supposed to find working pathways when needed but does not seem to be working just right.  

Thanks. Generally my Zwave network ( more than 70 devices, a few 3, most 5 series)  works fine with 5.2 and the 500 dongle. Since the 5.2 upgrade I get more communication error messages, but in fact the devices continue to work.

[blueman2]

As an update to my "Green 1011 Icon" issue, I think what caused this originally is that I tried to do a "Repair Links" with a node within a multi channel device that said Repair Links was not supported or something like that.  I just remember clicking on do it anyway, and that is what created the "Green 1011" icon and the following attempts by the ISY to continue trying to write to the device.  @Chris Jahn, is this something you can look into to see what is going on?  Let me know what logs or other help you need. 

 

[danbutter]

10 hours ago, blueman2 said:

 

1. synchronizing each device, one by one, by bringing them near the ISY

So you had to go through almost the same motions as redoing your entire network from scratch...sigh.

This is exactly what I was hoping I wouldn't have to do.

[asbril]

1 hour ago, danbutter said:

So you had to go through almost the same motions as redoing your entire network from scratch...sigh.

This is exactly what I was hoping I wouldn't have to do.

The  Kasa device hat I added earlier today has the green "writing" in permanence, but the event viewer shows no activity for the device, other than 100 when ON and 0 when OFF.

[GregE]

Was looking to upgrade my version 4.8 ISY994i and was following the list and it said to make sure your z-wave firmware was at 4.55 but when I look at mine I see this.  Did I miss a step when I installed it?  Only z-wave device installed in my network is a repeater currently so no big deal whatever I need to do.  I got it so I could install a z-wave switch on my water heater since Insteon got rid of theirs but haven't gotten to it yet.

 

Edit:  Did some more reading.  Could this be because I have a new z-wave module so it's a 500 series but my ISY is only on version 4.8?  If so, should I remove the card, do the upgrade, and then install the card?
 

[blueman2]

6 hours ago, GregE said:

Was looking to upgrade my version 4.8 ISY994i and was following the list and it said to make sure your z-wave firmware was at 4.55 but when I look at mine I see this.  Did I miss a step when I installed it?  Only z-wave device installed in my network is a repeater currently so no big deal whatever I need to do.  I got it so I could install a z-wave switch on my water heater since Insteon got rid of theirs but haven't gotten to it yet.

 

Edit:  Did some more reading.  Could this be because I have a new z-wave module so it's a 500 series but my ISY is only on version 4.8?  If so, should I remove the card, do the upgrade, and then install the card?
 

I recall seeing the same thing for 0.00 bootloader on series 500 dongle.  Unless someone else chimes in, I think this is normal.   What menu item did you click to get that message?  

[gviliunas]

This is normal.  I believe that the 500 series chip does not need a boot loader.

[astar]

1 hour ago, blueman2 said:

I recall seeing the same thing for 0.00 bootloader on series 500 dongle.  Unless someone else chimes in, I think this is normal.   What menu item did you click to get that message?  

 

When I click on Z-Wave version (5.2.0RC3) I see a total different popup..  (??)

 

 

[lilyoyo1]

1 hour ago, AStarink said:

 

When I click on Z-Wave version (5.2.0RC3) I see a total different popup..  (??)

 

 

That's the firmware version. The bootloader is 0.00

 

[gviliunas]

Yes, it looks like UDI took the Boot Loader line out with v5.2.0 RC3. That is okay. 6.81.00 is the latest version so you have no problem here.

The 500 series doesn't need a Boot Loader

[GregE]

13 hours ago, blueman2 said:

I recall seeing the same thing for 0.00 bootloader on series 500 dongle.  Unless someone else chimes in, I think this is normal.   What menu item did you click to get that message?  

Z-Wave||Advanced||Z-Wave Version.

I was also asking because there is no version on my screen but I think that's because I am only at ISY version 4.8 right now.

[MrBill]

26 minutes ago, GregE said:

Z-Wave||Advanced||Z-Wave Version.

I was also asking because there is no version on my screen but I think that's because I am only at ISY version 4.8 right now.

I'm not sure why UDI has chimed in here, but I think you've hit the nail on the head... V4.8 doesn't know what a series 500 dongle is, so it displays nothing.

I'm only making an educated guess tho....  I haven't tried various configurations....

[lilyoyo1]

19 minutes ago, MrBill said:

I'm not sure why UDI has chimed in here, but I think you've hit the nail on the head... V4.8 doesn't know what a series 500 dongle is, so it displays nothing.

I'm only making an educated guess tho....  I haven't tried various configurations....

You're probably right since the 500 board isn't compatible with 4.0. I think support came around 5.0.13 or somewhere around there

[tibbar]

On 9/7/2020 at 11:47 AM, blueman2 said:

 

1. synchronizing each device, one by one, by bringing them near the ISY

Still running v5.0.16.C afraid of upgrading for this reason.

I still have few outlets and door locks Gen3 and it would be PITA to bring it close to ISY. ISY should have taken approach to this like VERA3. 

Wireless WiFi and ability to run without Insteon Modem so you could bring ISY close to Zwave device. Much easier then bringing device to ISY.

[asbril]

18 minutes ago, tibbar said:

Still running v5.0.16.C afraid of upgrading for this reason.

I still have few outlets and door locks Gen3 and it would be PITA to bring it close to ISY. ISY should have taken approach to this like VERA3. 

Wireless WiFi and ability to run without Insteon Modem so you could bring ISY close to Zwave device. Much easier then bringing device to ISY.

When I moved from 5.0.16 to 5.2 I did not have that issue. It was pretty smooth.

[lilyoyo1]

28 minutes ago, tibbar said:

Still running v5.0.16.C afraid of upgrading for this reason.

I still have few outlets and door locks Gen3 and it would be PITA to bring it close to ISY. ISY should have taken approach to this like VERA3. 

Wireless WiFi and ability to run without Insteon Modem so you could bring ISY close to Zwave device. Much easier then bringing device to ISY.

You can run zwave without insteon. Simply use the zwave only firmware. Insteon will still work. Polisy has a wifi version which would allow you to carry it around. While that doesn't help you now, it will in the future once isy is ported over.