I've searched threads about setting up a secondary znet ccontroller .I'm confused how to do it .I would like step by step instructions written for someone who may not be the brightest bulb in the box. My primary works great. Just not getting coverage in some parts of the house .
Announcement
Collapse
No announcement yet.
Secondary znet
Collapse
X
-
If you're having issues in a remote area you might think about just putting on a second znet, as opposed to a secondary controller. Run two networks.Blair
HomeSeer: HS3 Pro | Blue-Iris 4 on Windows10Pro
| Devices: 832 | Events: 211 |
Plug-Ins: Z-Wave | RFXCOM | UltraRachio3 | Sonos
BLLAN | BLLOCK | NetCAM | Global Cache Pro | Blue-Iris4
Comment
-
Originally posted by joewilly1 View PostI've searched threads about setting up a secondary znet ccontroller .I'm confused how to do it .I would like step by step instructions written for someone who may not be the brightest bulb in the box. My primary works great. Just not getting coverage in some parts of the house .
To start things off:
Pros multiple one network
1. Network wide inclusion (NWI)
2. The controller determines best routing and assigned closest z-net
3. Redundant controller - all z-sticks have network data
4. Provide greater density of network and mesh.
5. Best deployed were there is a dead zone in mesh
Pro multiple separate networks.
1. Granular control over networks
2. Provides greater coverage for deployments.
4. Can be used a multiple locations
5. Good for large deployments
Comment
Comment