Only subset of writable numbers via mqtt in HomeAssistant

[schnitzel001]

Description

I am using ebusd running on a debian LXC Container to read and write to my Wolf heatpump with this config:

message definition (just a subset):
r1;w,bm2,sollwertkorrektur_dhk,Sollwertkorrektur DHK,,35,5022,CCB527,sollwertkorrektur_dhk,,SIN,10,,Sollwertkorrektur DHK
r1;w,bm2,korrektur_aussentemperatur,Korrektur Aussentemperatur,,35,5022,CCA305,korrektur_aussentemperatur,,SIN,10,,Korrektur Aussentemperatur

active filters mqtt-hassio.cfg:
filter-seen = 2
filter-direction = r|u|w|^w (also tested with r|u|^w )

root@debian:~# ebusctl find -w
bm2 korrektur_aussentemperatur = no data stored
bm2 sollwertkorrektur_dhk = no data stored

root@debian:~# ebusctl info
version: ebusd 24.1.24.1
update check: version 25.1 available, device firmware 1[540f] available
device: 192.168.178.74, TCP, enhanced, firmware 1.1[5210].1[5210]
signal: acquired
symbol rate: 42
max symbol rate: 87
min arbitration micros: 6
max arbitration micros: 46
min symbol latency: 5
max symbol latency: 15
reconnects: 0
masters: 4
messages: 120
conditional: 0
poll: 117
update: 0
address 03: master #11
address 08: slave #11, scanned "MF=Wolf;ID= );SW=0180;HW=0000"
address 30: master #3
address 31: master #8, ebusd
address 35: slave #3
address 36: slave #8, ebusd
address 50: slave
address f1: master #10

Actual behavior

sollwertkorrektur_dhk is discovered in HomeAssistant as sensor.ebusd_bm2_sollwertkorrektur_dhk -> only readable -> not ok
korrektur_aussentemperatur is discovered in HomeAssistant as number.ebusd_bm2_korrektur_aussentemperatur -> read and write -> ok

Expected behavior

both variables should be discovered in HomeAssistant as writable numbers.

ebusd version

current source from git

ebusd arguments

EBUSD_OPTS="--configpath=/home/ebusd_config --mqtthost=192.168.178.20 --mqttport=1883 --mqttuser=mqtt-user --mqttpass=mqtt-pswd --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg"

Operating system

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

CPU architecture

x64

Dockerized

None

Hardware interface

Adapter Shield v5 via USB

Related integration

No response

Logs

None

[schnitzel001]

Hi, no ideas by anyone? I haven't found any explanation for this behavior yet.