-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathtemperature-control.txt
54 lines (36 loc) · 1.34 KB
/
temperature-control.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
Temperature Control state machine
Low-level (Allowable range)
===========================
Two inputs:
1) Heating or Cooling mode
2) Desired Temperature (e.g. 65F)
General logic:
- if heating mode and current temperature < desired, turn on heating
- if cooling mode and current temperature > desired turn on AC
Considerations:
- allow for hystheresis (+/- some degrees)
- allow for duty cycle limit (no on/off within X time period)
High-Level (Programming)
========================
Level 0: Manual Control
- fixed desired low/high temperatures
Level 1: Weekday/Weekend scheduling, with up to 4 periods per day
- separate schedules for heating (desired lows) and cooling (desired highs) modes
- period override (resets at next period)
- hold (stays until manually cleared)
- optional: predict temperature response to achieve next period's constraint
Level 2: Smart modes
- Holiday (override indefinitely)
- Weekend away (override until Sunday 6pm)
- Guests staying (?)
- WFH (override until 6pm)
- improvement is "override until X" function
Scrapped Ideas:
Low-level (Allowable range)
===========================
Two inputs:
1) Desired Low Temperature (e.g. 65F)
2) Desired High Temperature (e.g. 80F)
General logic:
- if current temperature < Desired Low, turn on heating
- if current temperature > Desired High, turun on AC