2nd z-net
Before I go and make a huge mistake, would like suggestions on proper configuration.
I have a long ranch house, with the primary z-net on one end of the house to pick up the devices in the garage. I decided to purchase a second with the plan of installing it on the other end for those devices.. which some times have communication issues and multiple routes seem to be killing the battery life on the devices in between. It was my understanding that you can add a 2nd z-net and use the " make this interface an inclusive controller on another network". I thought this would leave the second z-net on a separate network, but now see that it makes it a secondary controller on the main network.
I have seen many cases of this not being recommended and to use separate networks, but then I can't let the system choose the best path, which was my plan, add a node to either and optimize the route.
So a few questions if someone can assist
Does "make this interface an inclusive controller on another network" work? if not why the option?
Why does the information for the z-net describe being able to add devices to either and optimizing for best route?
What is the best method?
Will the above work for only 50 devices?
I also noticed that in the install instructions for the z-net, it really doesn't cover if it is the second, only how to move from one to another, it could use some editing.
I can see if my network grows, how and why I might want a separate network all together, the limit mentioned seems to be 100, doubt I will ever hit 100 in this house. I plan on taking this to the workshop outside, and will put it on another network. but for now, still just worried about the devices in the house and the battery life of the devices passing hop data along (one is a door lock on a door that is never used, it seems to be the mid point and is used by all the devices in the far side of the house)
Suggestions welcomed... PLEASE..lol
Before I go and make a huge mistake, would like suggestions on proper configuration.
I have a long ranch house, with the primary z-net on one end of the house to pick up the devices in the garage. I decided to purchase a second with the plan of installing it on the other end for those devices.. which some times have communication issues and multiple routes seem to be killing the battery life on the devices in between. It was my understanding that you can add a 2nd z-net and use the " make this interface an inclusive controller on another network". I thought this would leave the second z-net on a separate network, but now see that it makes it a secondary controller on the main network.
I have seen many cases of this not being recommended and to use separate networks, but then I can't let the system choose the best path, which was my plan, add a node to either and optimize the route.
So a few questions if someone can assist
Does "make this interface an inclusive controller on another network" work? if not why the option?
Why does the information for the z-net describe being able to add devices to either and optimizing for best route?
What is the best method?
Will the above work for only 50 devices?
I also noticed that in the install instructions for the z-net, it really doesn't cover if it is the second, only how to move from one to another, it could use some editing.
I can see if my network grows, how and why I might want a separate network all together, the limit mentioned seems to be 100, doubt I will ever hit 100 in this house. I plan on taking this to the workshop outside, and will put it on another network. but for now, still just worried about the devices in the house and the battery life of the devices passing hop data along (one is a door lock on a door that is never used, it seems to be the mid point and is used by all the devices in the far side of the house)
Suggestions welcomed... PLEASE..lol
Comment