You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(decisions): record HA climate/thermostat control as out of scope (#612)
#442's value controls (light dimming, cover position, fan speed) shipped in
v0.2.0. The thermostat/climate setpoint is a deliberate won't-do; log it so a
future session does not re-add the climate domain to the action allowlist.
Ref #442 (closed).
Signed-off-by: badbread <badbread@users.noreply.github.com>
Co-authored-by: badbread <badbread@users.noreply.github.com>
Copy file name to clipboardExpand all lines: docs/DECISIONS.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,31 @@ revisit.
8
8
9
9
---
10
10
11
+
## 2026-08-10, Home Assistant `climate` (thermostat/HVAC setpoint) control is out of scope
12
+
13
+
**Context.**#442 introduced value-setting HA controls. Light dimming
14
+
(`set_brightness`), cover position (`set_position`), and fan speed (`set_speed`)
15
+
shipped in v0.2.0 and actuate from the on-video badge, gated by the `actuators`
16
+
capability. The issue also listed a thermostat/climate setpoint
17
+
(`climate.set_temperature`).
18
+
19
+
**Decision.** The `climate` domain is deliberately NOT in the action allowlist
20
+
(`HA_ACTION_ALLOWLIST`, `services/api/src/ha.rs`); a unit test asserts
21
+
`climate.set_temperature` stays rejected. A camera view is a security-monitoring
22
+
surface, not a thermostat UI, and setpoint control would add a per-entity
23
+
min/max/step/unit contract across every client for something the operator can
24
+
already do in Home Assistant itself. #442 was closed as complete on the three
25
+
delivered value controls.
26
+
27
+
**Rejected:** adding `climate` control (the "Slice 2" once sketched in an
28
+
HA-management plan). Owner decision, 2026-08-10.
29
+
30
+
**Revisit if:** the maintainer wants HVAC control on the video wall and will own
31
+
the setpoint min/max/step/unit UI across all clients. Until then, keep `climate`
32
+
out of the allowlist.
33
+
34
+
---
35
+
11
36
## 2026-08-08, A main whose SDP lacks `fmtp` is repaired for Android by an OPT-IN H.265->H.264 transcode (`_mainv`), not the `_subv`-style copy — because a copy-remux reintroduces an AP Media3 can't read
12
37
13
38
**Context.** Some cameras (verified: a Uniview H.265 LPR main) publish their main
0 commit comments