We have moved at community.getvera.com

Author Topic: Master / Slave compared to Bridging  (Read 1397 times)

Offline nathanwinters

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
Master / Slave compared to Bridging
« on: April 03, 2017, 05:41:22 pm »
I'm trying to understand the difference between Primary and Secondary controllers and Bridging. Firstly I assume there is a difference. Secondly, i've got my main house, where the VeraPlus is, and then a cabin at the bottom of the garden which some devices seem to just about work and others seem to be just out of range.
What is the appropriate solution to supporting this second building.

Offline Z-Waver

  • Master Member
  • *******
  • Posts: 4437
  • Karma: +249/-120
Re: Master / Slave compared to Bridging
« Reply #1 on: April 04, 2017, 08:05:25 am »
Master and secondary controllers are part of the same Z-Wave network. They both participate in the same mesh and can communicate without a gateway with any of the devices in the mesh.

Bridging allows two Veras with two discrete Z-Wave networks to share information about devices and activities over the TCP/IP network. When it works, it allows you to view, manage, and control two disparate Z-Wave networks as a single virtual entity. Z-Wave devices in one Z-Wave network cannot communicate with devices in the other. However, the controllers can send commands from one network to the other by using the other Vera(Z-Wave controller) as a gateway. For example, scenes on Vera1 can activate devices on Vera2's Z-Wave network as Vera1 sends a command over the TCP/IP network to Vera2 who then sends the Z-Wave command to the target device.

It's a tough call, based on your description. But I suspect that you would have a more reliable setup if you chose to use two discrete Z-Wave networks, due to their geographic separation. IN such a case bridging is a valid confutation option, but it may not be necessary to bridge, unless you want one Vera to control everything. If you don't, it may be better to leave the two Veras and their networks as separate entities, since bridging can introduce some flakiness with its added complexity.

Offline akbooer

  • Beta Testers
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +292/-70
  • "Less is more"
Re: Master / Slave compared to Bridging
« Reply #2 on: April 04, 2017, 08:24:46 am »
Also, if you choose to use AltUI as an interface (and why would you not?) then you can control 2 separate machine with the one Web interface.
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.