docs: add ha1 memory recommendation to migration plan
Some checks failed
Run nix flake check / flake-check (push) Failing after 3m28s
Some checks failed
Run nix flake check / flake-check (push) Failing after 3m28s
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -154,6 +154,10 @@ For each stateful host, the procedure is:
|
|||||||
6. Verify Zigbee devices are still paired and communicating
|
6. Verify Zigbee devices are still paired and communicating
|
||||||
7. Decommission old VM
|
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
|
**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
|
coordinator state in `/var/lib/zigbee2mqtt` should preserve pairings, but verify on a
|
||||||
non-critical time window.
|
non-critical time window.
|
||||||
|
|||||||
Reference in New Issue
Block a user