Track Proxmox core integration parity before switching from custom proxmoxve

[CCOSTAN]

Goal

Track whether Home Assistant Core's built-in Proxmox VE integration has enough parity to replace the current custom proxmoxve integration.

Do not switch incrementally. Revisit this after each new Home Assistant Core release. Once core covers all required entities and controls, switch cold turkey and remove the custom integration dependency.

Why now

Home Assistant Core 2026.7 added Proxmox improvements, including config-flow work and a longer API connection timeout. The current core documentation also shows support for Proxmox sensors, binary sensors, and control buttons.

References:

• Home Assistant Core 2026.7 changelog: https://www.home-assistant.io/changelogs/core-2026.7
• Core Proxmox VE integration docs: https://www.home-assistant.io/integrations/proxmoxve/
• Current custom integration: https://github.com/dougiteixeira/proxmoxve

Current dependency surface to preserve

Before switching, core must cover or allow clean replacement for the current production surfaces:

• Node status and runtime health used by the infrastructure dashboard.
• VM/LXC status entities used for outage recovery and infrastructure monitoring.
• VM control buttons needed by outage recovery and maintenance workflows, especially start, shutdown, stop, and reboot.
• Node package-update detection, including update-available binary sensors.
• Package-count/update-list sensors used to build Joanna/BearClaw handoff payloads for Proxmox patching.
• Node CPU, memory, and disk pressure sensors used by dashboards and alerts.
• Storage/disk health and storage usage sensors currently provided by the custom integration.
• Entity IDs or compatibility shims stable enough that dashboard, recorder, package, and automation references do not break.

Revisit checklist for each Home Assistant Core release

• Review the latest Home Assistant Core release notes and full changelog for Proxmox VE changes.
• Compare core Proxmox entity coverage against the current custom proxmoxve entity list.
• Confirm whether core exposes package-update detection and update-list details equivalent to the custom integration.
• Confirm whether core exposes the required VM/LXC control buttons with safe Proxmox permissions.
• Confirm whether core exposes required disk/storage health and usage sensors.
• Confirm whether entity names can be preserved directly or through small template compatibility shims.
• If parity is complete, plan one cold-turkey migration window: add core integration, validate all referenced entities, update YAML/dashboard references, remove custom integration, restart, and verify automations/dashboards.

Security cleanup opportunity

If/when this migration happens, use the official guidance to move to a dedicated Proxmox PVE realm user/API token with only the required permissions instead of broad host credentials.

Acceptance criteria

• Core Proxmox integration covers all production entity and button needs.
• config/packages/proxmox.yaml, the infrastructure dashboard, Powerwall outage recovery, and recorder exclusions all validate against the new entity surface.
• Home Assistant config check passes.
• The custom proxmoxve integration can be removed without losing required monitoring or controls.