github dougiteixeira/proxmoxve 6.0.0b1

latest release: 6.0.0
pre-release52 minutes ago

Breaking Change: Domain Migration

Important

The automatic Marketplace update will fail if you attempt to perform the update without first manually installing version 6.0.0b0. This is expected behavior.
Version 6.0.0b0 is responsible for migrating the integration domain from proxmoxve to proxmoxve_custom.
If you have not installed version 6.0.0b0, please follow the steps below.

Caution

Create a full Home Assistant backup before starting. Only legacy configuration entries at version 7 can migrate automatically. Do not remove the integration from Devices & Services.
The commands require shell access, curl and unzip. Replace config if your Home Assistant configuration directory is elsewhere.

1. Install version 6.0.0b0 manually

This transition release installs both components and migrates eligible legacy entries. Do not remove the integration from Devices & Services.

cd /config &&
  mkdir -p custom_components/proxmoxve custom_components/proxmoxve_custom &&
  curl -fL -o /tmp/proxmoxve-6.0.0b0.zip \
    https://github.com/dougiteixeira/proxmoxve/releases/download/6.0.0b0/proxmoxve.zip &&
  curl -fL -o /tmp/proxmoxve-custom-6.0.0b0.zip \
    https://github.com/dougiteixeira/proxmoxve/releases/download/6.0.0b0/proxmoxve_custom.zip &&
  unzip -o /tmp/proxmoxve-6.0.0b0.zip -d custom_components/proxmoxve &&
  unzip -o /tmp/proxmoxve-custom-6.0.0b0.zip -d custom_components/proxmoxve_custom

Restart Home Assistant. Each enabled, eligible legacy entry is migrated automatically; disabled entries must be enabled to start migration. Use the restart button in the repair that appears, then verify the new entry, devices, entities and automations. Restore the backup if the migration does not succeed.

2. Check the legacy component

The new integration removes the recognized legacy directory automatically once no legacy entries or incomplete migrations remain. If the directory is already absent, continue to the next step.

If the directory remains, first verify that all legacy entries, including disabled entries, have migrated and that the directory belongs to this legacy integration. Do not remove it while any legacy entry or migration is pending.
Once verified, you can remove a regular directory manually:

cd /config &&
  if [[ -L custom_components/proxmoxve ]]; then
    printf 'Legacy path is a symbolic link; inspect it before removing it.\n'
  elif [[ -d custom_components/proxmoxve ]]; then
    rm -r -- custom_components/proxmoxve
  else
    printf 'Legacy directory is already absent.\n'
  fi

Restart Home Assistant if you removed the directory manually.

3. Install version 6.0.0b1 through the Marketplace

  • After verifying the migration, uninstall the old repository from the Marketplace, not from Devices & Services.
  • Install the repository again through the Marketplace and select version 6.0.0.

This resets the Marketplace's recorded domain without deleting the migrated configuration entry. Restart if the Marketplace requests it. Subsequent updates can then be installed through the Marketplace.

The new entry receives a new entry ID. Its settings, options, devices, device IDs and entity IDs are transferred, and entity unique IDs are adjusted to match the new entry. The proxmoxve.backup action remains available as an alias for proxmoxve_custom.backup. A detected registry conflict stops the transfer; check the Home Assistant logs before retrying.

After the new integration starts successfully and all legacy entries have been removed, it removes the recognized legacy custom_components/proxmoxve directory. It leaves the directory in place while disabled, incompatible or incomplete legacy entries remain, or if it is a symbolic link or does not match this integration's manifest. Cleanup is retried on subsequent starts; check the logs if file permissions prevent removal.

The Marketplace does not update an installed repository when its domain changes; the manual transition and Marketplace reinstallation above are required for existing installations. The new release must advertise proxmoxve_custom in its root manifest and in the proxmoxve_custom.zip manifest. Once reinstalled, subsequent Marketplace updates install only proxmoxve_custom.

What's Changed

Full Changelog: 5.3.5...6.0.0b0
Full Changelog: 6.0.0b0...6.0.0b1

Don't miss a new proxmoxve release

NewReleases is sending notifications on new releases.