eBUS Adapter Shield C6 and Protherm Medveď Condens 25 KKS

[whitoSB]

Hello everyone, I have problem with Protherm Medveď Condens 25 KKS (Vaillant Group) and eBUS Adapter Shield C6. When I connect the adapter to the boiler, the green diode flashes quickly (communication works). But ebusd in home assistant does not see the boiler during automatic configuration.
log from ebusd:

ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=aerohpeeDahyoom5kieGh1yi7Ja2zaelahyoh0faef0phabaefienaiNok5phaiz --scanconfig --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.68.71:9999 --log=all:notice
2025-08-07 15:16:30.846 [device notice] transport opened
2025-08-07 15:16:30.873 [main notice] ebusd 25.1.p20250414 started with broadcast scan on device: 192.168.68.71:9999, TCP, enhanced
2025-08-07 15:16:31.459 [bus notice] bus started with own address 31/36
2025-08-07 15:16:31.459 [device notice] reset, supports info
2025-08-07 15:16:31.459 [bus notice] signal acquired
2025-08-07 15:16:31.461 [device notice] extra info: firmware 1.1[560f].1[560f], jumpers 0x0b
2025-08-07 15:16:31.686 [mqtt notice] connection established
2025-08-07 15:16:41.460 [main notice] starting initial broadcast scan
2025-08-07 15:16:41.578 [update notice] sent write Broadcast Queryexistence QQ=31:
2025-08-07 15:16:48.743 [bus notice] new master 00, master count 2
2025-08-07 15:16:51.774 [main error] scan config 05: ERR: read timeout
2025-08-07 15:17:53.969 [main error] scan config 05: ERR: read timeout
2025-08-07 15:17:55.970 [main notice] scan completed 1 time(s), check again
2025-08-07 15:18:36.119 [device notice] extra info: ID 7c2c6761e5bc180100
2025-08-07 15:18:36.220 [main notice] update check: revision 25.1 available, device firmware v5-c6 1[560f] up to date
2025-08-07 15:19:06.385 [main error] scan config 05: ERR: read timeout
2025-08-07 15:19:08.386 [main notice] scan completed 2 time(s), check again
2025-08-07 15:20:18.578 [main error] scan config 05: ERR: read timeout
2025-08-07 15:20:20.579 [main notice] scan completed 3 time(s), check again

Is it necessary to have an ebus thermostat connected to the boiler? I don't have an ebus thermostat, only the Adapter Shield C6.

thanks for the responses
sorry for my eng.

[Brosius18]

Go to the ebusd-configuration repository
Look for the vaillant/ or protherm/ subfolder — many Protherm Condens models share configs with Vaillant ecoTEC or similar.
Download all relevant *.csv files (e.g. bai.csv, bas.csv, hc1.csv, etc.) and put them into /etc/ebusd/

[whitoSB]

The adapter does not see any device.
Are *.csv files needed for the adapter to detect the device?

[whitoSB]

Protherm MEDVEĎ Condens 25 KKS 0010013665, can i use similar number for 0010013665? 0010013665 is not supported
the similar boiler is Vaillant ecoVIT pro VKK 256/5

/ # ebusctl info
version: ebusd 25.1.p20250414
update check: revision 25.1 available, device firmware v5-c6 1[560f] available
device: 192.168.68.86:9999, TCP, enhanced, firmware 1.1[5b02].1[5b02]
signal: acquired
symbol rate: 24
max symbol rate: 30
min arbitration micros: 14
max arbitration micros: 16
min symbol latency: 5
max symbol latency: 34
scan: finished
reconnects: 0
masters: 2
messages: 18
conditional: 0
poll: 0
update: 10
address 00: master #1
address 31: master #8, ebusd
address 36: slave #8, ebusd

2025-11-15 14:20:20.569 <0008b5090228028e
2025-11-15 14:20:21.331 <0008b5090228028e
2025-11-15 14:20:33.390 >310507040031
2025-11-15 14:21:22.238 <0008b5090228028e
2025-11-15 14:21:22.996 <0008b5090228028e
2025-11-15 14:21:45.559 >310507040031
2025-11-15 14:22:23.907 <0008b5090228028e
2025-11-15 14:22:24.662 <0008b5090228028e
2025-11-15 14:22:57.769 >310507040031
2025-11-15 14:23:25.582 <0008b5090228028e
2025-11-15 14:23:26.340 <0008b5090228028e
2025-11-15 14:24:09.962 >310507040031
2025-11-15 14:24:27.221 <0008b5090228028e
2025-11-15 14:24:27.979 <0008b5090228028e

