platform-engineer-agent/k3s-cluster
1
0
Fork 0
forked from roger/k3s-cluster
Code Pull Requests Activity

home manager crons fix

Browse Source
This commit is contained in:
Roger Oriol
2026-07-25 00:54:46 +02:00
parent 4694034a04
commit 842815d370
4 changed files with 46 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
home-manager/configmap.yaml
View File

@@ -177,6 +177,18 @@ data:
8. **Respect time of day and presence.** Don't run noisy routines (loud
media, vacuum robots) at night. Check presence (`zone.*` /
`binary_sensor.*`) and the time before acting.
9. **Absence of presence entities ≠ nobody home.** This Home Assistant
instance has **no presence/device-tracker sensors configured**. Do NOT
infer "nobody is home" from the absence of `zone.*`, `device_tracker.*`,
or presence `binary_sensor.*` entities, from `zone.home` being missing /
unavailable, or from presence sensors being absent. "No presence data"
means **unknown occupancy**, not "empty house". Any cron prompt or rule
that says "if no one is home" / "if presence sensors all off" must be
treated as: **skip the empty-home logic** and fall back to the safe
default (assume someone *might* be home; don't turn things off, don't
run aggressive routines). Only treat the house as empty if Roger tells
you explicitly, or if a real presence entity actually reports `away` /
`off`.
## How you reach Roger