Proxmox-addon partly doesn't work after HA core-update

Hi,
after updating HA core to 2025.05.02 my proxmox integration doesn’t work partly.
That means, I have to proxmox devices enabled. One with username, password and pam as realm. After disablbling and enabling the integration entries, it’s working now.
The other device was configuerd with user: HomeAssistant, Tokenname and token. REALM is pve.
I had a look at the log:

Logger: homeassistant.config_entries
Source: config_entries.py:1098
First occurred: 11:05:28 AM (1 occurrence)
Last logged: 11:05:28 AM

Error migrating entry 192.168.178.140:8006 for proxmoxve
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1098, in async_migrate
    result = await component.async_migrate_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/proxmoxve/__init__.py", line 372, in async_migrate_entry
    dev_reg.async_update_device(
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        device_id=device.id,
        ^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
        },
        ^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 1117, in async_update_device
    added_identifiers = new_values["identifiers"] = self._validate_identifiers(
                                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~^
        device_id, new_identifiers, False
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 1231, in _validate_identifiers
    raise DeviceIdentifierCollisionError(identifiers, existing_device)
homeassistant.helpers.device_registry.DeviceIdentifierCollisionError: Identifiers {('proxmoxve', '01JQHGHT9WFNFY19KFGY8B05QN_DISK_pve_nvme.144d-533733444e583158323434353533-53414d53554e47204d5a564c3435313248424c552d3030425457-00000001')} already registered with DeviceEntry(area_id=None, config_entries={'01JQHGHT9WFNFY19KFGY8B05QN'}, config_entries_subentries={'01JQHGHT9WFNFY19KFGY8B05QN': {None}}, configuration_url='https://192.168.178.140:8006/#v1:0:=node/pve::2::::::', connections=set(), created_at=datetime.datetime(2025, 5, 20, 11, 3, 34, 162020, tzinfo=datetime.timezone.utc), disabled_by=None, entry_type=<DeviceEntryType.SERVICE: 'service'>, hw_version=None, id='2084c107cee90cc829c000d028b0be26', identifiers={('proxmoxve', '01JQHGHT9WFNFY19KFGY8B05QN_DISK_pve_nvme.144d-533733444e583158323434353533-53414d53554e47204d5a564c3435313248424c552d3030425457-00000001')}, labels=set(), manufacturer='unknown', model='NVME SAMSUNG MZVL4512HBLU-00BTW ', model_id=None, modified_at=datetime.datetime(2025, 5, 20, 11, 3, 38, 57551, tzinfo=datetime.timezone.utc), name_by_user=None, name='Disk pve: SAMSUNG MZVL4512HBLU-00BTW', primary_config_entry='01JQHGHT9WFNFY19KFGY8B05QN', serial_number='S73DNX1X244553', suggested_area=None, sw_version=None, via_device_id='03e290375c03868c5651717c52d3901c', is_new=False, _cache={'json_repr': b'{"area_id":null,"configuration_url":"https://192.168.178.140:8006/#v1:0:=node/pve::2::::::","config_entries":["01JQHGHT9WFNFY19KFGY8B05QN"],"config_entries_subentries":{"01JQHGHT9WFNFY19KFGY8B05QN":[null]},"connections":[],"created_at":1747739014.16202,"disabled_by":null,"entry_type":"service","hw_version":null,"id":"2084c107cee90cc829c000d028b0be26","identifiers":[["proxmoxve","01JQHGHT9WFNFY19KFGY8B05QN_DISK_pve_nvme.144d-533733444e583158323434353533-53414d53554e47204d5a564c3435313248424c552d3030425457-00000001"]],"labels":[],"manufacturer":"unknown","model":"NVME SAMSUNG MZVL4512HBLU-00BTW ","model_id":null,"modified_at":1747739018.057551,"name_by_user":null,"name":"Disk pve: SAMSUNG MZVL4512HBLU-00BTW","primary_config_entry":"01JQHGHT9WFNFY19KFGY8B05QN","serial_number":"S73DNX1X244553","sw_version":null,"via_device_id":"03e290375c03868c5651717c52d3901c"}'})

I have no idea what this means.

I have the same issue. Anyone has an idea how to solve it yet?
Thanks,
Patrick

The core integration or the one from HACS ?