Problem with ebus binding for Vaillant VCR 470

It seems that there is an error in the ebus configuration for my Vaillant VCR 470. I don’t know which item causes the error but the error message tells, that there is a numeric value expected but the received value is zero followd by a colon:

2023-09-16 00:11:37.140 [ERROR] [.csdev.ebus.core.EBusEbusdController] - Error while parsing ebusd response: :ERR: invalid numeric argument
2023-09-16 00:11:37.140 [ERROR] [.csdev.ebus.core.EBusEbusdController] - error!
de.csdev.ebus.core.EBusDataException: Unable to send telegram FF 15 B5 09 03 0D 44 00 80 after 2 attempts ... [ERROR: TOO_MANY_ATTEMPS, DATA: FF 15 B5 09 03 0D 44 00 80]
	at de.csdev.ebus.core.EBusQueue.checkSendStatus( ~[?:?]
	at de.csdev.ebus.core.EBusEbusdController$ [?:?]
	at ~[?:?]
2023-09-16 00:11:37.141 [ERROR] [.csdev.ebus.core.EBusEbusdController] - Error Trace!
java.lang.NumberFormatException: For input string: "0:" under radix 16
	at java.lang.NumberFormatException.forInputString( ~[?:?]
	at java.lang.Integer.parseInt( ~[?:?]
	at java.lang.Integer.valueOf( ~[?:?]
	at de.csdev.ebus.utils.EBusUtils.toByteArray2( ~[?:?]
	at de.csdev.ebus.core.EBusEbusdController.parseLine( ~[?:?]
	at ~[?:?]

How can I find out which item causes the error?
Afterwards, how can I fix it?

Any hint is welcome.

The ebus protocol is very slow (2400 bits/sec) and even if you don’t activate the binding, a lot happens on the bus.
I also had errors like “Send queue is full”, 'Invalid numeric argument" and “Unable to send telegram”.
Changing the polling interval from 60s and 75s to 120s and 150s seems to fix the problem. The last two days I had no error at all.

Edit: every night I restart the Raspberry Pi; today the errors came back.