john30
Each version after 23.3 breaks RAM reading with ebusctl
Description
Using ebusd 24.x or 25.x deliver wrong results if you try to read values from RAM. Usecase: reading values from a Weishaupt (TEM) solar unit that delivers no broadcast values on its own using NodeRed.
For example ebusd 23.3: ebusctl --port=8887 r -f -d fc -i '62596;2' ram => delivers correct upper storage temperature ebusd 24.x: high four digit value ebusd 25.x: wrong value too
Parameters:
/etc/defaults/ebusd_solar: EBUSD_S="--mqtttopic=eBus/Solar/%circuit%/%field%"
/etc/systemd/Sytem/ebusd_solar:
EnviromentFile=/etc/defaults/ebusd_solar ExecStart=/usr/bin/ebusd $EBUSD_S --device=ens:192.168.xxx.xxx:9999 --scanconfig=full --pidfile=/var/run/ebusd_solar.pid --port=8887 --httpport=8898 --mqtthost=192.168.xxx.xxx --mqttuser=xxxxxx --mqttpassword=xxxxxx
System: Debian Trixie (same behavior on Bookworm and/or with proxmox kernel)
Actual behavior
.
Expected behavior
Getting correct value(s) as like as with 23.3.
ebusd version
25.1
ebusd arguments
.
Operating system
Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)
CPU architecture
x64
Dockerized
None
Hardware interface
Adapter Shield v5/C6/Stick via WiFi
Related integration
other
Logs
.
