send to fe: ERR: arbitration lost, retry

[gwaitsi]

Description

everything was working with my esp-ebus v6.3 board until some time ago, i am now only getting arbitration lost errors. started a few months ago. the admin access to the board is working fine.

I am using the ebusd plugin to home assistant.

Actual behavior

[09:12:15] INFO: eBUSd addon version 26.1.8
[09:12:15] INFO: mqtt-hassio.cfg exists in config folder and seed_mqtt_cfg is true — set seed_mqtt_cfg: false and add --mqttint=/config/mqtt-hassio.cfg and --mqttjson to commandline_options if you no longer need auto-seeding.
[09:12:15] INFO: ebusd --foreground --updatecheck=off --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=<redacted> --mqttpass=<redacted> --mqttint=/config/mqtt-hassio.cfg --mqttjson --device=192.168.30.28:3335 --pollinterval=30 --receivetimeout=100 --latency=200000 
2026-06-22 09:12:15.711 [device notice] transport opened
2026-06-22 09:12:15.716 [main notice] ebusd 26.1.26.1 started with broadcast scan on device: 192.168.30.28:3335, TCP
2026-06-22 09:12:16.148 [bus notice] bus started with own address 31/36
2026-06-22 09:12:16.148 [bus notice] signal acquired
2026-06-22 09:12:16.273 [mqtt notice] connection established
2026-06-22 09:12:26.149 [main notice] starting initial broadcast scan
2026-06-22 09:12:30.966 [bus error] send to fe: ERR: arbitration lost, retry
2026-06-22 09:12:31.323 [bus error] send to fe: ERR: arbitration lost, retry
2026-06-22 09:12:31.699 [bus error] send to fe: ERR: arbitration lost

Expected behavior

should provide the data from the device

ebusd version

current source from git

ebusd arguments

ebusd --foreground --updatecheck=off --mqtthost=core-mosquitto --mqttport=1883 --mqttuser= --mqttpass= --mqttint=/config/mqtt-hassio.cfg --mqttjson --device=192.168.30.28:3335 --pollinterval=30 --receivetimeout=100 --latency=200000

Operating system

Debian 13 (Trixie) / Ubuntu 24-25 / Raspberry Pi OS 13

CPU architecture

x64

Dockerized

None

Hardware interface

Adapter Shield v5/C6/Stick via USB

Related integration

No response

Logs

[09:12:15] INFO: eBUSd addon version 26.1.8
[09:12:15] INFO: mqtt-hassio.cfg exists in config folder and seed_mqtt_cfg is true — set seed_mqtt_cfg: false and add --mqttint=/config/mqtt-hassio.cfg and --mqttjson to commandline_options if you no longer need auto-seeding.
[09:12:15] INFO: ebusd --foreground --updatecheck=off --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=<redacted> --mqttpass=<redacted> --mqttint=/config/mqtt-hassio.cfg --mqttjson --device=192.168.30.28:3335 --pollinterval=30 --receivetimeout=100 --latency=200000 
2026-06-22 09:12:15.711 [device notice] transport opened
2026-06-22 09:12:15.716 [main notice] ebusd 26.1.26.1 started with broadcast scan on device: 192.168.30.28:3335, TCP
2026-06-22 09:12:16.148 [bus notice] bus started with own address 31/36
2026-06-22 09:12:16.148 [bus notice] signal acquired
2026-06-22 09:12:16.273 [mqtt notice] connection established
2026-06-22 09:12:26.149 [main notice] starting initial broadcast scan
2026-06-22 09:12:30.966 [bus error] send to fe: ERR: arbitration lost, retry
2026-06-22 09:12:31.323 [bus error] send to fe: ERR: arbitration lost, retry
2026-06-22 09:12:31.699 [bus error] send to fe: ERR: arbitration lost

[tomstruyf6]

I'm experiencing the same, started today without any changes to setup, hardware of software.

[gwaitsi]

@tomstruyf6 I had to add "enh:" in front of the IP if you are using latest HAOS and port 3335. then it was working again

[tomstruyf6]

@tomstruyf6 I had to add "enh:" in front of the IP if you are using latest HAOS and port 3335. then it was working again

yes, that worked.

Thanks!

[TheRealLenni]

I am experiencing the same issue but I am using the ESERA USB Adapter. Any ideas how to fix this issue here? Adding "enh:" in front of the device didn't help.

[gwaitsi]

@TheRealLenni looks like HAOS made some change to the UI a few months ago. as i remember, for my adapter you selected the enhanced mode and they auto appended the enh: as a preffix. but that is specific to Danial Kucera's adapter. suggest you look at your adapter details if there was any specific prefix or suffix added to the ip address