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

Device takes a long time to respond to request. Longer read timeout necessary? #315

Open
mill1000 opened this issue Feb 26, 2025 · 0 comments
Labels
msmart-ng Issue is with underlying msmart-ng library need more info Further information is requested

Comments

@mill1000
Copy link
Owner

Originally posted in another issue, the logs from this user show the device responding but typically after the first timeout. This causes multiple responses to be received since the device also responds to the resent request.

Now that I've found this ticket, perhaps it has something to do with running as midea_ac_lan.

Yes running both integrations against a device can cause problems.

I initially used the Carrier app to control my mini split then uninstalled it when I discovered this integration. Now I don't know how, if even possible, to NOT use midea_ac_lan. Thoughts?

I don't follow? Is there a functionality missing that you need from midea_ac_lan?

I'm running only this integration. Sorry, disregard the midea_ac_lan comments. I thought that meant a LAN configuration rather than Carrier's cloud configuration, which I have not used for a very long time.

I need full debug log to help. The summary provided by HA is useless.

See attached

home-assistant_2025-02-23T03-25-10.248Z.log

Originally posted by @ryanandres in #283

@mill1000 mill1000 added need more info Further information is requested msmart-ng Issue is with underlying msmart-ng library labels Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
msmart-ng Issue is with underlying msmart-ng library need more info Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant