The Vera Community forums have moved!

General => Upgrading => Topic started by: ZwaveOutlet on December 19, 2014, 05:42:50 pm

Title: VeraEdge Bridging Together
Post by: ZwaveOutlet on December 19, 2014, 05:42:50 pm
Seeing if anyone has been able to bridge two VeraEdges together yet?

When scanning for UPNP devices they don't seem to be showing up correctly. The network we are playing on is pretty robust to say the least, so I need to make sure there is not a bug with the new 1.7.906 firmware where it's labeling UPNP devices weird. It could be something to do with the cisco network but I'd like to start somewhere easier. So let me know if you have successfully bridged 2 veraedges together.

Another idea that I have been playing with is to manually add the other veraedge mirroring the way I use to on UI5 but that doesn't seem to be working either.

Any insight on this would be awesome!
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on February 26, 2015, 09:00:13 am
I have the same issue.  Bridging my Edge with my Vera Lite on ui5 as slave. It seems that ui7 on the edge does not detect it under upnp devices.  It detects a whole bunch of other devices.   I logged this with very support.   Got a reply from them that they were able to reproduce the issue,  and that they will fix it in some future release...  (roll eyes).   No workaround available yet.
Title: Re: VeraEdge Bridging Together
Post by: integlikewhoa on February 26, 2015, 01:19:10 pm
I have the same issue.  Bridging my Edge with my Vera Lite on ui5 as slave. It seems that ui7 on the edge does not detect it under upnp devices.  It detects a whole bunch of other devices.   I logged this with very support.   Got a reply from them that they were able to reproduce the issue,  and that they will fix it in some future release...  (roll eyes).   No workaround available yet.

I would be surprised if Bridging ever works with two different UI's. Both should be on UI7 first.
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on February 26, 2015, 01:21:53 pm
I don't agree with you integlikewhoa.   As the bridging is a function of the exposed upnp properties,  and this is a set standard,  and not specific to the UI versions.
Title: Re: VeraEdge Bridging Together
Post by: garrettwp on February 26, 2015, 01:24:22 pm
In order for bringing to work they MUST be on the same firmware version. This has been stated many times in the past.

- Garrett

Title: Re: VeraEdge Bridging Together
Post by: MrAutomate on March 05, 2015, 08:08:36 pm
@ garrettwp :  I searched for UI7 Bridging, and saw this post.  My Vera lite and My edge are on the same firmware, and both on UI7.  I can see all type of UPNP devices on my LAN, but not the most critical, my vera light from the Edge. 

What am I doing wrong?  Thanks ???
Title: Re: VeraEdge Bridging Together
Post by: integlikewhoa on March 05, 2015, 09:13:04 pm
@ garrettwp :  I searched for UI7 Bridging, and saw this post.  My Vera lite and My edge are on the same firmware, and both on UI7.  I can see all type of UPNP devices on my LAN, but not the most critical, my vera light from the Edge. 

What am I doing wrong?  Thanks ???

I think your problem currently is the EDGE. Currently bridging with the EDGE doesn't work to my knowledge. Support says they working on it.
Title: Re: VeraEdge Bridging Together
Post by: MrAutomate on March 07, 2015, 09:20:18 am
All I wanted to take a minute to updAte this thread also, Support is planning a new firmware update , expected release is this March 2015, and should resolve the UPNP issue.
Title: Re: VeraEdge Bridging Together
Post by: integlikewhoa on March 07, 2015, 12:06:54 pm
All I wanted to take a minute to updAte this thread also, Support is planning a new firmware update , expected release is this March 2015, and should resolve the UPNP issue.

Well they were doing monthly updates, but then they missed Jan. now its more then a month since the last update. And when they say March that will be no sooner then the last day of the month and more likely be the following month at least.
Title: Re: VeraEdge Bridging Together
Post by: Vreo on April 19, 2015, 05:19:43 pm
Hi everyone, I've just recieved my Vera Edge and updated it's firmware to the latest, 1.7.1089, and I am trying to bridge it my VeraLite, leaving the new one as the main one, but still no success, I think things are in the same way as the last post on this thread? No support? Nothing fixed in this firmware regarding that?

BTW, the reason I am trying to bridge and not replacing, is because another bug with Instant Updates of Leviton dimmers treated in this thread: http://forum.micasaverde.com/index.php/topic,29569.50.html So it is bug over bug...
Title: Re: VeraEdge Bridging Together
Post by: integlikewhoa on April 19, 2015, 05:26:39 pm
Hi everyone, I've just recieved my Vera Edge and updated it's firmware to the latest, 1.7.1089, and I am trying to bridge it my VeraLite, leaving the new one as the main one, but still no success, I think things are in the same way as the last post on this thread? No support? Nothing fixed in this firmware regarding that?

