Tucker Kern

Here are some observations I've noticed - The devices don't handle multiple connections well. e.g. If you're using the app alongside this integration you might have connection issues. Or running...

It appears the matching indoor unit (40MPHA) contains the actual WiFi connectivity. Based on the manual the WiFi module is one of the following parts: KSAIF0101AAA, KSAIF0201AAA, KSAIF0301AAA, KSAIF0401AAA, KSAIF0501AAA,...

A possible solution for you. Install the latest commit (or even better my [future branch](https://github.com/mill1000/midea-ac-py/) instead). It supports configuration via the GUI and registers a device which can be renamed.

Duplicate of #197. This project is currently in a broken state. Manually installing msmart inside the docker container should have fixed it. Might need to clear the browser cache or...

There's a PR out for this #177. I have a fork with this and other PRs merged. You can add it as a custom repo in HACS. https://github.com/mill1000/midea-ac-py

There's a `home-assistant.log` in the same directory as `custom_components`. You should try clearing your browser cache, or trying a hard refresh (PC: `Ctrl-F5`, Mac: `Cmd-Shift-R`)

That is likely because of mac-zhou/midea-msmart#90. Unfortunately this integration is currently in a bit of a bad state. I've got a branche with a number of fixes merged here: [mill1000/midea-msmart](https://github.com/mill1000/midea-msmart/tree/future)....

To me it looks like HA is still using the old version of midea-msmart because the `get_capabilities` call is missing. I've had issues where HA doesn't update the requirements even...

Great. I was just about to reply to see if you were using this [add-on](https://github.com/hassio-addons/addon-ssh) or other "official" one. The official one seems quite limited in its use

If you're getting issues with `get_capabilities`, then it sounds like you're installing msmart...at least not where HA is looking for it. Are you running these pip commands within the Docker...