Hi everyone,
I’m running a simulation in Honeybee Legacy and I’m struggling with the zone heating and cooling behavior.
newset.3dm (373.4 KB)
setpoint-lbf.gh (622.7 KB)
- I created two schedules for the EP Zone Loads component – one for heating and one for cooling.
- Heating setpoint: 21 °C day, 18 °C at night.
- Cooling setpoint is 26 °C.
- Natural ventilation is only operates when the zone temperature is between 23–25 °C, so it shouldn’t conflict with heating or cooling.
What I expected was
- The zone should heat back up to 21 °C if it drops below that setpoint (18 °C at night).
- The zone should cool back down to 26 °C if it rises above that setpoint.
- Between 21–26 °C, there should be a deadband.
What actually happens:
- In winter, the indoor temperature doesn’t stabilize at the heating setpoint (21 °C). Instead, it continues rising and tries to reach
26 °C, as if the heating system is allowed to keep running all the way up to the cooling setpoint. - This creates the impression that the heating is “overshooting” the intended setpoint.
- When I add natural ventilation, the heating load spikes even more, but I believe the core issue is that the zone temperature is drifting up to the cooling setpoint rather than staying closer to the heating setpoint.
My main question is:
- Why does the zone temperature in winter climb all the way to 26 °C, instead of stabilizing around the heating setpoint (21 °C)?
- Is this how the dual setpoint thermostat works in Honeybee Legacy, or am I missing something in the schedule/thermostat setup?
Any clarification or examples would be greatly appreciated.
this is january first’s results, reaching 22 degree with 100 kwh consumption
and this is without natural ventilation, still reaching 26 degree without cooling
Thanks in advance!