Bridging Vera2 as a secondary controller to Vera3

Community Playground General Discussions
1

Does anyone bridge Vera2 as a secondary controller to Vera3?
I have a new Vera 3 which is great except there are a few compatibility bugs to work out with certain devices like HSM100. I am considering adding my Vera2 UI4 as a slave to Vera3 UI5.
Would I still have the device compatibility issues?

Thank,
dlwertz57

2

I think you could try setting up Vera2/UI4 as primary with her own set of devices, and then import those into Vera3/UI5 (i.e. the bridging method), so you get to control everything from Vera3/UI5.

3

Do you think this would work the other way using the UI4 unit as the “master”

4

OK…
This was way too simple…
http://docs5.mios.com/doc.php?language=1&manual=1&platform=0&page=multiple_mios
2 Veras (Vera2 and Vera3)
Select which Vera will control the system.
In my case it was my Vera3

Add device (uPnP)
-Vera scans the network and provides a list from your network
-Select your Veras (mine was Vera2) that you want to control
-All of the devices are imported and show up in the master (Vera3).
-Create all scenes in the master to eliminate confusion.

Done!

2 reasons to do this
Distance from the controller (Ethernet extends the distance)
Some devices don’t work well on the master controller (e.g HSM100)

5

I have the same setup (Vera2 as secondary bridged with VeraLite as primary) and works just fine but I need now to remove the Vera2 from the z-wave network to use it elsewhere. I tried removing it as a z-wave controller but it didn’t work.

Anyone knows how can this be done?

Roy.

6

[quote=“Roy S, post:5, topic:170414”]I have the same setup (Vera2 as secondary bridged with VeraLite as primary) and works just fine but I need now to remove the Vera2 from the z-wave network to use it elsewhere. I tried removing it as a z-wave controller but it didn’t work.

Anyone knows how can this be done?

Roy.[/quote]

Lets get some terms cleared up first

Bridged via the mios engine is an IP capability NOT a zwave thing. Basically you are simply making the devices visible to the other Vera so you can control them. The devices are only part of the zwave network of the Vera you included them to. There is no secondary or primary concept here. If you are talking bridged… then you simply delete the device and all the share devices disappear from the bridged Vera. You will then need to add those devices on the remaining vera’s zwave network through inclusion.

IF you are talking secondary controller to a primary controller then that IS a zwave thing. Then you need to follow zwave methods for removing a seconday controller

7

@aschwalb,

That’s what I thought at first but after completing the bridging I did a controller shift and now the new VeraLite is the primary controller (Master SIS:NO PRI:YES) while the old Vera2 is the secondary (Slave SIS:NO PRI:NO)
If I turn off the old Vera2, I can still control all the devices. And I cannot exclude any of the z-wave devices from the Vera2 using the usual method.

Roy.

8

[quote=“Roy S, post:7, topic:170414”]@aschwalb,

That’s what I thought at first but after completing the bridging I did a controller shift and now the new VeraLite is the primary controller (Master SIS:NO PRI:YES) while the old Vera2 is the secondary (Slave SIS:NO PRI:NO)
If I turn off the old Vera2, I can still control all the devices. And I cannot exclude any of the z-wave devices from the Vera2 using the usual method.

Roy.[/quote]

so you did both? Then the Vera 2 is just a secondary controller (which means you cannot include or exclude devices from it). The zwave deivces are on the master z-wave network so the only thing you have to do is run the convert 2.78 to 3.2 hack on Vera2. this forces Vera2 to become master again (Slave SIS:NO PRI: YES). That is in the setup->zwave->advanced area (by memory so it may be close) I dont know how else to make Vera master again… The Vera3 unit should be fine and not care.