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

minecraft server allowlist

Browse Source
This commit is contained in:
Roger Oriol
2026-08-23 11:54:17 +02:00
parent 70bc473280
commit ec6b83de3a
3 changed files with 16 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
home-manager/cron-seed.yaml
View File

@@ -10,11 +10,10 @@
# cron prompts containing curl+auth-header patterns. The exact HA REST API
# endpoints and examples are documented in the agent's SOUL.md instead.
#
# Schedule (4 jobs):
# 1. energy-anomaly — every 4h (silent unless power draw is too high)
# 2. comfort-check — every 4h (silent unless a room is out of range)
# 3. morning-briefing — 0 6 * * * (always delivered)
# 4. evening-briefing — 0 22 * * * (always delivered)
# Schedule (3 jobs):
# 1. comfort-check — every 4h (silent unless a room is out of range)
# 2. morning-briefing — 0 6 * * * (always delivered)
# 3. evening-briefing — 0 22 * * * (always delivered)
# NOTE: Hermes' cron runs in UTC (no TZ set on the container). The cluster is
# at UTC+2, so every fixed daily time below is expressed in UTC and shifted
# back 2h from the intended local wall-clock time:
@@ -85,19 +84,18 @@ spec:
kubectl -n home-manager exec "$POD" -- hermes cron create "$schedule" "$prompt" --name "$name" --deliver "$deliver"
}
# ---- 1. Energy anomaly (every 4h, silent unless too high) ----
create "energy-anomaly" "every 4h" "discord" \
"Check the Home Assistant REST API as documented in your SOUL.md. Read the current total house power draw sensor (sensor.* power / current_power — your main power clamp). Determine whether it is currently day (06:00 to 23:00) or night (23:00 to 06:00) from the current time. If the power draw exceeds 4000 W during the day, or exceeds 1000 W during the night, report to Roger on Discord: the current reading in watts, the time, whether it is day or night, and which threshold was exceeded. Ask Roger what he wants to do about it. Do NOT turn anything off or change any entity yourself — only report and ask. If power is within the normal range for the time of day, reply with exactly [SILENT]."
# Removed from schedule — make sure any live copy is deleted too.
kubectl -n home-manager exec "$POD" -- hermes cron delete "energy-anomaly" || true
# ---- 2. Temperature & humidity check (every 4h, silent unless out of range) ----
# ---- 1. Temperature & humidity check (every 4h, silent unless out of range) ----
create "comfort-check" "every 4h" "discord" \
"Check the Home Assistant REST API as documented in your SOUL.md. Read indoor temperature and humidity sensors in each room (sensor.*temperature, sensor.*humidity). Comfortable range: temperature between 18C and 26C, humidity between 30 and 65 percent. For any room that is outside that range, report to Roger on Discord: the room name (entity_id), the reading, and whether it is too high or too low. Ask Roger what he wants to do about it. Do NOT change climate/HVAC, fans, or any entity yourself — only report and ask. If every room is within the comfortable range, reply with exactly [SILENT]."
# ---- 3. Morning briefing (daily at 08:00 local = 06:00 UTC, always delivered) ----
# ---- 2. Morning briefing (daily at 08:00 local = 06:00 UTC, always delivered) ----
create "morning-briefing" "0 6 * * *" "discord" \
"Produce a morning home briefing for Roger using the Home Assistant REST API as documented in your SOUL.md. Include, in short bullet form: (1) today's calendar events from calendar.* entities for today (time + title); (2) open tasks from todo.* task lists; (3) overnight energy use — total energy consumed overnight from energy / utility_meter sensors, plus the current power draw; (4) outdoor and indoor temperature and humidity, and the current weather from weather.*; (5) occupancy status from zone.home — report its state if it exists; if zone.home is missing or unavailable, state 'occupancy: unknown — zone.home not configured' rather than claiming no one is home; (6) any sensors currently in an alert or unavailable state. Keep the message under 1800 chars. Always deliver (no [SILENT])."
# ---- 4. Evening briefing (daily at midnight local = 22:00 UTC, always delivered) ----
# ---- 3. Evening briefing (daily at midnight local = 22:00 UTC, always delivered) ----
create "evening-briefing" "0 22 * * *" "discord" \
"Produce an evening home status report for Roger using the Home Assistant REST API as documented in your SOUL.md. Report on: (1) lights currently turned on (light.* with state 'on'); (2) sockets and switches currently turned on (switch.* with state 'on'); (3) current energy use / power draw; (4) indoor temperature and humidity per room. List the specific entity_ids and their values. Then ask Roger which of the on devices/lights he wants turned off. Do NOT turn anything off yourself — only report and ask. Keep the message under 1800 chars. Always deliver (no [SILENT])."