Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Old version of integration remains cached after manual update #478

Open
BenJewell opened this issue Jan 26, 2025 · 2 comments
Open

Old version of integration remains cached after manual update #478

BenJewell opened this issue Jan 26, 2025 · 2 comments

Comments

@BenJewell
Copy link

BenJewell commented Jan 26, 2025

I was trying to install my fork of this integration over top of the existing version and it wasn't working. Then I realized after more testing that HA seems to be doing some caching of the data in the custom_components/midea_ac_lan folder. If you manually change the version number in manifest.json and restart HA, it does not get reflected anywhere. Then it gets stranger, you can rename/move the custom_components/midea_ac_lan folder entirely, and restart HA, and it will continue functioning, using the last known code.

It appears to be being cached somewhere within HA. Therefore, the instructions in the description under option 3 to install this no longer work. Whatever HACS is doing to "reset" the cache is not being done when installing the integration with the manual method. It may work for the original installation, but definitely not any subsequent updates after the integration is configured.

Deleting and reconfiguring the integration from the UI also does not seem to have any affect of clearing this "cache". Does anyone else experience this, or know of a workaround?

@wzlwtq133
Copy link

My HA also has such a problem. Due to system issues, I haven't found a simple way to delete files. So currently, I can only refrain from updating HA and the software.

@wuwentao
Copy link
Owner

wuwentao commented Feb 5, 2025

@BenJewell @wzlwtq133 NO one provided a debug log file when you works in an ERROR status.
we just need the debug log file when you works in this status, NO one can guess it without log.
so please always add debug log when you post some issue.

anyway, you still can upload it in current issue, if there is no any debug log exist, we will close current issue, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants