Multiple zone, multiple controller deployment

[SailingGreg]

The deployment is a simple multiple zone with a Vaillant ecotech plus boiler, VR66 dual zone controller and two wired VRT350s for the individual zones. I’ve had some issues as the first VRT are not appearing on expected address of 15, but 35 and 75 and there appears to be no way of mapping these

Three questions related to this:

• I’ve addressed the first VRT350 appearing on address 35 and not 15 by downloading the relevant confirmation file and mapping via a local configuration (symlinked). Is there a way of mapping the addresses so that I could use the default of repo of https://ebus.github.io?

• How do you typically address multiple devices as symlinking 35.350.csv to 75.350.csv leads to duplicate names errors on loading if I use the latest configuration files. This means that I can't get a definition to load for the secondary controller.

• I’ve symlinked the V65 definition file to VR66 to get this going buy is there there a V66 definition or one being produced?

The existing ebusctl info output

ebusctl info

version: ebusd 25.1.25.1
device: 192.168.100.144:9999, TCP, enhanced, firmware 1.1[560f].1[560f]
signal: acquired
symbol rate: 23
max symbol rate: 134
min arbitration micros: 0
max arbitration micros: 2
min symbol latency: 5
max symbol latency: 14
scan: finished
reconnects: 0
masters: 5
messages: 365
conditional: 0
poll: 0
update: 7
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0608;HW=5502", loaded "vaillant/bai.0010011701.inc" ([id_hw=5502]), "vaillant/08.bai.csv"
address 10: master #2
address 30: master #3
address 31: master #8, ebusd
address 35: slave #3, scanned "MF=Vaillant;ID=35000;SW=0108;HW=7102", loaded "vaillant/35.350.csv"
address 36: slave #8, ebusd
address 64: slave, scanned "MF=Vaillant;ID=V6600;SW=0107;HW=7602", loaded "vaillant/64.v66.csv"
address 70: master #4
address 75: slave #4, scanned "MF=Vaillant;ID=35000;SW=0109;HW=7102"

[MzLiv]

Sorry to hijack but I have an almost identical system with 1 VR66 and 2 VRT350s. I am one step behind though. How did you link the config files?

version: ebusd 25.1. p20250414 update check: version 26.1 available, device firmw are v5 1[6216] available device: 192.168.0.110: 9999, TCP, enhanced, firmware 1.1[ 5c07].1[5c07]
signal: acquired
symbol rate: 22
max symbol rate: 133 min arbitration micros: 3 max arbitration micros: 724 min s ymbol latency: 1 max symbol latency: 59
scan: finished
reconnects: 1
masters: 5
messages: 242
condit ional: 3
poll: 71
update: 16
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant ;ID= BAI 00;SW=1104;HW= 7603 ", loaded "vaillant/bai. 00100438 97.inc" ([id_hw=7603]), " vaillant /08. bai.csv"
address 10: master #2
address 30: master #3
address 31: master #8, ebusd
address 35: slave #3, scanned "MF-Vaillant; ID=3500 0;SW= 0114; HW=7102 "
address 36: slave #8, ebusd
address 64: slave, scanned "MF=Vaillant; ID =V6600; W=0203; HW=7602
address 70: master #4 address 75: slave #4, scanned "ME-Vaillant ; ID=3500 0;SW=0114; HW=7102 "