mattlward
(Matt Ward)
January 27, 2025, 3:16am
1
So, HACs finally removed the package for Midea ac units. Now I can’t remove it from HACS because HACS says I need to remove the integration first. When I try to remove the integration it thinks I did, but it is still there.
In HACS:
Navigate takes me here…
But, it does not delete the entity.
What am I doing wrong? Can I just delete the custom_components/midea_ac_lan folder to kill it? I assume that I would need to have Home Assistant stopped to do it this way?
Auto-configure and then control your Midea M-Smart devices (Air conditioner, Fan, Water heater, Washer, etc) via local area network. - georgezhao2010/midea_ac_lan
1 Like
stevemann
(Stephen Mann (YAML-challenged))
January 27, 2025, 11:25pm
3
Have you tried restarting Home Assistant?
mattlward
(Matt Ward)
January 28, 2025, 2:18am
4
Yes, many times. Also did the latest monthly update. I tried deleting the custom components folder for it and hacs just would not start after that. So, I did a full restore to get back up and running.
Any updates on this? Having the same issue.
mattlward
(Matt Ward)
January 30, 2025, 12:31am
7
Nothing new with mine. Have tried a couple other things but no change.
Not sure where to make a ticket as no support from author.
mattlward
(Matt Ward)
February 2, 2025, 4:12am
8
I just updated to the latest HACS as the release notes for 2.0.4 said " Handle deprecation in lovelace data by @ludeeus in #4402 "
I was on 2.0.3 and now on 2.0.5 and no change.
mattlward
(Matt Ward)
February 2, 2025, 4:34am
9
Not sure if it is the right place, but I just raised an issue with HACS backend.
opened 04:33AM - 02 Feb 25 UTC
issue:backend
### System Health details
## System Information
version | core-2025.1.4
-- | -… -
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.13.1
os_name | Linux
os_version | 6.6.66-haos
arch | x86_64
timezone | America/Chicago
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 4994
Installed Version | 2.0.5
Stage | running
Available Repositories | 1512
Downloaded Repositories | 23
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 14.1
-- | --
update_channel | stable
supervisor_version | supervisor-2024.12.3
agent_version | 1.6.0
docker_version | 27.2.0
disk_total | 109.3 GB
disk_used | 18.7 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization |
board | generic-x86-64
supervisor_api | ok
version_api | ok
installed_addons | DHCP server (1.4.0), Duck DNS (1.18.0), File editor (5.8.0), Glances (0.21.1), Home Assistant Google Drive Backup (0.112.1), Log Viewer (0.17.1), Mosquitto broker (6.5.0), Network UPS Tools (0.14.0), RPC Shutdown (2.5), SDR to Home Assistant (0.1.24), Advanced SSH & Web Terminal (20.0.0), Samba Backup (5.2.0), Samba share (12.4.0), WireGuard (0.10.2), HDD Tools (1.1.0), Scrutiny (Full Access) (v0.8.1-9), FTP (5.1.1), TasmoBackup (1.06.09), Z-Wave JS UI (3.19.0), TasmoAdmin (0.31.3), ESPHome Device Builder (2024.12.4), Matter Server (7.0.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 4
-- | --
resources | 10
views | 18
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | January 15, 2025 at 4:46 AM
-- | --
current_recorder_run | February 1, 2025 at 3:47 PM
estimated_db_size | 1133.48 MiB
database_engine | sqlite
database_version | 3.47.1
</details>
<details><summary>Sonoff</summary>
version | 3.8.2 (c4b6fda)
-- | --
cloud_online | 1 / 3
local_online | 0 / 0
</details>
### Checklist
- [x] I'm running the newest version of HACS <https://github.com/hacs/integration/releases/latest>
- [x] I have enabled debug logging for my installation.
- [x] I have filled out the issue template to the best of my ability.
- [x] I have read <https://hacs.xyz/docs/help/issues/>
- [x] This issue is related to the backend (integration part) of HACS.
- [x] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
- [x] This is a bug and not a feature request.
- [x] This issue is not a duplicate issue of currently [open](https://github.com/hacs/integration/issues) or issues [pending release](https://github.com/hacs/integration/issues?q=is%3Aissue+is%3Aclosed+sort%3Aupdated-desc+milestone%3Anext).
### Describe the issue
The midea _ac_lan integration was dropped from HACS. When I click the delete item from the drop down menu, it just never deletes it.


When I try to remove the repo in HACS I get the following message:


How do I make it go away?
### Reproduction steps
1.Have the midea_ac_lan repo installed.
2.Try to delete it.
3.
...
### Debug logs
```text
file:///C:/Users/mattl/Downloads/home-assistant_2025-02-02T04-31-09.107Z.log
```
### Diagnostics dump
[config_entry-hacs-9a57ab674b4c1f2bc58714986bdc569c.json](https://github.com/user-attachments/files/18631147/config_entry-hacs-9a57ab674b4c1f2bc58714986bdc569c.json)
mattlward
(Matt Ward)
February 2, 2025, 9:20pm
10
So ludeeus close my ticket and said just hit the ignore button. Really useful as it does not delete the integration which is still stuck there and cannot be deleted.
He should have been more clear about where to click “Ignore,” since my first thought was also that he was talking about ignoring the notification. But he was referring to the “Ignore” button from the dialog above, which indeed removes the integration after clicking it.
mattlward
(Matt Ward)
February 9, 2025, 4:43am
12
That finally did it!!! Thanks for the guidance.
And how exactly does one get to this dialogue? This is a perfect example for a completely borked UI.
mattlward
(Matt Ward)
February 9, 2025, 8:18pm
14
The initial ignore is done from within HACS by opening the midea install. Did and already forgot the specifics. I think it was the 3 dots on the upper right of that window and click remove or delete and then ignore. After I did that, I still could not clear the actual HA error until I rebooted HA and then it was just gone in devices.