Firstly, excellent ui node!

This is an enhancement request, not a bug (actually a return of a previous feature from v2).

As per the title - I am currently using v2.02 with a plan to move to v3 (been testing on a node-red test instance) but one feature that I personally make use of is the ability to set separate upper and lower hysteresis values.

I use your heater controller node (one for each z-wave thermostatic radiator valve, 19 in total) to drive the call for heat from our boiler. Based on the output value of currentHeaterStatus which I store in persistent global variables (one per valve), a simple boolean logic node checks the global variables and if one or more are in state "on", the boiler is fired.

Because of thermal overshoot in the winter (the boiler alters the flow temperature based on an external "weather compensation" sensor - AKA a thermistor!) when the flow temp can be as high as 70c, I use an upper hysteresis value of between -0.2 and -1, dependent on the size of the room/radiator.....the bigger the radiator and smaller the room, the greater the thermal mass and larger the overshoot from the 70c water. I also use a lower hysteresis of between 0.5 and 1, again dependent on the room/radiator size. This for the most part has drastically reduced the thermal overshoot as the heater outputs "off" between 0.2 and 1 degree below the target temperature.

The new heater node has a single hysteresis value that is either added or subtracted to the target temperature to determine the on/off output state.

Would you consider reintroducing the separate upper/lower settings?

I appreciate you may have no motivation to do this as this is most likely a fringe case, but I thought I'd ask 😃