From 4d330182853bba2195eec63928075f2d27c513cb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Torjus=20H=C3=A5kestad?= Date: Thu, 5 Feb 2026 17:48:45 +0100 Subject: [PATCH] docs: add ha1 memory recommendation to migration plan Co-Authored-By: Claude Opus 4.5 --- docs/plans/host-migration-to-opentofu.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/plans/host-migration-to-opentofu.md b/docs/plans/host-migration-to-opentofu.md index 4a54292..7f537fc 100644 --- a/docs/plans/host-migration-to-opentofu.md +++ b/docs/plans/host-migration-to-opentofu.md @@ -154,6 +154,10 @@ For each stateful host, the procedure is: 6. Verify Zigbee devices are still paired and communicating 7. Decommission old VM +**Note:** ha1 currently has 2 GB RAM, which is consistently tight. Average memory usage has +climbed from ~57% (30-day avg) to ~70% currently, with a 30-day low of only 187 MB free. +Consider increasing to 4 GB when reprovisioning to allow headroom for additional integrations. + **Note:** ha1 is the highest-risk migration due to Zigbee device pairings. The Zigbee coordinator state in `/var/lib/zigbee2mqtt` should preserve pairings, but verify on a non-critical time window.