Occupancy Manager interaction with Standalone scheduler

This document explains how scheduled heating and cooling temperatures work in a simple, easy-to-understand format for installers, QA teams, support teams, and non-technical stakeholders.

| Understanding the Basics

The controller allows users to configure:

• HDT - Heating Desired Temperature
• CDT - Cooling Desired Temperature

These temperatures can be configured separately for:

• Weekdays
• Weekends
  • Occupied mode
  • Unoccupied mode

| Temperature Limits (Min / Max Rules)

The User should always ensures temperatures stay within safe configured limits.

Heating Temperature Rules

Heating temperature must always stay between:

Heating Minimum  ≤  HDT  ≤  Heating Maximum

Cooling Temperature Rules

Cooling temperature must always stay between:

Cooling Minimum  ≤  CDT  ≤  Cooling Maximum

Dual Fix Rule Explained

In Dual Fix Temperature Mode, users must configure both:

• HDT
• CDT

The system maintains a fixed deadband between them.

Rule

CDT - HDT = Total Deadband

Example:

| How Different Temperature Modes Behave

| Occupied Schedule Configuration

Occupied schedules are used when the space is actively in use.

Users must configure temperatures:

• Within heating/cooling limits
• While following deadband requirements

Occupied Schedule Flow

User Configures Occupied HDT/CDT

 ↓
System Validates:
- Heating Min/Max
- Cooling Min/Max
- Deadband Rule

↓
Schedule Saved

 ↓
Applied as Occupied values
 

| Unoccupied Schedule Configuration

Unoccupied schedules help reduce energy usage when the space is empty.

Instead of maintaining strict comfort temperatures, the system relaxes the temperatures using:

Unoccupied Setback Temperature

managed by the Occupancy Manager.

Example

Unoccupied Flow

Unoccupied Schedule starts
  ↓
User entered Scheduled temperatures are considered
  ↓
These values are expected to be Occupied values. 
 ↓
Occupancy Manager applies the Setback tuner

| Scheduler and Occupancy Manager Interaction

When a scheduled event starts:

1. Scheduler checks current time
2. Occupancy Manager is suspended first
3. Scheduled configuration is then applied

This prevents conflicts between occupancy logic and scheduled events.

| Event Trigger Flow

Scheduled Event Time Reached
   ↓
Occupancy Manager Suspend Requested
  ↓
Suspend Successful?
 ↓ Yes                         ↓ No
Apply Scheduled         Do Not Apply
Configuration           Schedule
 

| Reboot Behaviour

This section explains what happens after a controller reboot.

Scenario

1. Schedule is active
2. User manually changes:
   • HDT or
   • CDT or
   • Conditioning mode
3. Controller reboots

Result

After reboot:

• Manual user changes are lost
• Scheduled configuration is applied again

| Important Note

Fan is NOT part of schedule configuration.

So:

• Fan changes remain unaffected
• Temperature and conditioning changes are overwritten

Reboot Flow

Schedule Applied
↓
User Makes Manual Changes
(HDT/CDT/Conditioning Mode)
↓
Controller Reboots
↓
System Reloads Active Schedule

↓
Manual User Changes Lost
 

| Key Takeaways