CLOSED --- Z-Wave 500 Series Beta

[mwester]

Sorry, I guess you'll have to wait until the industry comes with zed-wave for y'all up there.

[Michel Kohanim]

Teken,

If you can send us a USPS return label, then it's much less daunting for us.

With kind regards,

Michel

[PurdueGuy]

Installed the new module tonight with no issues (much easier to install without flexing the case around the LED!).

My Z-Wave locks and HSM200 works like normal.

Healed the network (have a few devices offline due to some electrical work), but otherwise fine.

I noticed I have some Z-Wave outlets.  The status wasn't populated, so I hit Query. and I would get

Fri 07/13/2018 12:40:28 AM : [ZWAVE-WAKEUP  17.000] Query device when awake ZW017_1

The device is set to "Always Awake -> Yes" in the Z-Wave submenu.  After I turned them off/on from the AC, then query seemed to work?

I think we can turn "Query all at restart" back on?  That had to be off just for the initial installation of the module, right?

I tried adding my VRCZ4 (Vizia RF+ Zone Controller) - it was recognized as a controller, but I can't do anything with it.  I added the node details.

VRCZ4_Details.txt

[rhdph1]

Email sent...

Backup in progress...WOW it really does take a lot of time to back it up and I got only few Zwave devices...

 

[Michel Kohanim]

Hello everyone,

Thanks so very much for the interest. Here are the instructions again:

• You must be running 5.0.13 
• You must backup your Z-Wave dongle (Z-Wave | Tools | Backup) … this is going to take a LONG time so, if you decide to go for this beta, it's best to backup now 
• Disable query at restart
• Replace the dongle
• Restore your Z-Wave dongle by doing Z-Wave | Tools | Restore … this is going to be pretty fast
• Test communications, backup, and range (should be a little better)
• If communications are not good, try a Network Heal

With kind regards,
Michel

[DaveF]

My new dongle just arrived in the mail.  Followed all the steps above and have it running.  Several devices failed to update on the network heal, but then it looped back around to them and then got 'success'. Range definitely seems better, before I only had a couple of devices that were 'neighbors' to my ISY, now pretty much all of them are.

[blueman2]

11 hours ago, PurdueGuy said:

...

I noticed I have some Z-Wave outlets.  The status wasn't populated, so I hit Query. and I would get

Fri 07/13/2018 12:40:28 AM : [ZWAVE-WAKEUP  17.000] Query device when awake ZW017_1

The device is set to "Always Awake -> Yes" in the Z-Wave submenu.  After I turned them off/on from the AC, then query seemed to work?

FYI, I have also noticed this in 5.0.12 and 5.0.13.  ALL z-wave devices show "Query device when awake" when queried, even those that are wired in and never sleep.  But in reality, they are being queried immediately, so I always ignored this line in the event viewer.  

My 500 module just arrived and I will install after my backup is complete.  I decided to do another backup since last one was a couple days ago and I changed some z-wave devices since then. 

[blueman2]

Did the install, and have a few issues.  I cannot get my front door to give a response, and most of my other z-wave devices are not being seen for some reason.  Attached is my event viewer level 3 log (started right after boot).  Of note the the following that I get during network heal:

