Jump to content

Recommended Posts

Posted (edited)

In preparation for my move from 994 to eisy and the matter board when it gets here, I was looking at excluding a Z-Wave device.  Throughout the documentation, I find “Select Remove/Exclude a Z-Wave Device.”  It even shows that in a screen-shot.  However, from the menu bar I only have “Remove a Z-Wave Device”, missing the “/Exclude.”  Is this is just a typo, versioning, or am I missing something?  As I’m going to re-build my ~30 device Z-Wave network I was hoping I could perform exclusion without having to visit every device and press a button.  Then again, this is probably just a “safety” feature requiring physical interaction with the device to prevent excluding the wrong device.  Must I physically visit each device?

994i, FW is at 5.3.4, product Z-Wave (21100) is installed, ZW Version 6.82.01 . 

Is the missing “/Exclude” in my menu just a typo, and/or I can or cannot exclude just by address without paying the Z-Wave device a visit a button press event? 

Thanks,

Grant

image.png.162073aaec7d7ebdf281cc7c39d31f86.png

Edited by GJ Software Products
Posted

When you are ready for your move, you can exclude first, then include all on eisy.

It is best whenever adding a Zwave device, even brand new, to exclude before adding.

 

Posted (edited)
3 minutes ago, DennisC said:

It is best whenever adding a Zwave device, even brand new, to exclude before adding

@DennisCis correct but be aware that the device may already have been "excluded" and as such it may not react to the exclusion.

I have made a "portable" switch box that I use to exclude/include switches near the ISY/Polisy/eisi before mounting them in the desired location.

Edited by asbril
  • Like 1
Posted
11 hours ago, GJ Software Products said:

In preparation for my move from 994 to eisy and the matter board when it gets here, I was looking at excluding a Z-Wave device.  Throughout the documentation, I find “Select Remove/Exclude a Z-Wave Device.”  It even shows that in a screen-shot.  However, from the menu bar I only have “Remove a Z-Wave Device”, missing the “/Exclude.”  Is this is just a typo, versioning, or am I missing something?  As I’m going to re-build my ~30 device Z-Wave network I was hoping I could perform exclusion without having to visit every device and press a button.  Then again, this is probably just a “safety” feature requiring physical interaction with the device to prevent excluding the wrong device.  Must I physically visit each device?

994i, FW is at 5.3.4, product Z-Wave (21100) is installed, ZW Version 6.82.01 . 

Is the missing “/Exclude” in my menu just a typo, and/or I can or cannot exclude just by address without paying the Z-Wave device a visit a button press event? 

Thanks,

Grant

image.png.162073aaec7d7ebdf281cc7c39d31f86.png

Exclude and remove mean the same thing.

  • Like 1
Posted

@lilyoyo1Thanks.  That's what I thought but when the GUI (menu bar) and the docs didn't match I figured I'd throw a request for clarification out there with all the problems I'm seeing out there I definitely can't risk bricking my 994.  That's why when my Matter get's here I'm gonna move one device at a time.  Fortunately I don't have any 15' ceilings and I'll exclude/reset/add the devices one at a time maybe just fire up my laptop and walk around the house.

Posted
14 minutes ago, GJ Software Products said:

@lilyoyo1Thanks.  That's what I thought but when the GUI (menu bar) and the docs didn't match I figured I'd throw a request for clarification out there with all the problems I'm seeing out there I definitely can't risk bricking my 994.  That's why when my Matter get's here I'm gonna move one device at a time.  Fortunately I don't have any 15' ceilings and I'll exclude/reset/add the devices one at a time maybe just fire up my laptop and walk around the house.

Depending on how quickly you're planning on moving things, you're potentially making things worse. Zwave use a routed mesh network. Every device you remove from your current network can potentially effect other devices down from that device. 

Depending on your devices, your network can potentially self heal but that's not an instantaneous thing. The more you remove, the worse it can potentially get. 

In addition, due to how network wide inclusion works, it can be harder to remove/include devices from their installed location (assuming all devices support NWI). 

Posted (edited)
3 hours ago, asbril said:

@DennisCis correct but be aware that the device may already have been "excluded" and as such it may not react to the exclusion.

I have made a "portable" switch box that I use to exclude/include switches near the ISY/Polisy/eisi before mounting them in the desired location.

@asbrilI like the switch box idea.  Back when I moved to Z-Wave it was a PITA when you installed a switch in it's final resting place then had to take it back out and move closer to the hub to associate the new device.  Thanks,  Grant

@lilyoyo1Thanks.  Yea I was thinking about that messing up the routing tables and how long it would take to heal.  Will Update Neighbors or Synchronize help speed things up?  When I first deployed my Z-Wave as expected, the longer it ran the better it got.  I forgot if there is a "Heal" action in the ISY.  Or will it just take time?  I was going to look at the devices neighbors and try to build a strategy/sequence depending on who is supporting who...

Edited by GJ Software Products
Posted
11 minutes ago, GJ Software Products said:

@asbrilI like the switch box idea.  Back when I moved to Z-Wave it was a PITA when you installed a switch in it's final resting place then had to take it back out and move closer to the hub to associate the new device.  Thanks,  Grant

@lilyoyo1Thanks.  Yea I was thinking about that messing up the routing tables and how long it would take to heal.  Will Update Neighbors or Synchronize help speed things up?  When I first deployed my Z-Wave as expected, the longer it ran the better it got.  I forgot if there is a "Heal" action in the ISY.  Or will it just take time?  I was going to look at the devices neighbors and try to build a strategy/sequence depending on who is supporting who...

The update neighbors can help but depending on what's removed, distance can be a factor. Whether it affects the 994 or EISY routing is hard to say. 

Posted

@lilyoyo1Thanks.  I had a pretty good idea distance was going to be a hurdle.  Of course my front door lock is one of the furthest away.  Through the most solid walls.  Murphy's Law, right?  I thought I read somewhere those Aeotech Range Extenders forward regardless of HomeID.  Do you know if that's true?  I've got a fair amount of those spread throughout the house from when I originally deployed Z-Wave.  

Posted (edited)
18 minutes ago, GJ Software Products said:

@lilyoyo1Thanks.  I had a pretty good idea distance was going to be a hurdle.  Of course my front door lock is one of the furthest away.  Through the most solid walls.  Murphy's Law, right?  I thought I read somewhere those Aeotech Range Extenders forward regardless of HomeID.  Do you know if that's true?  I've got a fair amount of those spread throughout the house from when I originally deployed Z-Wave.  

Not that I am aware of. The whole point in routing is everything being aware of other things so aeotech repeating messages could indiscriminately would make things worse vs helping. 

Edited by lilyoyo1
Posted
1 minute ago, lilyoyo1 said:

Not that I am aware of. The whole point in row is everything being aware of other t things so aeotech repeating messages could indiscriminately would make things worse vs helping. 

Yea I had quite the popcorn effect awhile back from this lock, every once in awhile I'd get ~20 notifications door locked instead of one.  But not always.  That seemed to settle down over time, I haven't experienced it in awhile, but it sure looked like too many messages floating around out there on the air waves.

Guest
This topic is now closed to further replies.

×
×
  • Create New...