Hi,
First of all, thank you for this great and clean PID controller integration – it's working perfectly in heating applications.
However, there’s a significant limitation when trying to use this integration for cooling scenarios, such as chilled ceiling panels or floor cooling systems.
Currently, the PID logic assumes heating behavior:
The lower the input sensor value compared to the setpoint, the higher the output.
In cooling applications, we typically want the opposite:
The higher the input value (e.g. supply water temperature) compared to the setpoint (e.g. dew point + 1 °C), the higher the output should be – to open the valve or activate cooling power.
Could you please add a reverse: true/false configuration option to the PID sensor?
reverse: false → classic heating PID logic (current behavior)
reverse: true → invert the output calculation, i.e. error = input - setpoint
This would allow users to seamlessly use this integration for both heating and cooling, without needing to:
swap the input and setpoint sensors (which makes the logic harder to follow), or
build inverse logic in Home Assistant automations (100 - PID_output)
Thank you again for your work, and we'd be happy to help test or review such an addition if needed!
Hi,
First of all, thank you for this great and clean PID controller integration – it's working perfectly in heating applications.
However, there’s a significant limitation when trying to use this integration for cooling scenarios, such as chilled ceiling panels or floor cooling systems.
Currently, the PID logic assumes heating behavior:
The lower the input sensor value compared to the setpoint, the higher the output.
In cooling applications, we typically want the opposite:
The higher the input value (e.g. supply water temperature) compared to the setpoint (e.g. dew point + 1 °C), the higher the output should be – to open the valve or activate cooling power.
Could you please add a reverse: true/false configuration option to the PID sensor?
reverse: false → classic heating PID logic (current behavior)
reverse: true → invert the output calculation, i.e. error = input - setpoint
This would allow users to seamlessly use this integration for both heating and cooling, without needing to:
swap the input and setpoint sensors (which makes the logic harder to follow), or
build inverse logic in Home Assistant automations (100 - PID_output)
Thank you again for your work, and we'd be happy to help test or review such an addition if needed!