KNX fails to load after upgrading to 2025.8.2

Configuration
1

Hi all
After upgrading to 2025.8.2 KNX installation failed to load. I didn’t do anything “special”. Just clicked upgrade. Had to revert to 2025.8.1. This is what the log shows. Appriciate all input!

Logger: homeassistant.util.package
Source: util/package.py:159
First occurred: 23:35:31 (21 occurrences)
Last logged: 23:35:52

Unable to install package xknxproject==3.8.2: × Failed to read `xknxproject==3.8.2` ├─▶ Failed to read metadata from installed package `xknxproject==3.8.2` ├─▶ Failed to parse METADATA file: │ `/usr/local/lib/python3.13/site-packages/xknxproject-3.8.2.dist-info/METADATA` ╰─▶ Metadata field Name not found
Unable to install package wakeonlan==3.1.0: × Failed to read `wakeonlan==3.1.0` ├─▶ Failed to read metadata from installed package `wakeonlan==3.1.0` ├─▶ Failed to parse METADATA file: │ `/usr/local/lib/python3.13/site-packages/wakeonlan-3.1.0.dist-info/METADATA` ╰─▶ Metadata field Name not found
Unable to install package unifi-discovery==1.2.0: × Failed to read `unifi-discovery==1.2.0` ├─▶ Failed to read metadata from installed package `unifi-discovery==1.2.0` ├─▶ Failed to parse METADATA file: │ `/usr/local/lib/python3.13/site-packages/unifi_discovery-1.2.0.dist-info/METADATA` ╰─▶ Metadata field Name not found
Unable to install package xiaomi-ble==1.1.0: × Failed to read `xiaomi-ble==1.1.0` ├─▶ Failed to read metadata from installed package `xiaomi-ble==1.1.0` ├─▶ Failed to parse METADATA file: │ `/usr/local/lib/python3.13/site-packages/xiaomi_ble-1.1.0.dist-info/METADATA` ╰─▶ Metadata field Name not found
Unable to install package yeelight==0.7.16: × Failed to read `yeelight==0.7.16` ├─▶ Failed to read metadata from installed package `yeelight==0.7.16` ├─▶ Failed to parse METADATA file: │ `/usr/local/lib/python3.13/site-packages/yeelight-0.7.16.dist-info/METADATA` ╰─▶ Metadata field Name not found
2

Hi! Do you have the full log available still? I do think this errors are the result of a different thing happened before.

3

True, it does seem like a result of something else :frowning: But I really didn’t touch anything besides doing that update. And don’t have logs anymore as I pulled a backup :frowning:

Will try to update again today.

4

When you update and it fails again, maybe also try to start in safe-mode. But having that log certainly helps finding the curlpit.