Message chaining sends result multiple times

[Virsacer]

Description

Hi,
I tried to read 6 integers with message chaining:

root@f4f14eb0a162:/# ebusctl read -f Zaehler
225;123;15;383;27;700

root@f4f14eb0a162:/#

Actual behavior

But the logfile outputs the read 6 times and apparently ebusd sends it to MQTT multiple (probably 6 ?) times.
I saw the update-timstamp in FHEM jump again after a second or two.

Expected behavior

Well, after reading of all values is complete, it should print it to the log just once and send the data to MQTT just once.

ebusd version

24.1

ebusd arguments

EBUSD_ACCESSLEVEL: "*" EBUSD_ADDRESS: "ff" EBUSD_CONFIGPATH: "/ebusd" EBUSD_DEVICE: "ens:192.168.18.43:5001" EBUSD_ENABLEHEX: "" EBUSD_MQTTCLIENTID: "ebusd" EBUSD_MQTTHOST: "192.168.18.2" EBUSD_MQTTJSON: "" EBUSD_MQTTPORT: 1883 EBUSD_MQTTTOPIC: "ebusd"

Operating system

Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)

CPU architecture

x64

Dockerized

latest

Hardware interface

other

Related integration

MQTT generic, TCP (cmdline client like ebusctl or netcat)

Logs

2025-01-28 12:17:23.579 [update notice] sent read sc Zaehler QQ=ff: 225;125;15;383;27;700
2025-01-28 12:17:23.959 [update notice] sent read sc Zaehler QQ=ff: 225;125;15;383;27;700
2025-01-28 12:17:24.576 [update notice] sent read sc Zaehler QQ=ff: 225;125;15;383;27;700
2025-01-28 12:17:24.958 [update notice] sent read sc Zaehler QQ=ff: 225;125;15;383;27;700
2025-01-28 12:17:25.357 [update notice] sent read sc Zaehler QQ=ff: 225;125;15;383;27;700
2025-01-28 12:17:25.754 [update notice] sent read sc Zaehler QQ=ff: 225;125;15;383;27;700