[jjfoid]

Try to play with latency. For me, the parameter below works fine
--latency=100
Try this first. Because I don't see any other eBus device in your ebusctl output. For example, my output has the following (I have Protherm Puma Condens):

address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=5016;HW=1303", loaded "vaillant/bai.308523.inc", "vaillant/08.bai.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd

and this difference looks like your adapter doesn't see your boiler device on the bus.

Also, I don't see --configpath in your command line, so https://ebus.github.io/ is used by default. Is it accessible from the ebusd host?

You can try local configuration files instead. For this, you need to clone ebus.github.io repo:

cd /etc/ebusd
git clone https://github.com/eBUS/ebus.github.io.git config

and then specify the full path to the next/en folder inside it, for example
--configpath /etc/ebusd/config/next/en
Not sure this will help from the start, but you definitely need to move from online to local CSV files to be able to customize them in case you need to add your device ID (0010013665) to be handled by 08.bai. You simply need to add your ID to the 08.bai.csv file (I assume to the line with load,bai.308523.inc , but you can play with other lines if you need).
You mentioned that Vaillant ecoVIT pro VKK 256/5 is similar to your Ptotherm. This Vaillant has product number 0010019520, and I don't see this number in CSV files as well, so not sure which config should work best for you. I suggest to start with bai.308523.inc anyway.

[whitoSB]

eBUSd:

seed_mqtt_cfg: true
commandline_options:

• --mqttjson
• --device=ens:192.168.68.**:****
• --scanconfig=08
• --accesslevel=*
• --configpath=/config/ebusd-config/de
• --pollinterval=2

[mqtt notice] connection established
2026-10-01 20:33:38.838 [main notice] starting initial scan for 08
2026-10-01 20:33:39.020 [bus notice] new master 03, master count 2
2026-10-01 20:33:39.020 [bus notice] scan 08: ;Vaillant;BAI00;0201;9002
2026-10-01 20:33:39.020 [update notice] store 08 ident: done
2026-10-01 20:33:39.021 [update notice] sent scan-read scan.08 QQ=31: Vaillant;BAI00;0201;9002
2026-10-01 20:33:39.021 [bus notice] scan 08: ;Vaillant;BAI00;0201;9002
2026-10-01 20:33:39.026 [main notice] read common config file vaillant/scan.csv
2026-10-01 20:33:39.026 [main notice] read common config file vaillant/broadcast.csv
2026-10-01 20:33:39.027 [main notice] read common config file vaillant/general.csv
2026-10-01 20:33:39.030 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0201, HW9002
2026-10-01 20:33:39.305 [update notice] sent scan-read Scan.08 Id QQ=31:
2026-10-01 20:33:39.388 [bus notice] new master 00, master count 3
2026-10-01 20:33:40.026 [update notice] sent scan-read Scan.08 Id QQ=31:
2026-10-01 20:33:40.251 [update notice] sent scan-read Scan.08 Id QQ=31:
2026-10-01 20:33:40.435 [update notice] sent scan-read Scan.08 Id QQ=31: 21;22;38;0010013665;3100;005362;N1
2026-10-01 20:33:40.456 [main notice] found messages: 229 (3 conditional on 35 conditions, 0 poll, 10 update)
2026-10-01 20:33:41.119 [update notice] sent scan-read Scan.08 Id QQ=31: 21;22;38;0010013665;3100;005362;N1
2026-10-01 20:33:41.286 [update notice] sent scan-read Scan.08 Id QQ=31: 21;22;38;0010013665;3100;005362;N1
2026-10-01 20:33:41.455 [update notice] sent scan-read Scan.08 Id QQ=31: 21;22;38;0010013665;3100;005362;N1
2026-10-01 20:33:41.616 [update notice] sent scan-read Scan.08 Id QQ=31: 21;22;38;0010013665;3100;005362;N1
2026-10-01 20:33:41.616 [bus notice] scan 08: ;21;22;38;0010013665;3100;005362;N1
2026-10-01 20:33:41.616 [main notice] initial scan result: 08;Vaillant;BAI00;0201;9002;21;22;38;0010013665;3100;005362;N1

de.zip