🛠️ Management & Workflow

Maintenance cycle, tooling and reporting for HA management at client locations. {.is-info}

---

Maintenance Cycle (bi-monthly)

1. Analyze release notes for breaking changes
2. Update test-HA environment and validate
3. Wait for patch release (.1) for stability
4. Update production installations: Backup → Add-ons → HACS → Core
5. Verify: dashboard reachable, devices active, remote access works
6. Generate report in CryptPad
7. Move Planka card to DONE

Rollback trigger: Dashboard unreachable > 10 min OR critical automation broken

Rule: Never skip more than 2 major versions.

---

Tooling

Tool	Role	Usage
Planka	Task overview	Columns: BACKLOG → SCHEDULED → IN PROGRESS → DONE
Calendar (Baikal)	Scheduling	Maintenance slots per client, technician assignment
Forgejo	Config storage	Git-versioned HA configurations per client
CryptPad	Reporting	Read-only links for client maintenance reports
Joplin	Field notes	Personal notes per technician during work

---

CryptPad Report Template

Each maintenance session gets a report containing:

• Version before/after update
• Executed steps (with timestamps)
• Downtime (if applicable)
• Issues (if applicable)
• Next maintenance date
• Link valid for 1 year

---

Access to HA Installations

Method	Details
Local	Via client's local network
Remote	Via Pangolin/VPN or HA Cloud (Nabu Casa)
App	Home Assistant Companion app
Configuration	Via Forgejo — configs per client in separate repository

---

See also: Managed Service | Installation Framework