EBUS Adapter not communicate with the heater

[jacekk233]

Hello
I have a heater Vaillant Ecotec Plus VC PL 306/3-5
I've mounted EBUS Adapter 2.0, checked it by the Measuring Plan from ebusd.eu, and all values were as it should be.
My Wemos was flashed with firmware wemos d1 mini (eBUS adapter 3) and connected to adapter.
Adapter was connected to the heater with 1m cable

When I connected to Wemos by HTTP and configured according to procedure i still can see that:
ebusd connected: no
eBUS signal: no signal

Could someone help me with that ?
What I should check?

[jacekk233]

In relation to last one, so far there are problems with communication between the heater and my ebus adapter.
My heateris Vaillant Ecotec Plus VC PL 306/3-5. I use EBUS Adapter 2.0, WEMOS with eBUS Adapter 3; RPi with Raspbian 10

After connection there is like that:

pi@raspberrypi:~ $ ebusd -f -scanconfig -d 192.168.2.138:9999 -l /var/log/ebusd.log 2022-10-09 17:24:38.195 [bus notice] signal acquired 2022-10-09 17:24:40.024 [bus error] signal lost pi@raspberrypi:~ $ ebusd -f -scanconfig -d 192.168.2.138:9999 -l /var/log/ebusd.log 2022-10-09 17:24:38.195 [bus notice] signal acquired 2022-10-09 17:24:40.024 [bus error] signal lost

pi@raspberrypi:~ $ ebusd -f -scanconfig -d 192.168.2.138:9999 -l /var/log/ebusd.log 2022-10-09 18:27:59.849 [main notice] ebusd 3.0.595c7c0 started 2022-10-09 18:27:59.868 [bus notice] bus started with own address 31/36 2022-10-09 18:30:10.135 [main notice] update check: version 22.4 available, broadcast.csv: different version available, memory.csv: different version available pi@raspberrypi:~ $ ebusd -f -scanconfig -d 192.168.2.138:9999 -l /var/log/ebusd.log 2022-10-09 18:27:59.849 [main notice] ebusd 3.0.595c7c0 started 2022-10-09 18:27:59.868 [bus notice] bus started with own address 31/36 2022-10-09 18:30:10.135 [main notice] update check: version 22.4 available, broadcast.csv: different version available, memory.csv: different version available

or

pi@raspberrypi:~ $ ebusd -f -scanconfig -d 192.168.2.138:9999 -l /var/log/ebusd.log 2022-10-09 18:27:59.849 [main notice] ebusd 3.0.595c7c0 started 2022-10-09 18:27:59.868 [bus notice] bus started with own address 31/36 2022-10-09 18:30:10.135 [main notice] update check: version 22.4 available, broadcast.csv: different version available, memory.csv: different version available pi@raspberrypi:~ $ ebusd -f -scanconfig -d 192.168.2.138:9999 -l /var/log/ebusd.log 2022-10-09 18:27:59.849 [main notice] ebusd 3.0.595c7c0 started 2022-10-09 18:27:59.868 [bus notice] bus started with own address 31/36 2022-10-09 18:30:10.135 [main notice] update check: version 22.4 available, broadcast.csv: different version available, memory.csv: different version available (...)

pi@raspberrypi:~ $ ebusctl i version: ebusd 3.0.595c7c0 update check: version 22.4 available, broadcast.csv: different version available, memory.csv: different version available signal: no signal reconnects: 0 masters: 1 messages: 11 conditional: 0 poll: 0 update: 4 address 31: master #8, ebusd address 36: slave #8, ebusd pi@raspberrypi:~ $ ebusd -f -scanconfig -d 192.168.2.138:9999 2022-10-09 17:24:38.139 [main notice] ebusd 3.0.595c7c0 started 2022-10-09 17:24:38.190 [bus notice] bus started with own address 31/36 2022-10-09 17:24:38.195 [bus notice] signal acquired 2022-10-09 17:24:40.024 [bus error] signal lost 2022-10-09 17:26:48.357 [main notice] update check: version 22.4 available, broadcast.csv: different version available, memory.csv: different version available
When I connected to Wemos by HTTP and configured according to procedure i still can see that:
ebusd connected: yes (inactive)
eBUS signal: no signal

I can't figure out the solution om my problem. Could someone help me with that ?
Thanks in advance

UPDATE
I've upgrated ebusd to ebusd 22.4, but configuration files are still ebusd-2.1.x like it was with ebusd 3.0.

pi@raspberrypi:~ $ ebusd --scanconfig -f -d 192.168.2.138:9999 --loglevel=debug --logfile=/var/log/ebusd.log 2022-10-10 10:13:44.281 [main notice] ebusd 22.4.v22.4 started with auto scan on device 192.168.2.138:9999 2022-10-10 10:13:44.281 [main info] loading configuration files from https://cfg.ebusd.eu/ 2022-10-10 10:13:44.572 [main info] reading templates / 2022-10-10 10:13:44.866 [main info] read templates in / 2022-10-10 10:13:44.866 [main info] reading file memory.csv 2022-10-10 10:13:45.155 [main info] successfully read file memory.csv 2022-10-10 10:13:45.155 [main info] reading file broadcast.csv 2022-10-10 10:13:45.457 [main info] successfully read file broadcast.csv 2022-10-10 10:13:45.459 [main info] read config files, got 11 messages 2022-10-10 10:13:45.489 [bus notice] bus started with own address 31/36 2022-10-10 10:13:45.490 [main info] registering data handlers 2022-10-10 10:13:45.491 [main info] registered data handlers

But info that "signal acquired" and next " signal lost" i can see very rarely like that:
pi@raspberrypi:~ $ ebusd --scanconfig -f -d 192.168.2.138:9999 -l /var/log/ebusd.log --configpath=/etc/ebusd 2022-10-10 12:01:47.624 [main notice] ebusd 22.4.v22.4 started with auto scan on device 192.168.2.138:9999 2022-10-10 12:01:47.668 [bus notice] bus started with own address 31/36 2022-10-10 12:03:58.098 [main notice] update check: OK, memory.csv: different version available 2022-10-10 12:07:51.578 [bus notice] signal acquired 2022-10-10 12:07:53.038 [bus error] signal lost

and only if i send in terminal: "sudo service ebusd restart" but only 1-2 seconds.

In EBUS ADAPTER 2.x there isn't any potentiometer to adjust to the heater like it was in EBUS-Adapter 1.6.
Can someone point me a right direction?