Home Assistant Integration: MQTT get does not return value of otherwise consistent sensor

[pipingtravel]

Description

When using ebusd with a recoVAIR device, the SupplyFlowActual value behaves inconsistently depending on the access method:

ebusctl read -c recov SupplyFlowActual returns the correct value every time.

The value is updated regularly via poll-read (and appears in the ebusd log as expected).

The MQTT topic ebusd/recov/SupplyFlowActual is published regularly, and Home Assistant receives and updates the sensor value as expected.

However: When sending a message to ebusd/recov/SupplyFlowActual/get via MQTT (to actively trigger a read), ebusd does not return a value. There is no error message in the ebusd log—just an empty response.

Additional info

The regular polling and MQTT publishing work perfectly.

Only the active /get via MQTT does not trigger a value update.

The issue is not related to CSV errors or version mismatches—other values behave as expected.

Actual behavior

No value is published in response to the /get request, and there is no error or warning in the ebusd log.

Expected behavior

Publishing to ebusd/recov/SupplyFlowActual/get should trigger an immediate read and publish the current value to MQTT, just like ebusctl read does.

ebusd version

25.1

ebusd arguments

--scanconfig=full -d ens:192.168.178.115:9999 --mqtthost=192.168.178.46 --mqttport=1883 --mqttjson --mqttint=/config/mqtt-hassio.cfg

Operating system

other

CPU architecture

x64

Dockerized

latest

Hardware interface

Adapter Shield v5 via Ethernet

Related integration

MQTT Home Assistant via mqtt-hassio.cfg

Logs

2025-07-14 22:03:40.131 [update notice] sent poll-read recov SupplyFlowActual QQ=31: 145 2025-07-14 23:09:54.218 [mqtt notice] read recov SupplyFlowActual:

[john30]

can't reproduce this, please share the message definition. actually you'd have to use "ebusctl read -f -c recov SupplyFlowActual" in order to force refresh the value and not simply return from cache