Referencing input_number entity as variable for leaf_temperature_offset does not work

[adroxTR]

Desired outcome:

I want an input field to be able to dynamically change leaf temperature offset as this parameter happens to change a lot in my setup. Is that simply not an intended feature? I'd love to contribute more, but I'm not a coder or developer. Therefore I thought maybe you would like some input from a frequent user of your chart card :)

EDIT: May as well leave another idea. What about adding charts for different growth stages? Especially interesting for the holy herbs out there. I'm sorry if this isnt the right place to put those comments!

[bogdan42k]

Referencing an input_number entity as variable for leaf_temperature_offset would be a neat feat!

[DelloxD1]

There is a workaround for this, you can just create a template sensor which uses your roomtemperature and calculates the leaf temp based on the input_number entity.

{{ states('sensor.median_temperature_growzelt') | float - states('input_number.flower_leaf_temp_offset') | float }}.

That newly created sensor can be used within the chart. At this point you don't need the "leaf_temp_offset" option of the chart anymore.

[SynthetikzZ]

There is a workaround for this, you can just create a template sensor which uses your roomtemperature and calculates the leaf temp based on the input_number entity.

{{ states('sensor.median_temperature_growzelt') | float - states('input_number.flower_leaf_temp_offset') | float }}.

That newly created sensor can be used within the chart. At this point you don't need the "leaf_temp_offset" option of the chart anymore.

Thank you sir searched for a way for exactly this.