Fri 07/13/2018 02:03:56 PM : [ZWAVE-HEAL    47] Updating Neighbors for 'ZW 047 Front Door' : Time allowed=103 seconds

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    47] Updating Neighbors for 'ZW 047 Front Door' failed to start

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    48] Updating Neighbors for 'ZW 048 Aeon Repeater LR' : Time allowed=103 seconds

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    48] Updating Neighbors for 'ZW 048 Aeon Repeater LR' failed to start

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    49] Updating Neighbors for 'ZW 049 Aeon6 Outside Den' : Time allowed=103 seconds

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    49] Updating Neighbors for 'ZW 049 Aeon6 Outside Den' failed to start

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    50] Updating Neighbors for 'ZW 050 Aeon6 Solar Bypass' : Time allowed=103 seconds

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    50] Updating Neighbors for 'ZW 050 Aeon6 Solar Bypass' failed to start

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    51] Updating Neighbors for 'ZW 051 Aeon6 Garage' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    51] Updating Neighbors for 'ZW 051 Aeon6 Garage' failed to start

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    52] Updating Neighbors for 'ZW 052 HEM Pool 220V' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    52] Updating Neighbors for 'ZW 052 HEM Pool 220V' failed to start

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    54] Updating Neighbors for 'ZW 054 Gen5 On-Off-USB Hallwa' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    54] Updating Neighbors for 'ZW 054 Gen5 On-Off-USB Hallwa' failed to start

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    55] Updating Neighbors for 'ZW 055 On-Off Power Switch' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    55] Updating Neighbors for 'ZW 055 On-Off Power Switch' failed to start

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    56] Updating Neighbors for 'ZW 056 Repeater Garage' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    56] Updating Neighbors for 'ZW 056 Repeater Garage' failed to start

Fri 07/13/2018 02:03:58 PM : Network Heal complete

I have done 2 network heals with the same result.  Also tried device synchronize, with no joy.  

ISY-Events-Log.v5.0.13__Fri 2018.07.13 02.06.38 PM.zip

[PurdueGuy]

2 minutes ago, blueman2 said:

Did the install, and have a few issues.  I cannot get my front door to give a response, and most of my other z-wave devices are not being seen for some reason.  Attached is my event viewer level 3 log (started right after boot).  Of note the the following that I get during network heal:

Fri 07/13/2018 02:03:56 PM : [ZWAVE-HEAL    47] Updating Neighbors for 'ZW 047 Front Door' : Time allowed=103 seconds

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    47] Updating Neighbors for 'ZW 047 Front Door' failed to start

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    48] Updating Neighbors for 'ZW 048 Aeon Repeater LR' : Time allowed=103 seconds

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    48] Updating Neighbors for 'ZW 048 Aeon Repeater LR' failed to start

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    49] Updating Neighbors for 'ZW 049 Aeon6 Outside Den' : Time allowed=103 seconds

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    49] Updating Neighbors for 'ZW 049 Aeon6 Outside Den' failed to start

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    50] Updating Neighbors for 'ZW 050 Aeon6 Solar Bypass' : Time allowed=103 seconds

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    50] Updating Neighbors for 'ZW 050 Aeon6 Solar Bypass' failed to start

Fri 07/13/2018 02:03:57 PM : [ZWAVE-HEAL    51] Updating Neighbors for 'ZW 051 Aeon6 Garage' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    51] Updating Neighbors for 'ZW 051 Aeon6 Garage' failed to start

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    52] Updating Neighbors for 'ZW 052 HEM Pool 220V' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    52] Updating Neighbors for 'ZW 052 HEM Pool 220V' failed to start

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    54] Updating Neighbors for 'ZW 054 Gen5 On-Off-USB Hallwa' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    54] Updating Neighbors for 'ZW 054 Gen5 On-Off-USB Hallwa' failed to start

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    55] Updating Neighbors for 'ZW 055 On-Off Power Switch' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    55] Updating Neighbors for 'ZW 055 On-Off Power Switch' failed to start

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    56] Updating Neighbors for 'ZW 056 Repeater Garage' : Time allowed=103 seconds

Fri 07/13/2018 02:03:58 PM : [ZWAVE-HEAL    56] Updating Neighbors for 'ZW 056 Repeater Garage' failed to start

Fri 07/13/2018 02:03:58 PM : Network Heal complete

I have done 2 network heals with the same result.  Also tried device synchronize, with no joy.  

You did the Z-Wave Restore, right?

[blueman2]

1 minute ago, PurdueGuy said:

You did the Z-Wave Restore, right?

Yup!

[blueman2]

