Vaillant Wärmepumpe liefert (praktisch) keine Daten

[zinray]

Hallo,
ich komme leider nicht weiter mit meinen Bemühungen Daten aus der Wärmepumpe auszulesen,
die in der Fachhandwerkerebene der Hydraulikstation (Code 17) zu sehen sind.
Meine Vaillantgeräte:
aroTHERM VWL 75/5 AS 230V S2 R1 (aussen)
Hydraulikstation 77/5 IS (innen)
Pufferspeicher VPS R 200/1 B
Warmwasserspeicher uniSTOR VIH RW 300/3 BR R1
VR 71
sensoCOMFORT VRC 720/2
Fernbedienung VR 92/2

ebus-Komponenten: (angezeigt von sensoCOMFORT mit Version)
Regler 05.14
Wärmepumpe 1 09.01
WP-Regelungsmodul 05.22
FM5 02.03
Fernbedienung 1 05.14

eBUS Adapter Shield v5 auf Raspberry Pi 3 Model B Rev 1.2
Build: [20250120]
ebusd device string: "ens:/dev/ttyAMA0" (number may vary)
WiFi station/client: , 100% (-29dBm)
WiFi access point: inactive
Chip ID: 54320484f1b0, [ESP32-C3, rev 4]
Hostname: ebus
Up time: 182316
Free heap: 48820 / 254564
ebusd connected: yes wechselt aber mit: yes (inactive)
eBUS signal: acquired
MQTT connected: yes (Mosquitto broker auf anderem Raspi: mqtt://192.168.1.22/WIFIebus)

Auf dem Raspberry wurde ebusd installiert und läuft:
piebus@raspi-ebus:~ $ systemctl status ebusd.service
● ebusd.service - ebusd, the daemon for communication with eBUS heating systems.
Loaded: loaded (/lib/systemd/system/ebusd.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-01-23 22:57:57 CET; 1h 18min ago
Process: 2895 ExecStart=/usr/bin/ebusd $EBUSD_OPTS (code=exited, status=0/SUCCESS)
Main PID: 2897 (ebusd)
Tasks: 4 (limit: 767)
CPU: 14.430s
CGroup: /system.slice/ebusd.service
└─2897 /usr/bin/ebusd --scanconfig -d ens:/dev/ttyAMA0 --latency=50 --configpath=https://ebus.github.io/

Jan 23 22:57:56 raspi-ebus systemd[1]: Starting ebusd.service - ebusd, the daemon for communication with eBUS heating systems....
Jan 23 22:57:57 raspi-ebus systemd[1]: Started ebusd.service - ebusd, the daemon for communication with eBUS heating systems....`

weiter:
piebus@raspi-ebus:~ $ ebusctl i
version: ebusd 24.1.24.1
update check: OK, device firmware v5 1[4c15] available
device: /dev/ttyAMA0, serial high speed, enhanced, firmware 1.1[5114].1[5114]
signal: acquired
symbol rate: 23
max symbol rate: 182
reconnects: 1
masters: 5
messages: 21
conditional: 0
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0901;HW=5103"
address 10: master #2
address 15: slave #2
address 26: slave, scanned "MF=Vaillant;ID=VR_71;SW=0203;HW=5904"
address 30: master #3
address 31: master #8, ebusd
address 35: slave #3, scanned "MF=Vaillant;ID=VR_92;SW=0514;HW=1204"
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZ00;SW=0522;HW=5103"

weiter:
piebus@raspi-ebus:~ $ ebusctl f
Broadcast ControlCmd = no data stored
Broadcast Datetime = no data stored
Broadcast Error = no data stored
Broadcast Id = no data stored
Broadcast IdAnswer = no data stored
Broadcast Netloss = no data stored
Broadcast Netresetcfg = no data stored
Broadcast Netresetstate = no data stored
Broadcast RcOperation = no data stored
Broadcast RcTarget = no data stored
Broadcast Signoflife = no data stored
Memory Eeprom = no data stored
Memory Ram = no data stored
scan.08 = Vaillant;HMU00;0901;5103
scan.26 = Vaillant;VR_71;0203;5904
scan.35 = Vaillant;VR_92;0514;1204
scan.76 = Vaillant;VWZ00;0522;5103

Im MQTT-Explorer erscheinen nur diese Daten:
WIFIebus
running = true
uptime = 192368
temp = 54
rssi = -27

/var/log/ebusd.log zeigt:
2025-01-24 00:25:58.963 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2025-01-24 00:25:59.157 [main notice] starting initial broadcast scan
2025-01-24 00:25:59.227 [update notice] received unknown MS cmd: 1008b51009000000ffffff070000 / 0101
2025-01-24 00:25:59.490 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101
2025-01-24 00:25:59.779 [update notice] received unknown MS cmd: 1026b5230f05ff0000000000ffff000000000000 / 0101
2025-01-24 00:25:59.827 [bus error] send to fe: ERR: arbitration lost, retry
2025-01-24 00:25:59.960 [update notice] received unknown MS cmd: 7108b5110107 / 0a000000e0002d00000000
2025-01-24 00:26:00.075 [update notice] received unknown MS cmd: 1026b5230402000000 / 02019c
2025-01-24 00:26:00.475 [bus error] send to fe: ERR: arbitration lost, retry
2025-01-24 00:26:01.045 [bus error] send to fe: ERR: arbitration lost
2025-01-24 00:26:01.046 [main error] initial scan failed: ERR: arbitration lost
2025-01-24 00:26:02.340 [update notice] received unknown MS cmd: 7108b5120e112f023002c701f4010f00000600 / 020000
(... [update notice] received unknown MS cmd: ...)
2025-01-24 00:26:10.570 [update notice] received unknown MS cmd: 7108b5120e112f023002c801f4010f00000600 / 020000
2025-01-24 00:26:11.046 [main notice] starting initial broadcast scan
2025-01-24 00:26:11.584 [bus error] send to fe: ERR: arbitration lost, retry
2025-01-24 00:26:12.155 [bus error] send to fe: ERR: arbitration lost, retry
2025-01-24 00:26:12.726 [bus error] send to fe: ERR: arbitration lost
2025-01-24 00:26:12.726 [main error] initial scan failed: ERR: arbitration lost
2025-01-24 00:26:13.517 [update notice] received unknown MS cmd: 7108b5110107 / 0a000000e0002d00000000
...

Test mit --configpath=/home/piebus/ebusd-config/de/
mit den Dateien aus https://github.com/john30/ebusd-configuration/tree/master/ebusd-2.1.x/de/
mit unterschiedliche Latenzen, anderem Kabel, aber "arbitration lost, retry" bleibt.

BTW: Auf dem homeassistant kommen natürlich nur die Werte an, die der MQTT-Explorer liefert.
BTW2: Ich habe auch das homeassistant-Addon (https://github.com/LukasGrebe/ha-addons/) ausprobiert,
leider mit dem gleichen Ergebnis.

Jetzt weiß ich nicht mehr weiter und hoffe auf Hinweise.

Vielen Dank
RainerS

[zinray]

Ich antworte mir selbst mit ein paar Korrekturen:

1. non-enhanced mode:
   Adapter: eBUS: plain via RPI
   ebusd device string: "/dev/ttyAMA0" (number may vary)
   Raspberry: /etc/default/ebusd (user: piebus@raspi-ebus)
   EBUSD_OPTS="--scanconfig -d /dev/ttyAMA0 --latency=50 --configpath=/home/piebus/ebusd-configuration/ebusd-2.1.x/de "--accesslevel=*" --mqtthost=192.168.1.22 --mqttport=1883 --mqtttopic=ebusd
2. local config, accesslevel, mqtthost, mqttport, mqtttopic
3. "vaillant/76.vwz.csv" von ebus.github.io/de nach ebusd-configuration/ebusd-2.1.x/de kopiert

-> kein "arbitration lost, retry"

piebus@raspi-ebus:~ $ ebusctpiebus@raspi-ebus:~ $ ebusctl i
version: ebusd 24.1.24.1
update check: OK, broadcast.csv: different version available, memory.csv: different version available, vaillant/08.hmu.csv: different version available, vaillant/15.ctlv2.csv: different version available, vaillant/broadcast.csv: different version available, vaillant/errors.inc: different version available, vaillant/general.csv: different version available, vaillant/hcmode.inc: different version available
device: /dev/ttyAMA0, serial
access: *
signal: acquired
symbol rate: 99
max symbol rate: 157
min arbitration micros: 3
max arbitration micros: 13
min symbol latency: 25
max symbol latency: 42
scan: finished
reconnects: 0
masters: 5
messages: 522
conditional: 0
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0901;HW=5103", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=CTLV2;SW=0514;HW=1104", loaded "vaillant/15.ctlv2.csv"
address 26: slave, scanned "MF=Vaillant;ID=VR_71;SW=0203;HW=5904", loaded "vaillant/26.vr_71.csv"
address 30: master #3
address 31: master #8, ebusd
address 35: slave #3, scanned "MF=Vaillant;ID=VR_92;SW=0514;HW=1204"
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZ00;SW=0522;HW=5103", loaded "vaillant/76.vwz.csv"
l i    liefert:
version: ebusd 24.1.24.1
update check: OK, broadcast.csv: different version available, memory.csv: different version available, vaillant/08.hmu.csv: different version available, vaillant/15.ctlv2.csv: different version available, vaillant/broadcast.csv: different version available, vaillant/errors.inc: different version available, vaillant/general.csv: different version available, vaillant/hcmode.inc: different version available
device: /dev/ttyAMA0, serial
access: *
signal: acquired
symbol rate: 99
max symbol rate: 157
min arbitration micros: 3
max arbitration micros: 13
min symbol latency: 25
max symbol latency: 42
scan: finished
reconnects: 0
masters: 5
messages: 522
conditional: 0
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0901;HW=5103", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=CTLV2;SW=0514;HW=1104", loaded "vaillant/15.ctlv2.csv"
address 26: slave, scanned "MF=Vaillant;ID=VR_71;SW=0203;HW=5904", loaded "vaillant/26.vr_71.csv"
address 30: master #3
address 31: master #8, ebusd
address 35: slave #3, scanned "MF=Vaillant;ID=VR_92;SW=0514;HW=1204"
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZ00;SW=0522;HW=5103", loaded "vaillant/76.vwz.csv"

und

MQTT Explorer zeigt

ebusd
 global
	running = true
	signal = true
	scan = finished
	updatecheck = OK, broadcast.csv: different version available, memory.csv: different version available, vaillant/08.hmu.csv: different version available, vaillant/15.ctlv2.csv: different version available, vaillant/broadcast.csv: different version available, vaillant/errors.inc: different version available, vaillant/general.csv: different version available, vaillant/hcmode.inc: different version available
	uptime = 928
	version = ebusd 24.1.24.1
 hmu
	SetMode = auto;0.0;-;-;1;1;1;0;0;0
	Status01 = 51.0;50.5;-;-;-;off
	State = 0;456;224;0
	StatusCirPump = off
 vr_71
	SensorData1 = 44.19;33.00;-;-;-;-;-;50 3d
	SensorData2 = -;-;-;-;0.00;8.00;80 57 05
	SetActorState = -;off;off;off;off;off;-;-;off;off;off;off;00 00
	Mc1FlowTempDesired = off;0.0;on;-100
 broadcast
	vdatetime = 22:51:44;02.02.2025
	outsidetemp = -0.113
 scan.08
	= Vaillant;HMU00;0901;5103
	id = 21;23;01;0010021111;0001;005125;N6
 scan.15
	= Vaillant;CTLV2;0514;1104
	id = 21;22;36;0020260914;0953;032805;N5
 scan.26
	= Vaillant;VR_71;0203;5904
	id = 21;22;48;0020184846;0082;033925;N2
	scan.35
	= Vaillant;VR_92;0514;1204
	id = 21;22;41;0020260923;0953;008564;N3
 scan.76
	= Vaillant;VWZ00;0522;5103
	id = 21;22;48;0010023495;1610;008040;N5

Soweit, so gut...
RainerS