BTW, the reason I am trying to bridge and not replacing, is because another bug with Instant Updates of Leviton dimmers treated in this thread: http://forum.micasaverde.com/index.php/topic,29569.50.html So it is bug over bug...

Bridge Mode has never worked on the EDGE. It's on the to do list, but who knows when. It's due to new z-wave chip.
Title: Re: VeraEdge Bridging Together
Post by: Vreo on April 19, 2015, 07:20:58 pm
I found a Solution! ???

Well, I THINK I found a workaround. I have being doing so much testing that I don't even know if this is the setting that finally worked, but I managed to bridge my VeraLite UI6 with my VeraEdge UI7. What I did is that in my VeraLite, which is the only one that allows changing IP address of the LAN parte (which is senseless because it only has one port), I changed the IP from 192.168.81.1 to 192.168.81.2. The VeraEdge comes also with 192.168.81.1, but it is unchangeable. The LANs IP I have set them to my own network, wich are 192.168.1.63 for VeraLite and 192.168.1.64 for the VeraEdge. And suddenly, both Veras found each other.

I THINK this was the solution because if you go to the properties of the device created in Vera, the name is MIOS_XXXXXX and the IP address is 192.168.81.2 and 192.168.81.1 respectively and not the IP of my network.

I don't want to touch any setting in my setup, maybe it was a coincidence or not, but maybe someone wants to try and let us all know if this really works or it was just me being lucky.

Regards.
Title: Re: VeraEdge Bridging Together
Post by: MrAutomate on April 20, 2015, 07:14:45 pm
Vreo- Yeah, that is how I had it working pre UI7, but I just upgraded my 2nd unit :o.  Not sure why they would restrict that on an upgraded platform, it caused us to lose capability. 

I do want  to bridge a few units, and offload apps like the iPhone locater, and Hue due to processing, and memory usage.  Glad you got it working, I'll just wait.
Title: Re: VeraEdge Bridging Together
Post by: RichardTSchaefer on April 20, 2015, 07:38:53 pm
Quote
It's due to new z-wave chip.

That should have nothing to do with it. Bridging is done at a higher level in Vera ... It only knows about devices and device properties (not the kind of devices).
It sounds like Vreo is on to the real problem ... it looks like it's trying to use the  192.168.81.xx subnet as opposed to the subnet the router switch is on..
Title: Re: VeraEdge Bridging Together
Post by: hellovn on May 19, 2015, 02:01:19 am
Anyone could bridge veraedge and veralite? I am planning to upgrade to veraedge and bridge them together. I already sent an email to Vera Control to ask if this is possible but have not received a reply.
Title: Re: VeraEdge Bridging Together
Post by: Vreo on May 19, 2015, 12:19:01 pm
I found a Solution! ???

Well, I THINK I found a workaround. I have being doing so much testing that I don't even know if this is the setting that finally worked, but I managed to bridge my VeraLite UI6 with my VeraEdge UI7. What I did is that in my VeraLite, which is the only one that allows changing IP address of the LAN parte (which is senseless because it only has one port), I changed the IP from 192.168.81.1 to 192.168.81.2. The VeraEdge comes also with 192.168.81.1, but it is unchangeable. The LANs IP I have set them to my own network, wich are 192.168.1.63 for VeraLite and 192.168.1.64 for the VeraEdge. And suddenly, both Veras found each other.

I THINK this was the solution because if you go to the properties of the device created in Vera, the name is MIOS_XXXXXX and the IP address is 192.168.81.2 and 192.168.81.1 respectively and not the IP of my network.

I don't want to touch any setting in my setup, maybe it was a coincidence or not, but maybe someone wants to try and let us all know if this really works or it was just me being lucky.

Regards.
I have mine bridged successfully since then.
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on July 23, 2015, 11:37:06 am
So is it at all possible to bridge two vera edge units?  since you cant set the LAN ip?
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 01, 2015, 10:29:54 am
Ok. After putting some unrelated info together I have managed to bridge two Vera edge units together...  and yes... it works!


Based on info in this thread we could establish that the main issue is that the Vera uses the "LAN"  interface to discover other Vera devices via uPnP.  The only issue is that the LAN interface IP addresses for all Vera edge devices are statically set at the factory to 192.168.81.1.  In the older devices you could change this..... On the new Vera Edge you can't...... Well, maybe you can! ;)


