There’s two ways you can do this.
Either, each network is independent, with it’s own mini computer running Velbus-tcp and one of the machines also running openHAB, HomeAssistant, NodeRed etc, connected to both Velbus networks.
Then it’s a matter of creating rules to link the events between the Velbus networks.
-
The advantage of this solution is that you can have 254 base addresses in use in both networks.
-
Disadvantage is that you must create the links outside of Velbuslink
The key question is "just how much interaction do you really need between the two locations?
Alternatively
You can make use of a great feature @jeroends put into #VelServ
Create your two Velbus networks.
On the primary network, install a computer running VelServ in server mode, which will allow you to connect Velbuslink, openHAB, HomeAssistant, NodeRed, Control4 and so on.
On the secondary Velbus network, connect a small SBC and only run VelServ, but in Client mode, directing it to the Server mode instance of VelServ on the primary network. (This does work across a reasonable public internet connection, you can make it secure by using a VPN or Zerotier bridge, instead of just opening a port on your primary router)
-
Advantage of this approach is that the two locations would present as one big Velbus installation to Velbuslink (and openHAB, HomeAssistant etc) and permit complete interaction between all modules natively.
-
Disadvantage is you are limited to 254 base addresses.
FYI, I have requested that the official Velbus Python / snap package also get a Client mode, but I doubt that will come any time soon.
Does this help you?