Replies: 4 comments 1 reply
-
|
hello can you post the config data |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Sorry, I just had time now. This is basically in the initial configuration; it can read the configuration files, it starts up, communicates with the adapter which in turn communicates with the boiler, and it receives 221 messages back. However, the CSV files are likely not compatible because it can't interpret the messages, so there's no data for EBUSD to return or save. I tried to update the CSV files because the log says it thinks there are newer ones, but I get the same result. I wouldn't think this boiler isn't supported; it's already about 6 years old. EBUSD_OPTS="--scanconfig --mqttport=1883 --mqtthost=192.168.1.### --mqttuser=### --mqttpass=### --device=enh:192.168.1.2:3335" |
Beta Was this translation helpful? Give feedback.
-
|
yes |
Beta Was this translation helpful? Give feedback.
-
|
root@debian:~# ebusctl info root@debian:~# ebusctl find |
Beta Was this translation helpful? Give feedback.
-
|
Check the branch of the config repo — some Vaillant models require the development branch instead of master, because new CSVs land there first. Force load the closest match — you can try renaming or symlinking the CSV for a similar SW/HW revision that’s confirmed to work (e.g., a bai.0010016100.inc file) to see if it decodes messages. Run ebusctl log on and capture raw telegrams — you can then post these to the ebusd-configuration repo so they can build or adjust the CSV for your exact firmware. Disable --scanconfig temporarily — sometimes it overrides your chosen CSV with a mismatched auto-selection. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I can draft a clear and polite email for you to send to the ebusd developer describing the issue and asking for guidance on the correct CSV files for your boiler.
Here’s a suggested version:
Subject: Help Needed: ebusd Not Receiving Data from Vaillant ecoTEC Pro VUW 236/5-3
Dear [Developer Name or ebusd Support Team],
I am reaching out because I am having trouble getting ebusd to correctly communicate with my Vaillant boiler.
System details:
Boiler: Vaillant ecoTEC Pro VUW 236/5-3 (H-INT II) R6
Detected via ebusd scan as: Vaillant;BAI00;0404;9602
ebusd version: [your ebusd version here]
MQTT connection works fine
Issue:
ebusd starts normally and detects the boiler as BAI00;0404;9602.
It loads the following configuration files:
bash
Másolás
Szerkesztés
vaillant/broadcast.csv
vaillant/general.csv
vaillant/scan.csv
vaillant/08.bai.csv (ID "bai00", SW0404, HW9602)
The log repeatedly shows:
pgsql
Másolás
Szerkesztés
scan completed X time(s), check again
update check: OK, vaillant/08.bai.csv: different version available
I do not receive any actual data updates from the boiler (no temperatures, no states).
I have tried removing all old CSV files and using the latest configuration from the official ebusd-configuration repository, but the result is the same.
Questions:
Which exact CSV file(s) do you recommend for this specific boiler model and firmware (BAI00;0404;9602)?
Is there a specific configuration or branch I should use to get proper data?
Could the "different version available" message be the reason I am not receiving values?
I would greatly appreciate any guidance to correctly configure ebusd for this boiler model.
Thank you for your support and for maintaining ebusd!
Best regards,
Lukács Sándor
Beta Was this translation helpful? Give feedback.
All reactions