I am finding that many of my z-wave devices are working, but only if they are able to directly talk to the ISY.  No ability to do any neighbor sharing apparently.  I check devices one by one doing z-wave show device links, and the only links that every show up is the ISY itself. No neighbors.

[MWareman]

I am finding that many of my z-wave devices are working, but only if they are able to directly talk to the ISY.  No ability to do any neighbor sharing apparently.  I check devices one by one doing z-wave show device links, and the only links that every show up is the ISY itself. No neighbors.

Have you done a heal yet?

[blueman2]

Yes,  3 heals.  You can see them in the Event Viewer log I attached.  Rechecked, and none of my 15 or so z-wave devices have any neighbors.  Only the ISY is listed.  Very odd.  I may have to go back to the old dongle and try it all again.  

[blueman2]

I rebooted the ISY twice now, and my PC as well.  Have done 5 network heals.  In all cases, none of my z-wave devices ends up with any neighbors except the ISY itself.  The good news is that the new 500 Series dongle has AMAZING range!  It is able to talk to most of the devices in my house.   But without any neighbor communications, several are not able to be communicated with.  

I plan to do another z-wave restore and see if that helps. If not, I will re-install my old z-wave dongle and see what happens. 

Oh, and I did turn off Query All on startup.  I tried doing another query all, but that did not help either.  I have left Query All on startup turned off for now.  

 

 

[blueman2]

Went from scratch again. Did a z-wave restore, then tried the heal again, but as you can see in the Event Viewer logs if you look closely, every attempt to send network neighbor updates fails.  And every device has only one neighbor: the ISY.  I am going to punt for now and go back to the original dongle just to make sure that works OK.  Attached is the event log for the second attempt.  

ISY-Events-Log.v5.0.13__Fri 2018.07.13 03.23.25 PM.zip

[Michel Kohanim]

Hi @blueman2,

What if you just restore your Z-Wave backup and do NOT do a heal at all. How's performance without the heal?

With kind regards,
Michel

 

[blueman2]

Just now, Michel Kohanim said:

Hi @blueman2,

What if you just restore your Z-Wave backup and do NOT do a heal at all. How's performance without the heal?

With kind regards,
Michel

 

Let me try that now.  I currently have the old z-wave dongle in my ISY just to reconfirm all is working.  Once that settles down, I will replace it again with the new dongle and do a restore without heal.  

[blueman2]

@Michel Kohanim, just did another restore of z-wave without doing a heal.  The neighbors are all there, but communications are very spotty right now.  I am tempted to do another heal just to see......

 

BTW, I noticed in the Show Network details it now shows which routes most recently were used.  Is that new?  It is very nice to be able to see what routes actually are being taken for diagnostics of the network.  Nice! 

[Michel Kohanim]

Hi @blueman2, before doing a heal, can you please try Z-Wave | Tools | Synchronize Nodes | All? 

If that does not help, please try Z-Wave | Advanced | Factory Reset  and then retry another Restore.

With kind regards,
Michel

[blueman2]

OK.  I did a synchronize all last time, but that was after the heal.  Will let you know....

UPDATE: @Michel KohanimOK, did the synch.  Did not seem to change anything except to restore some deleted z-wave devices I no longer have.  But I then tried the heal again and it seemed to go a bit better.  I am seeing neighbors on the devices, and communications appear to be at least as good as before.  Front door lock still not reliable.  

But just for testing purposes, I decided to install my old z-wave board again, do another FULL backup, switch in the new board, and do a restore and then heal.  And this time it appeared to work just fine, without a Synchronize ALL.  And Front Door is now working fine, apparently.  So either my prior backup was somehow bad, or I did something else wrong in the install process.  

I will continue to test and see what else I can break!

 

 

[blueman2]

Well, it appears I am still having alot of communications issues.  Front Door Lock is very spotty, and other z-wave devices are not as reliable as with the other z-wave board.  I will leave the new board in for a couple days to see if it improves, but there must be something wrong with my setup.  

