Old WOLF R16 W5 with eBUS Adapter Shield V5

Hello dear forum,

perhaps someone here has experience with this (or similar) setup. I have an old WOLF R16 W5 controller with an eBUS. I have obtained an adapter called “eBUS Adapter Shield V5” for this purpose. This adapter is set up, connected to the network, and also receives signals from the heating controller.

In Home Assistant (Home Assistant OS 12.1 on an ESXi / vSphere as a VM), I have installed and configured the “eBUSd” add-on. It starts up and “communicates” with the adapter. The connection via MQTT also seems to be working. However, only the “values” of the adapter itself are being received.

As far as I can see, the add-on doesn’t know what to do with the “data” because it’s either looking for some configuration or can’t find it. Here’s the log of the add-on:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

ebusd --foreground --mqtthost=192.168.0.29 --mqttport=1883 --mqttuser=ANDERS --mqttpass=AUCHANDERS --scanconfig --mqttjson --latency=10 --pollinterval=5 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.0.82:9999 --log=all:notice
2024-04-09 09:12:16.760 [main notice] ebusd 23.2.p20230716 started with auto scan on device: 192.168.0.82:9999, enhanced
2024-04-09 09:12:17.509 [bus notice] device status: resetting
2024-04-09 09:12:17.509 [bus notice] bus started with own address 31/36
2024-04-09 09:12:17.510 [mqtt notice] connection established
2024-04-09 09:12:17.513 [bus notice] device status: reset, supports info
2024-04-09 09:12:17.516 [bus notice] device status: extra info: firmware 1.1[431e].1[431e], jumpers 0x0b
2024-04-09 09:12:17.547 [bus notice] signal acquired
2024-04-09 09:12:25.484 [bus notice] new master f1, master count 2
2024-04-09 09:12:25.484 [update notice] received unknown BC cmd: f1fe050308010548ff72ff3311
2024-04-09 09:12:26.945 [update notice] received unknown BC cmd: f1fe080008003d000d80010033
2024-04-09 09:12:27.691 [bus notice] scan f6: ;Kromschroeder; ;0121;0108
2024-04-09 09:12:27.691 [update notice] store f6 ident: done
2024-04-09 09:12:27.691 [update notice] sent scan-read scan.f6 QQ=31: Kromschroeder; ;0121;0108
2024-04-09 09:12:27.691 [bus notice] scan f6: ;Kromschroeder; ;0121;0108
2024-04-09 09:12:27.865 [main error] HTTP failure: receive error: 404 Not Found
2024-04-09 09:12:27.865 [main error] unable to load scan config f6: list files in kromschroeder ERR: element not found
2024-04-09 09:12:27.865 [main error] scan config f6: ERR: element not found
2024-04-09 09:12:35.525 [update notice] received unknown BC cmd: f1fe050308010540ff72ff3311
2024-04-09 09:12:36.987 [update notice] received unknown BC cmd: f1fe0800080027000d80010033
2024-04-09 09:12:45.517 [update notice] received unknown BC cmd: f1fe050308010540ff72ff3311
2024-04-09 09:12:46.978 [update notice] received unknown BC cmd: f1fe0800080027000d80010033
2024-04-09 09:12:55.509 [update notice] received unknown BC cmd: f1fe050308010540ff72ff3311
2024-04-09 09:12:56.970 [update notice] received unknown BC cmd: f1fe0800080027000d80010033
2024-04-09 09:13:05.501 [update notice] received unknown BC cmd: f1fe050308010540ff72ff3311
2024-04-09 09:13:06.962 [update notice] received unknown BC cmd: f1fe0800080027000d80010033
2024-04-09 09:13:15.494 [update notice] received unknown BC cmd: f1fe050308010540ff72ff3311
2024-04-09 09:13:16.955 [update notice] received unknown BC cmd: f1fe0800080027000d80010033
2024-04-09 09:13:25.539 [update notice] received unknown BC cmd: f1fe050308010540ff72ff3311
2024-04-09 09:13:27.000 [update notice] received unknown BC cmd: f1fe0800080027000d80010033
2024-04-09 09:13:35.532 [update notice] received unknown BC cmd: f1fe050308010540ff72ff3311
2024-04-09 09:13:36.993 [update notice] received unknown BC cmd: f1fe0800080027000d80010033
2024-04-09 09:13:45.524 [update notice] received unknown BC cmd: f1fe050308010540ff72ff3411
2024-04-09 09:13:46.986 [update notice] received unknown BC cmd: f1fe0800080027000d80010033

The first problem that I may have already solved (or perhaps solved incorrectly) was that the path /etc/ebusd/ was not created or didn’t exist. According to the “instructions,” this is where the configuration should be saved.

I just don’t want to upload any files to the server that might mess everything up. Maybe someone has a, perhaps only a “small,” tip for me on where the issue might be.