Hi,
I maintain a small custom integration. Lately, a few users have reported issues that we’ve traced to the underlying library (msmart-ng) being out of date with the version specified in the manifest.
The manifest.json
{
"domain": "midea_ac",
"name": "Midea Smart AC",
"codeowners": [
"@mill1000"
],
"config_flow": true,
"dependencies": [],
"documentation": "https://github.com/mill1000/midea-ac-py",
"iot_class": "local_polling",
"issue_tracker": "https://github.com/mill1000/midea-ac-py/issues",
"loggers": [
"msmart"
],
"requirements": [
"msmart-ng>=2024.9.0"
],
"version": "2024.9.2"
}
In the first report, the integration reports it is using library version 2024.7.3
, the second report is stuck using 2024.5.4
.
I’ve asked both users to uninstall and reinstalled the integration with no luck. I’ve had both enable debug logging and we see an attempt to install the correct requirement with no indication of failure, yet the old library remains in use.
e.g. From case 2.
2024-09-17 22:18:10.095 INFO (SyncWorker_59) [homeassistant.util.package] Attempting install of msmart-ng>=2024.9.0
2024-09-17 22:18:10.096 DEBUG (SyncWorker_59) [homeassistant.util.package] Running pip command: args=['/usr/local/bin/python3', '-m', 'pip', 'install', '--quiet', 'msmart-ng>=2024.9.0', '--timeout', '60', '--upgrade', '--constraint', '/usr/src/homeassistant/homeassistant/package_constraints.txt']
...
2024-09-17 22:19:05.188 INFO (MainThread) [custom_components.midea_ac] Starting midea-ac-py for device ID 31885837306570 (192.168.68.76:6444). Using msmart-ng version 2024.5.4.
In at least one case, it appears that pip believes the correct requirement is installed, but the integration is still referencing the older version.
At this point it appears that HA is looking for the requirements in an alternate location, but I am at a loss at what to do about it.
Any help would be greatly appreciated.