[DaveF]

Not sure if this is a dongle issue or 5.0.13 as I was having issues after installing the beta.  My Schlage lock is not behaving.  I decided to punt and exclude it and re-include it, but it is still not reporting events reliabiy and queries are failing.

[blueman2]

7 minutes ago, DaveF said:

Not sure if this is a dongle issue or 5.0.13 as I was having issues after installing the beta.  My Schlage lock is not behaving.  I decided to punt and exclude it and re-include it, but it is still not reporting events reliabiy and queries are failing.

And yes, the biggest issue I am having is with a Schlage.  The 2 Schlages I have which are closer to the ISY appear to be working a bit better, but still not well. The one that relies on Neighbors is not working.  

 

Here is event viewer when I query 46 (closer to the ISY) and 47 (further from the ISY)

Fri 07/13/2018 06:07:12 PM : [ZWAVE-WAKEUP  46.000] Query device when awake ZW046_1
Fri 07/13/2018 06:07:13 PM : [ZW-TX-FAILED] enc=Fail uid=9.0 cmd=0x86.13 VERSION
Fri 07/13/2018 06:07:15 PM : [ZW-TX-FAILED] enc=Ok uid=46.0 cmd=0x80.02 BATTERY
Fri 07/13/2018 06:07:22 PM : [ZW-TX-FAILED] enc=Ok uid=9.0 cmd=0x86.13 VERSION
Fri 07/13/2018 06:07:23 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x80.02 BATTERY
Fri 07/13/2018 06:07:24 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x80.02 BATTERY
Fri 07/13/2018 06:07:24 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x62.02 DOOR_LOCK
Fri 07/13/2018 06:07:25 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x62.02 DOOR_LOCK
Fri 07/13/2018 06:07:25 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x62.02 DOOR_LOCK
Fri 07/13/2018 06:07:25 PM : [     ZW046_1]       ST 101 (uom=11 prec=0)
Fri 07/13/2018 06:07:27 PM : [ZWAVE-WAKEUP  47.000] Query device when awake ZW047_1
Fri 07/13/2018 06:07:31 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x71.07 NOTIFICATION
Fri 07/13/2018 06:07:40 PM : [ZWAVE-MISC      ] ZW046_1 : Schlage : Unrecognized 0x06FE
Fri 07/13/2018 06:07:45 PM : [ZWAVE-MISC      ] ZW046_1 : Schlage : Unrecognized 0x07FE
Fri 07/13/2018 06:07:52 PM : [ZW-TX-FAILED] enc=Ok uid=47.0 cmd=0x71.04 NOTIFICATION
Fri 07/13/2018 06:07:55 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x71.04 NOTIFICATION
Fri 07/13/2018 06:07:56 PM : [ZW-TX-FAILED] enc=Fail uid=47.0 cmd=0x71.04 NOTIFICATION
Fri 07/13/2018 06:07:56 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x71.04 NOTIFICATION
Fri 07/13/2018 06:07:56 PM : [ZW-TX-FAILED] enc=Fail uid=47.0 cmd=0x71.04 NOTIFICATION
Fri 07/13/2018 06:08:02 PM : [ZW-TX-FAILED] enc=Fail uid=46.0 cmd=0x71.04 NOTIFICATION

 

[DaveF]

4 minutes ago, blueman2 said:

And yes, the biggest issue I am having is with a Schlage.  But the other 2 Schlages I have which are closer to the ISY appear to be working OK.  Just the one that relies on Neighbors is not working.  

I have a Schlage and a Yale lock, about the same distance from the ISY (@10 feet).  The Yale is working fine.

[rccoleman]

All good here.  As before, I have to manually query my three Kwikset locks before I can see the state, battery status, or lock/unlock them.  After I run a query, they work fine.  I still get a "Request Failed" when querying my MIMOlite sensor/relay, but I mentioned that in the 5.0.13A thread.