-
Notifications
You must be signed in to change notification settings - Fork 335
Description
hi,
i have a setup with a Vaillant heat pump, ebusd and HA which is working quite ok.
But recently i've stumbled over an error message in the HA logs that gets repeated every few minutes.
2025-12-14 10:07:49.479 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.ebusd_ctlv3_offsetoutsidetemp: -0.5 (range 0.0 - 100.0)
Reading a bit through the documentation, it seems that the MQTT discovery message sent by ebusd for the (writeable) number.ebusd_ctlv3_offsetoutsidetemp does not provide values for min and max ranges and thus, HA falls back to default values (in this case min: 0.0 and max: 100.0)
I tried to understand how to provide suitable values for min, max (and step), but failed to get anything working.
Neither could i figure out how to extend the csv file definitions (this is from my 15.ctlv3.csv )
type,circuit,level,name,comment,qq,zz,pbsb,id,*name,part,type,divisor/values,unit,comment
r,,,OffsetOutsideTemp,offset outside temperature,,,b524,020000002d00,value,,IGN:4,,,,value,,EXP,,K,
w,,,OffsetOutsideTemp,offset outside temperature,,,b524,020100002d00,value,,EXP,,K,
Nor could i really make sense how to properly trigger the right actions via changes in the /etc/ebusd/mqtt-hassio.cfg file. min, max and step are mentioned there (see sniplet below), but i guess this refers to variables passed via the csv definitions. (brute force setting of "min": -5 worked, of course. But then this is set for all writeable numbers, which is not ideal either).
# HA integration: optional variable with the minimum numeric value
min_number ?= ,
"min":%min
# HA integration: optional variable with the maximum numeric value
max_number ?= ,
"max":%max
# HA integration: optional variable with the numeric step value
step_number ?= ,
"step":%step
Thus, I'm either looking for advise how to properly update the csv entry for this (and other) variables to provide min, max and steps parameters or to how to catch the definition of OffsetOutsideTemp via adaptations in the mqtt-hassio.cfg and tweak it there.
Any insights appreciated!