SO I started digging around an came upon another unrelated post in a random thread about how to do some weird stuff with the wireless on a Vera 3.... I put on and one together, and presto...


The Steps:


1. You need to SSH into your vera (
either of them will suffice.  Only do this on ONE of them), using putty or something similar.  You'll also need your vera's root password, or temporarily enable remote support, and use those details.  there is enough info available on this... Google is your friend...
2.  You need to run a couple of commands:
3.  After doing the above, You need to restart BOTH your Veras so that the uPnP service restarts it's discovery.


That's it.... Fully functioning Bridging......!!!!


Warning!!!  I have NO IDEA if this will leave anything broken... So far, for me, it's working perfectly, but don't blame me if this has any negative after effects... at OWN Risk!

Title: Re: VeraEdge Bridging Together
Post by: guest20975 on August 03, 2015, 02:58:10 pm
Tried your method on both my veralite and Vera edge, no success at all on Vera lite no eth0.1
On Vera edge more successful until last command which was refused  as being incorrect. Both Vera's are on latest firmware.
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 03, 2015, 03:07:40 pm
Tried your method on both my veralite and Vera edge, no success at all on Vera lite no eth0.1
On Vera edge more successful until last command which was refused  as being incorrect. Both Vera's are on latest firmware.


I suggest you change this on the Edge, but it should be possible on the Lite also.... maybe run cat /etc/config/network 

The last command is not really important... as long as you reboot or power cycle the Vera, however it MUST work... are you sure you copied it correctly?
If you did it correctly, then if you go to settings->Net & Wifi... You should see the updated LAN IP 192.168.81.2.






Title: Re: VeraEdge Bridging Together
Post by: guest20975 on August 04, 2015, 06:30:16 am
tried originally with Terminal on Macbook Air, then PUTTy on a windows VM this am (UK). No success then used WinSCP to get to the /etc/config/network file, altered the LAN IP address to 192.168.82.2 saved then rebooted my Vera Edge and the Veralite. Success altered the LAN address on Vera Edge the added UPNP device and found VeraLite. The two are now bridged!! Thanks for the info to start with, I am more confident dealing direct with files than with the command prompt these days.
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 04, 2015, 10:57:05 am
Awesome stuff... Sometimes it's about the information you gather from someone else, rather that how they did it.....
Glad you got it working also!!
Title: Re: VeraEdge Bridging Together
Post by: slajgaj on August 06, 2015, 07:23:52 am
Tiaanv!

Can this IP change method working vith Vera Edge UI7 and Vera Edge UI7 ?
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 06, 2015, 07:26:56 am
Tiaanv!

Can this IP change method working vith Vera Edge UI7 and Vera Edge UI7 ?
Yes.   Exactly what it's for.

Sent from my SM-G900F using Tapatalk

Title: Re: VeraEdge Bridging Together
Post by: filippodei on August 16, 2015, 05:41:39 am
Ok. After putting some unrelated info together I have managed to bridge two Vera edge units together...  and yes... it works!


Based on info in this thread we could establish that the main issue is that the Vera uses the "LAN"  interface to discover other Vera devices via uPnP.  The only issue is that the LAN interface IP addresses for all Vera edge devices are statically set at the factory to 192.168.81.1.  In the older devices you could change this..... On the new Vera Edge you can't...... Well, maybe you can! ;)


SO I started digging around an came upon another unrelated post in a random thread about how to do some weird stuff with the wireless on a Vera 3.... I put on and one together, and presto...


The Steps:


1. You need to SSH into your vera (
either of them will suffice.  Only do this on ONE of them), using putty or something similar.  You'll also need your vera's root password, or temporarily enable remote support, and use those details.  there is enough info available on this... Google is your friend...
2.  You need to run a couple of commands:
  • uci set network.lan.ifaddr="192.168.81.2"  (this sets the LAN interface's IP address)
  • uci commit (this saves the changed settings)
  • cat /etc/config/network  (just to review that you changed the setting correctly....)
  • ifconfig eth0.1 down  (this will "down" the LAN interface.  We do this to re-load the settings in a moment)
  • rm /var/state/network (this clears the network cached settings)
  • /etc/init.d/network restart (restart the network)
3.  After doing the above, You need to restart BOTH your Veras so that the uPnP service restarts it's discovery.


That's it.... Fully functioning Bridging......!!!!


Warning!!!  I have NO IDEA if this will leave anything broken... So far, for me, it's working perfectly, but don't blame me if this has any negative after effects... at OWN Risk!
Hello. i tried with Putty from Windows but i received this error:
uci: Parse error (unterminated ') at line 17, byte 31

so, i tried with rbrowser by mac editing the file /etc/config/network file, altered the LAN IP address to 192.168.82.2 saved then rebooted my two Vera Edge but now in the net setting inside the web panel of the edited vera edge i have the field always in dhcp (??? not setted it anytime) and the other important field like 192.168.81.1...empty....!

See the image:https://www.dropbox.com/s/x3xek7llpzkxqif/Vera%E2%84%A2_%E2%96%BE_Smarter_Home_Control.png?dl=0 (https://www.dropbox.com/s/x3xek7llpzkxqif/Vera%E2%84%A2_%E2%96%BE_Smarter_Home_Control.png?dl=0)

Rebooted it and try to control with rbrowser. the file is the corrected, i think, modified before:

Quote
config interface 'loopback'
   option ifname 'lo'
   option proto 'static'
   option ipaddr '127.0.0.1'
   option netmask '255.0.0.0'

config globals 'globals'
   option ula_prefix 'auto'

config interface 'lan'
   option ifname 'eth0.1'
   option type 'bridge'
   option proto 'static'
   option netmask '255.255.255.0'
   option ip6assign '60'
   option ipaddr '192.168.81.1?
   option macaddr '94:4a:0c:08:4b:ba'

config switch_vlan
   option device 'eth0'
   option vlan '1'
   option ports '4 5t'

config interface 'wan'
   option ifname 'br-lan'
   option macaddr '94:4a:0c:08:4b:ba'
   option proto 'static'
   option ipaddr '192.168.101.101'
   option netmask '255.255.255.0'
   option gateway '192.168.101.1'
   option dns '192.168.101.1'

Naturally...or better to use unfortunatly the two vera aren't bridged.  The problems could be that the second vera is in other subnet? I must forwarding any other ports for this? upnp ports (i dont know what are the upnp ports)
thanks
Can anyone help me?
Title: Re: VeraEdge Bridging Together
Post by: konradwalsh on August 16, 2015, 07:36:24 am


Quote

Naturally...or better to use unfortunatly the two vera aren't bridged.  The problems could be that the second vera is in other subnet? I must forwarding any other ports for this? upnp ports (i dont know what are the upnp ports)
thanks
Can anyone help me?


Open up the subnet to allow it..

Change 255.255.255.0 to 255.255.0.0

Sent from my A0001 using Tapatalk

Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 16, 2015, 07:46:15 am
No need to change the subnet. The screenshot attached.  Shows the normal net settings.  Further down you will find the "LAN"  settings.   This ip is on a different subnet.   As long as both veras are on the same subnet it will be fine.

Sent from my SM-G900F using Tapatalk

Title: Re: VeraEdge Bridging Together
Post by: konradwalsh on August 16, 2015, 07:59:27 am
No need to change the subnet. The screenshot attached.  Shows the normal net settings.  Further down you will find the "LAN"  settings.   This ip is on a different subnet.   As long as both veras are on the same subnet it will be fine.

Sent from my SM-G900F using Tapatalk
Ya but he may have a reason he's on a different subnet

Sent from my A0001 using Tapatalk

Title: Re: VeraEdge Bridging Together
Post by: filippodei on August 16, 2015, 08:16:02 am
i have the second vera on different subnet because i have located in a different building near my home connected to my primary lan with point to point by nanostation ubnt. for better use all other equipment that i have installed there, i need to use subnet. so for see for example the webserver page of the second vera, i have port forwarded her port because my first lan is like a "internet world" for the subnet connected by wan.

But about the error and the page of second vera that now are with the empty field? always if i rewrite inside them, after save...same situation.
any chance to fix:
uci: Parse error (unterminated ') at line 17, byte 31
?

thanks for all

I must procede to reset the vera?

Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 16, 2015, 10:49:04 am
i have the second vera on different subnet because i have located in a different building near my home connected to my primary lan with point to point by nanostation ubnt. for better use all other equipment that i have installed there, i need to use subnet. so for see for example the webserver page of the second vera, i have port forwarded her port because my first lan is like a "internet world" for the subnet connected by wan.

But about the error and the page of second vera that now are with the empty field? always if i rewrite inside them, after save...same situation.
any chance to fix:
uci: Parse error (unterminated ') at line 17, byte 31
?

thanks for all

I must procede to reset the vera?
In your script you have a?  After the ip?   That should be a '

Sent from my SM-G900F using Tapatalk

Title: Re: VeraEdge Bridging Together
Post by: filippodei on August 16, 2015, 11:41:12 am
i have the second vera on different subnet because i have located in a different building near my home connected to my primary lan with point to point by nanostation ubnt. for better use all other equipment that i have installed there, i need to use subnet. so for see for example the webserver page of the second vera, i have port forwarded her port because my first lan is like a "internet world" for the subnet connected by wan.

But about the error and the page of second vera that now are with the empty field? always if i rewrite inside them, after save...same situation.
any chance to fix:
uci: Parse error (unterminated ') at line 17, byte 31
?

thanks for all

I must procede to reset the vera?
In your script you have a?  After the ip?   That should be a '

Sent from my SM-G900F using Tapatalk
Thanks but i think that it was copy and paste error of my script, because i check now and my network script is this:


config interface 'loopback'
   option ifname 'lo'
   option proto 'static'
   option ipaddr '127.0.0.1'
   option netmask '255.0.0.0'

config globals 'globals'
   option ula_prefix 'auto'

config interface 'lan'
   option ifname 'eth0.1'
   option type 'bridge'
   option proto 'static'
   option netmask '255.255.255.0'
   option ip6assign '60'
   option ipaddr '192.168.81.1?
   option macaddr '94:4a:0c:08:4b:ba'

config switch_vlan
   option device 'eth0'
   option vlan '1'
   option ports '4 5t'

config interface 'wan'
   option ifname 'br-lan'
   option macaddr '94:4a:0c:08:4b:ba'
   option proto 'static'
   option ipaddr '192.168.101.101'
   option netmask '255.255.255.0'
   option gateway '192.168.101.1'
   option dns '192.168.101.1'


Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 16, 2015, 11:45:00 am
It's still there:



config interface 'lan'
   option ifname 'eth0.1'
   option type 'bridge'
   option proto 'static'
   option netmask '255.255.255.0'
   option ip6assign '60'
   option ipaddr '192.168.81.1?
   option macaddr '94:4a:0c:08:4b:ba'
Title: Re: VeraEdge Bridging Together
Post by: filippodei on August 16, 2015, 11:52:49 am
!
ugly bastard of Rbrowser!
thanks to your info and leads...i see now that when i editing the file by rbrowser by mac, when i delete the .1 in 192.168.81.1 and put at is place .2 the program give me to screen this:
   '192.168.81.1?

Title: Re: VeraEdge Bridging Together
Post by: filippodei on August 16, 2015, 12:16:15 pm
now thanks to you is come back the correct field in the web panel. i have correct set the second vera to 192.168.81.2 but unfortunatly...no way to bridge probably for the different subnet. i tried also to to use 255.255.0.0 on the first vera but any positive results.
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 16, 2015, 12:38:13 pm
Your situation is a little different, as you have the veras running on two seperate lans.  How are you bridging the two lans?  Router?

You could try putting the lan ips as two seperate ips in the same subnet as your wan ip.... In other words... If your veras ip is normally 192.168.0.x. Then put the lan ip with a static ip in the same subnet... That way if your router is doing the nat for the normal data (wan)it should in theory work for the lan...


Sent from my iPad using Tapatalk HD
Title: Re: VeraEdge Bridging Together
Post by: filippodei on August 17, 2015, 02:33:07 am
sorry i didnt understand very well. :(
my lan primary is 192.168.100.x and where is my first vera with 192.168.100.219
from this location i have near other building where i have a cpe wifi that connect to a wifi access point from the primary lan. this cpe have 192.168.100.230 for lan ip in the primary and use it as WAN. then create and dhcp from her a new subnet, 192.168.101.x where 192.168.101.1 is the cpe and where my second vera edge is 192.168.101.100.
I have port forwarded the ports of the 192.168.101.100 for make it visible from the primary lan, for example the 80 for web panel, the 3480 for use it from control4 (and this is the only way for now that make useful have 2 vera, because control4 control some vera edge in a moment)
Probably if we know the port used for upnp...we can hope and try.
Title: Re: VeraEdge Bridging Together
Post by: tiaanv on August 17, 2015, 02:49:21 am
sorry i didnt understand very well. :(
my lan primary is 192.168.100.x and where is my first vera with 192.168.100.219
from this location i have near other building where i have a cpe wifi that connect to a wifi access point from the primary lan. this cpe have 192.168.100.230 for lan ip in the primary and use it as WAN. then create and dhcp from her a new subnet, 192.168.101.x where 192.168.101.1 is the cpe and where my second vera edge is 192.168.101.100.
I have port forwarded the ports of the 192.168.101.100 for make it visible from the primary lan, for example the 80 for web panel, the 3480 for use it from control4 (and this is the only way for now that make useful have 2 vera, because control4 control some vera edge in a moment)
Probably if we know the port used for upnp...we can hope and try.


Sorry.  I am not too knowledgeable on  CPE bridges, so I can't help....  I also am unsure about what ports are used for bridging.
Try this: ?
https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol (https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol)




port 1900...  that in addtion to 3480 might actually work, not sure how the traffic flows both ways, and even if you can discover across subnets..... that doesn't make much sense to me, but it's worth a try...


Good luck.

Title: Re: VeraEdge Bridging Together
Post by: ReneH on September 09, 2015, 06:08:22 am
2.  You need to run a couple of commands:
  • uci set network.lan.ifaddr="192.168.81.2"  (this sets the LAN interface's IP address)
  • uci commit (this saves the changed settings)
  • cat /etc/config/network  (just to review that you changed the setting correctly....)
  • ifconfig eth0.1 down  (this will "down" the LAN interface.  We do this to re-load the settings in a moment)
  • rm /var/state/network (this clears the network cached settings)
  • /etc/init.d/network restart (restart the network)


I tried this method on Vera Edge and Lite but came across a few hurdles.

1. After ifconfig eth0.1 down the ssh is disconnected. This is ok since I can restart the Vera manually but I cannot clear the network cache then.
2. Adding the ifaddr does just adds a option ifaddr in the config file which was not there yet. My ipaddr stays the same also after reboot.
3. If I change and verify the ipaddr it seems all good. But after the reboot the ipaddr is set back to the old factory set ipaddr.

My Vera lite has 192.168.81.1 and the Edge has 192.168.00.78

Any suggestions?
Title: Re: VeraEdge Bridging Together
Post by: pjeterinfo on September 13, 2015, 04:13:16 am
@reneh you can just edit one of the /etc/config/network files so both lan ipadress will be in the same range.
My example:
edge1:
config interface 'lan'
   option ifname 'eth0.1'
   option type 'bridge'
   option proto 'static'
   option netmask '255.255.255.0'
   option ip6assign '60'
   option macaddr '94:4a:0c:08:4d:22'
   option ipaddr '192.168.84.22'

edge2:
config interface 'lan'
   option ifname 'eth0.1'
   option type 'bridge'
   option proto 'static'
   option netmask '255.255.255.0'
   option ip6assign '60'
   option macaddr 'd4:21:22:fc:ce:eb'
   option ipaddr '192.168.84.23'


If you run a ifconfig you will see that the br-lan(bridge) ipadress will match the lan ipadress. This is not the ipadress were you connect to the vera's over http but I assume this is used for bridging.

br-lan    Link encap:Ethernet  HWaddr D4:21:22:FC:CE:EB 
          inet addr:192.168.84.23  Bcast:192.168.84.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8572 errors:0 dropped:96 overruns:0 frame:0
          TX packets:9435 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2973090 (2.8 MiB)  TX bytes:5564099 (5.3 MiB)

I managed to brigde them but I do not see any advantages yet  ??? It would be nice if this ipadress was configurable from the webui.
 
Title: Re: VeraEdge Bridging Together
Post by: sasaba on October 03, 2015, 01:28:43 pm
I have a veralite and a veraedge that I would like to bridge but they don't see each other. I have tried changing the /etc/config/network file on 1st one then the other and it seems to go ok but within a few minutes the file, whether changed on the lite or the edge reverts back to it's original ipaddr value. I am running the latest firmware and I have tried this with both the lite and the edge set as the master controller. Any ideas why new ipaddr settings wont stay permanent?

Edit
I guess this is the same issue ReneH is seeing only I am using the direct edit method of the /etc/config/network file instead of the set of commands he used.
Title: Re: VeraEdge Bridging Together
Post by: rnm on October 05, 2015, 07:25:51 pm
Ok. After putting some unrelated info together I have managed to bridge two Vera edge units together...  and yes... it works!


Based on info in this thread we could establish that the main issue is that the Vera uses the "LAN"  interface to discover other Vera devices via uPnP.  The only issue is that the LAN interface IP addresses for all Vera edge devices are statically set at the factory to 192.168.81.1.  In the older devices you could change this..... On the new Vera Edge you can't...... Well, maybe you can! ;)


SO I started digging around an came upon another unrelated post in a random thread about how to do some weird stuff with the wireless on a Vera 3.... I put on and one together, and presto...


The Steps:


1. You need to SSH into your vera (
either of them will suffice.  Only do this on ONE of them), using putty or something similar.  You'll also need your vera's root password, or temporarily enable remote support, and use those details.  there is enough info available on this... Google is your friend...
2.  You need to run a couple of commands:
  • uci set network.lan.ifaddr="192.168.81.2"  (this sets the LAN interface's IP address)
  • uci commit (this saves the changed settings)
  • cat /etc/config/network  (just to review that you changed the setting correctly....)
  • ifconfig eth0.1 down  (this will "down" the LAN interface.  We do this to re-load the settings in a moment)
  • rm /var/state/network (this clears the network cached settings)
  • /etc/init.d/network restart (restart the network)
3.  After doing the above, You need to restart BOTH your Veras so that the uPnP service restarts it's discovery.


That's it.... Fully functioning Bridging......!!!!


Warning!!!  I have NO IDEA if this will leave anything broken... So far, for me, it's working perfectly, but don't blame me if this has any negative after effects... at OWN Risk!

I used the above procedure, but the IP would not change.  It did give me a another line that had the right IP, but this IP did not take effect.  I had no idea how my VeraEdge had the ip of 192.168.12.24 and while my VeraLite had 192.168.81.1.  The VeraEdge was visible on the VeraLite unp, but the VeraEdge did not show the VeraLite.  After many attempts using the above procedure, I used SCP and using the terminal mode, I edited etc/config/network file and  made the change to the IP 192.168.12.24 to show 192.168.81.2.  After, I rebooted, the Veralite was visible on the VeraEdge and all devices made to trip to the VeraEdge.  I later deleted the second IP line and everything works just great.  It is my feeling that just editing the etc/config/network file is all that is needed to change the IP to get the VeraEdge to bridge to the Veralite.
   
config interface 'lan'
   option ifname 'eth0.1'
   option type 'bridge'
   option proto 'static'
   option netmask '255.255.255.0'
   option ip6assign '60'
   option macaddr 'z4:41:22:fc:b4:ab'
   option ipaddr '192.168.12.24'  1.
   option ifaddr '192.168.81.2'      2.
Title: Re: VeraEdge Bridging Together
Post by: sasaba on October 06, 2015, 05:52:04 pm
Well I finally got the /etc/config/network file change, changing the ipaddr address, to take and remain permanent. The obvious thing that I seemed to be missing was that on the Vera Settings - Net & Wi-fi page the Manually configure button had to be selected and then the Apply and Save button had to be pressed to get the Vera into Manual mode. It appears that if left in Automatically configure mode it automatically resets any changes to the /etc/config/network file back to default. I also turned the firewall off as well as the Wifi and SSID when I changed to manual mode so this may have had something to do with it but I think it was just that it had to be in manual configure mode not automatic.
Title: Re: VeraEdge Bridging Together
Post by: Klugheim on October 24, 2015, 02:00:39 am
It is working, i used tiaanv posting in that way:
1. You need to SSH into your vera (
either of them will suffice.  Only do this on ONE of them), using putty or something similar.  You'll also need your vera's root password, or temporarily enable remote support, and use those details.  there is enough info available on this... Google is your friend...
2.  You need to run a couple of commands:
uci set network.lan.ipaddr="192.168.81.2"  (this sets the LAN interface's IP address)
uci commit (this saves the changed settings)
cat /etc/config/network  (just to review that you changed the setting correctly....)

After this I go with Http to the box into networksettings and save it when I can see the correct IP
Title: Re: VeraEdge Bridging Together
Post by: litby on December 18, 2015, 11:45:09 am
Erroneous post please delete^-^
Title: Re: VeraEdge Bridging Together
Post by: BlackNTan on January 18, 2016, 03:22:44 pm
I tried this today, and my vera3 can see the edge, but not vice-versa.

Just so i'm clear -- once the edge's ip is set to 192.168.81.2 (Vera3 is 192.168.81.1) - the next step is to add UPnP device.  This is really odd though.  Adding via UPnP, I can't see the vera3 from the edge...

From Vera3, I can see the edge though via "add devices UPnP"???
Title: Re: VeraEdge Bridging Together
Post by: youataknow on May 04, 2016, 05:45:16 pm
I know this is an older post but it was somewhat helpful for me.  I have 2 VeraLites.  Lets call them Master and Slave.  Up until last week they were both on UI5 (never took the plunge to upgrade) and my Master controlled everything on the Slave just fine (as a UPNP device).  I upgraded both Units to UI7 and for the most part that wasn't bad.  It is quite different so after years of UI5 I'm having to rethink the way I had some of my stuff was setup.  My biggest part is the UPNP bridge.  It never connected back and the devices couldn't see each other.  I then followed the steps of changing the 192.168.81.1 IP on the Slave unit to 192.168.81.2.  I'm puzzled as to why Vera would use an IP on a port for UPNP broadcast packets that doesn't exist but that's another thread.  It does make sense as to why they both can't be 81.1.  So changing the IP on the Slave worked fine, and then reboot both.  My Slave can see my Master but not visa versa.  I then changed my Master from 81.1 to 81.3.  Just to see if there's something stuck on it thinking 81.1 is a gateway.  Reboot both units and still the same.  My slave can see my master but not the other way.  So for testing purposes I then told my slave to go ahead and add my master as a UPNP device and it worked fine.  It pulled in all the devices. 

So now I'm finally to where I'm looking for some guidance.  I'm ok with any of the options I think I can go with.

1:  I don't mind my Slave unit seeing my master but I'd really like some thoughts on how to flip this.   I prefer my master to be the one controlling the slave.

2:  If I can get my master to see the slave then I need to know how to delete a UPNP device.  I'm not seeing that as an option under devices.

Worst case scenario:

3:  My Master is connected to my Alarm system via Serial.  So my slave is now trying to open a serial port, which it doesn't have, to try and talk to the unit.  I'm not sure why it's doing that since it should see it through the master.  So my question is how can I remove some of the devices that were pulled in off the Master?  Is it even possible for you to specific what parts of a UPNP device you want?  If I can't get my master to see my slave I can have my slave watch for status changes and then react.  Which is OK just not the best way to handle this.
Title: Re: VeraEdge Bridging Together
Post by: gsegovia15 on June 02, 2016, 04:30:32 pm
I had a similar issue last week. It was easier for me since I upgraded to the veraplus. After I did that the veralite (slave) created a scene controller. So what I did was after making sure my device's worked on the veraplus.basically I disconnected the veralite and everything was still on the plus. I went ahead and rested the veralite to factory. Tried bridging the units together and the veraplus wouldnt pickup the device I had on the vera plus. So I called customer care. And we came to the conclusion that after I had rested the veralite I need to rest the z wave network on it too. Then tried bridging the vera's again. Now it's working.

Hope I explained it In a understanding way. Side note customer care did everything for me while I was on the phone with them. Took about 30min.
Title: Re: VeraEdge Bridging Together
Post by: bluezr1 on June 02, 2016, 10:28:57 pm
I had a similar issue last week. It was easier for me since I upgraded to the veraplus. After I did that the veralite (slave) created a scene controller. So what I did was after making sure my device's worked on the veraplus.basically I disconnected the veralite and everything was still on the plus. I went ahead and rested the veralite to factory. Tried bridging the units together and the veraplus wouldnt pickup the device I had on the vera plus. So I called customer care. And we came to the conclusion that after I had rested the veralite I need to rest the z wave network on it too. Then tried bridging the vera's again. Now it's working.

Hope I explained it In a understanding way. Side note customer care did everything for me while I was on the phone with them. Took about 30min.

So basically you had to set the IP/sub net addresses?

Sent from my VS985 4G using Tapatalk

Title: Re: VeraEdge Bridging Together
Post by: gsegovia15 on June 03, 2016, 09:33:25 am
I had a similar issue last week. It was easier for me since I upgraded to the veraplus. After I did that the veralite (slave) created a scene controller. So what I did was after making sure my device's worked on the veraplus.basically I disconnected the veralite and everything was still on the plus. I went ahead and rested the veralite to factory. Tried bridging the units together and the veraplus wouldnt pickup the device I had on the vera plus. So I called customer care. And we came to the conclusion that after I had rested the veralite I need to rest the z wave network on it too. Then tried bridging the vera's again. Now it's working.

Hope I explained it In a understanding way. Side note customer care did everything for me while I was on the phone with them. Took about 30min.

So basically you had to set the IP/sub net addresses?  thats the first thing i did. give both of the veras static ip addresses. assign the vera ip(192.168.1.xx) address thats out of dchp range. and then subnet(255.255.255.0) and gateway ip (at&t default ip)(192.168.1.254). your default might be different but its the most common.

Sent from my VS985 4G using Tapatalk