Description of configuration in README.md appears to be outdated

[Yveaux]

The tabs when configuring SAT appear to contain different options than described in README.md.

General

SAT 4.1.2 install in HA (in Dutch, but you get the point):

Differences w.r.t. the description in the section of the README.md file for 4.1.2:

• Missing in the documentation:
  • PID Controller Version 'Adaptive controller'
  • Only available when 'Dynamic Minimum Setpoint (Experimental)' under Advanced is enabled?:
    • Minimum Setpoint Controller Version
    • minimum_setpoint_adjustment_factor
• Missing in the HA configuration:
  • Automatic Gains Value
  • Derivative Time Weight
  • Adjustment Factor for Return Temperature

Presets

No description of both 'synchronization options'.

System configuration

Completely missing from the README.md.

Advanced

No description of 'Simulation', 'Error monitoring', 'Enforce PWM', 'Offset of climate valve', 'Sample time' (translated from Dutch, so actual terms may differ).

It seems that the readme is just outdated.

[sergeantd83]

Thank you very much for gathering all the missing informations. We will try to update the readme file soon. Until we will update the readme, please feel free to ask any questions regarding these informations.

[Yveaux]

@sergeantd83 I'm basically struggling with the following: my home has underfloor heating on the groundfloor and radiators with Sonoff TRVZB TRVs in the bedrooms. The underfloor is controlled by a Generic Thermostat in HA that switches the underfloor pump. The TRVs are controlled by individual Versatile Thermostat instances (https://github.com/jmcollin78/versatile_thermostat).
When I add the TRVs to the SAT config as room thermostats, their temperature differences trigger SAT to turn on the central boiler, as expected.
However the difference is initially rather large (e.g. 5 degrees C), so when the underfloor is at temperature (and its pump stopped), all heat will be directed to the radiator(s). This causes the boiler to immediately overshoot (I suppose that the radiator cannot handle all the power):

Here you see that the radiator was openened and after a short burner cycle (red bar at the bottom) it starts to repeatedly switch on/off for short cycles.

When only the underfloor is heating and radiators are closed, the return temperature is much lower (sorry for the inconsistent coloring):

I also found #88 PR which seems to add better balancing of generated power, but I'm not sure if it will help in my situation.

Thanks for your help!

[sergeantd83]

However the difference is initially rather large (e.g. 5 degrees C), so when the underfloor is at temperature (and its pump stopped), all heat will be directed to the radiator(s).

It’s likely that the Versatile climate entities are causing the issue by setting a high setpoint in the TRV climate entities.

I believe you have two proposed solutions:

• Use Versatile Climate Entities Instead of TRVs

During the initial configuration, add the Versatile climate entities in the rooms section instead of the TRV climate entities.

• Control Valves via Generic Thermostat Climate Entities

1. Set up one generic thermostat per TRV.
   Create an automation for each TRV to adjust the room setpoint:

2. Set a high setpoint (e.g., 24°C) when hvac_action == heating in the generic thermostat.

3. Set a low setpoint (e.g., 18°C) when hvac_action == idle in the generic thermostat.

4. Add the generic thermostats to the rooms section instead of the TRV climate entities.

Let me know if you need further clarification!

[Yveaux]

It’s likely that the Versatile climate entities are causing the issue by setting a high setpoint in the TRV climate entities.

Yes, the delta will be rather big, as the temperature in the bedrooms is maybe only 15 degrees and the target is set to 20. However I don't see how this is related to the type of thermostat (Versatile or Generic) ; it's just the result of setting a target that causes a large error.

• Use Versatile Climate Entities Instead of TRVs

That is indeed how I configured it. The TRVs are recognized as climate entries themselves by HA, with the limitation that the TRVs will control the temperature locally. I'd like to have a temparature sensor somewhere else in the room, so I put a Versatile Thermostat 'on top of' the TRV climate entry. This in itself works correctly, as the valves open and close depending on the temperature error from the room temperature sensor.

• Control Valves via Generic Thermostat Climate Entities

1. Set up one generic thermostat per TRV.
   Create an automation for each TRV to adjust the room setpoint:
2. Set a high setpoint (e.g., 24°C) when hvac_action == heating in the generic thermostat.
3. Set a low setpoint (e.g., 18°C) when hvac_action == idle in the generic thermostat.
4. Add the generic thermostats to the rooms section instead of the TRV climate entities.

Maybe I could build something where the increase in room setpoint is determined by the room capacity, or something.
I need to think about it a bit longer, but I was hoping SAT had the option to tune this is some way. Maybe through the PR #88 as I mentioned.

[sergeantd83]

Yes, the delta will be rather big, as the temperature in the bedrooms is maybe only 15 degrees and the target is set to 20. However I don't see how this is related to the type of thermostat (Versatile or Generic) ; it's just the result of setting a target that causes a large error.

Then you can try the Heating mode Eco option instead of Comfort in the general settings. Only your main climate entity will affect the CS value.