micro-ebusd with USR-ES1 --> VRC720/3 keeps rebooting. Ebusd with rpi works without problems.

[BePeMee]

Description

I have a heatpump installed with the following components:

• AroTherm 75/6 outside unit.
• UniTower 190/6E boiler
• VR71 controller
• VRC720/3 thermostat.

I bought a C6 adapter with USR-ES1 ethernet adapter that I want to use to connect the system to Home Assistant. I want to use micro-ebusd for that. I purchased the token and set the protocol to micro-ebusd:

Actual behavior

When I connect the adapter to the bus and ethernet and power it through a usb-c phone charger it connects to the bus and shows a number of measured values in Home assistant.
But at this point my VRC720 enters a boot loop. It boots, then after about 40 seconds it reboots again.

In order to test I have installed ebusd on a raspberry pi and connected the C6 adapter by USB cable to it.
This works without problems. The measured values are being read and the VRC720 does not reboot.

Expected behavior

I would expect that it would work with micro-ebusd the same as with the raspberry pi.

ebusd version

26.1

ebusd arguments

EBUSD_OPTS="--scanconfig --mqtthost=192.168.107.40 --mqtttopic=ebusd --mqttuser= --mqttpass= --mqttport=1883 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqttjson"

Operating system

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

CPU architecture

arm64

Dockerized

None

Hardware interface

Adapter Shield v5/C6/Stick via Ethernet

Related integration

MQTT Home Assistant via mqtt-hassio.cfg

Logs

These logs show nothing special, because with the C6 connected to the rpi there's no problem.
This is how the status page of micro-ebusd looks when connected.

[john30]

if it is related to micro-ebusd only, then please use https://github.com/john30/ebusd-esp32/issues/ instead.
anyway, you could check which message on the bus potentially leads to the boot when increasing the log level. then the log tab shows "sent MS cmd:" with the time and the content.
to what value did you set the poll interval?

[BePeMee]

Sorry about posting in the wrong section. I wasn't aware of the other one.

I was trying to find the "sent MS cmd:" on the log page, but there wasn't one. Then I noticed that while trying to reload the log the page was not responding. Looking at the adapter self I noticed that it was rebooting.
Then I saw that first the ebus adapter is rebooting, then right after that the VRC720 reboots as well.
This is what I found in the log:

I also attached the log as a file.

About the poll intervall. I tried several values between the default 60 and 120. That did not seem to make a difference.

ebuslog.json

[john30]

it looks as if there are lower level networking issues ("outbox enqueue"). can you temporarily switch to wifi (only) to see if that makes a difference?

[BePeMee]

I have tried connecting with Wifi. That showed the same behaviour.
But I found out that it is the QoS setting that makes it reboot or not. When set to 1 (which I had) both the adapter and VRC720 keep rebooting. I now have set QoS to 0 and it's been running stable since then.

I don't know why. I did some tests on my LAN.
"ip -s link show" on the server running mosquitto (docker) does not show any dropped packets.

And mosquitto doesn't seem to be very slow with QoS 1 either:

time mosquitto_pub -h 192.168.107.40 -p 1883 -u "<username>" -P "<password>" -t "test/latency" -m "ping" -q 1

real	0m0,007s
user	0m0,000s
sys	0m0,006s

But for it works with QoS set to 0.