Hi @JustTotallyMe,
you were not completely wrong with your assumption to control everything in openhab. Like @martin111 already wrote, you usually have several ways to achieve your goal.
For sure Martin’s solution is fine, but let me share some additional thoughts.
In comparison to Martin’s solution I wanted to have nearly everything in openhab. This applies not only to the thermostats, but also to all other devices.
In my setup the thermostats are always set to the manual mode - The auto mode is never used. If you’re using the auto mode, the schedule and the temperatures are managed by the CCU itself. In manual mode the CCU never changes any temperatures, but I’m using openhab rules to manage the temperatures.
I recommend you to have a look into the following:
Heating boilerplate with modes
Heating boilerplate DP
The reason why I want to have almost everything in openhab is that openhab should represent my logic layer.
I give you an example:
In the homematic CCU you could create a direct connection between a window sensor and a thermostat, to turn off the thermostat when the window is open. In this scenario you are limited to homematic devices.
If you build a rule in openhab instead to turn off the thermostat in the event of “Window changed to open”, you could use every window sensor which works with openhab.
Another example:
If you want to change the temperatures not just on a schedule, but maybe also on presence, you need to create rules in openhab. But if you have a schedule built in the CCU and logic in openhab, which one will win??
cheers,
Ralf