System Setup:
- eBUSd version: 26.1
- Device 1: Vaillant Boiler (BAI00) at address 08
- Device 2: Vaillant Solar/Extension Module (EMM00) at address 15
The Problem:
I am experiencing significant issues using the new TypeSpec (.tsp) configurations in a multi-device Vaillant setup. There are naming conflicts between the base boiler definitions and the extension modules, which prevents eBUSd from loading the complete message set.
-
Naming Conflicts (Duplicate Name):
When eBUSd identifies the extension module (EMM), it attempts to load vaillant/bai.emm.inc (or the .tsp equivalent). This fails because several message names (like Date, Time, WaterPressure, and various EnergySum / FuelSum counters) are already defined in the main BAI configuration.
As a result, the solar-specific data points are not accessible because the loading process aborts.
-
Hardware Recognition / Scan Prefix:
The automatic scan fails to map address 15 (EMM00) to the correct configuration because the system expects a .csv file with the prefix 15., but the repository currently only provides .tsp files which are not automatically picked up as entry points during the scan.
Logs:
Plaintext
[main error] error loading "vaillant/bai.emm.inc" for "08": ERR: duplicate name vaillant/bai.emm.inc:10: ERR: duplicate name, invalid name
[main error] unable to load scan config 15: no file from vaillant with prefix 15 found
[update error] unable to parse poll-read bai ... ERR: invalid position
System Setup:
The Problem:
I am experiencing significant issues using the new TypeSpec (.tsp) configurations in a multi-device Vaillant setup. There are naming conflicts between the base boiler definitions and the extension modules, which prevents eBUSd from loading the complete message set.
Naming Conflicts (Duplicate Name):
When eBUSd identifies the extension module (EMM), it attempts to load vaillant/bai.emm.inc (or the .tsp equivalent). This fails because several message names (like Date, Time, WaterPressure, and various EnergySum / FuelSum counters) are already defined in the main BAI configuration.
As a result, the solar-specific data points are not accessible because the loading process aborts.
Hardware Recognition / Scan Prefix:
The automatic scan fails to map address 15 (EMM00) to the correct configuration because the system expects a .csv file with the prefix 15., but the repository currently only provides .tsp files which are not automatically picked up as entry points during the scan.
Logs:
Plaintext
[main error] error loading "vaillant/bai.emm.inc" for "08": ERR: duplicate name vaillant/bai.emm.inc:10: ERR: duplicate name, invalid name
[main error] unable to load scan config 15: no file from vaillant with prefix 15 found
[update error] unable to parse poll-read bai ... ERR: invalid position