It is difficult to understand who has which level.
Also the fact that this (still) uses a custom repository doesn’t make it easier.
Another difficulty is that OTA don’t work on all ESP’a due the file size being too big.
All in all there are many different ways to compile.
I think it is easiest to:
Maybe you shouldn’t use this component at that stage. The development of this component is in it’s early stages, and it doesn’t work out of the box. That will come, but it’s not here yet, and if you struggle to work with ESPHome in a development branch, this component is not yet for you. 
It’s not meant rude, it is simply acknowledging that some people are more experienced than others. This is not yet a component that doesn’t involve trying, errors and possible damage to devices. If you know what you’re doing, that’s ok, because you can estimate the risk you’re willing to take. If not, you could easily ruin something, and that’s not the purpose of this component.
I have quite large devices installed with both simple and custom integrations that work well. But since I am not good in programming, some things are not clear to me. Specifically in the case of this integration, how to connect midea-climate-support to esphome. In fact, your proposal is rather unfriendly and this approach will scare off many people, as a result, the product will be geeky and designed for a very small number of diy wariors 80 lvl))
See, that’s where you’re wrong. This component is not at a stage, where people without deeper knowledge of how things work should install it. Simple as that. And as you said earlier, and your questions show, you are not one of these people (yet).
That doesn’t mean you could not get there, but at the moment it’s not for you. And to make that totally clear, it is not unfriendly to tell someone to wait for a stage of development, where the user knowledge combines well with the stage of the component.
In this thread everything you need is written down. If you can’t understand that, you’re not the audience for this component yet. And let me asure you, this component will not be geeky or designed for a small number of people, it will be nothing of that, once development has reached a state where people with a “normal” HA knowledge can work with. Right now it is more hindering, if questions are asked, that have nothing to do with developing this component…
To make it short: this component is in a developing stage, called it a beta version. As long as you don’t know what you are doing, leave it, until it get’s to a testing stage.
That will also be the time, where someone will make a write-up with instructions on how to install and use it. There is a reason, why instructions are not as clear, as a “normal” user would need it: to stop people from ruining their installations, because they don’t know what they are doing.
Ok, you’re right, everything is really here, but it took a lot of time to figure out such a simple thing. The submission of information is very upsetting, but glad to have it, thanks to Aceindy
Works without TTL converter (WeMos D 1) and is updated via OTA.
Go to Supervisor-> ESPhome-> Configuration
in the line esphome_version add dudanov: midea-climate-support, Save, the plugin will ask for a restart.
Next, go to the ESPhome tab and, as usual, create a configuration with the code specified at the beginning of the branch. compile the file and flash the ESP
It’s all. Why information on cmd python, docker was given. I had to install Python, I assure most people using HA this is not a standard program. I had to install Git. And all this was unnecessary.
Probably because you used a WeMos D1, which has more RAM than the ESP01 I used.
Hence OTA works, and installing Python/Git is not needed…
But I did not have a WeMosD1 and ended up with
ERROR Error binary size: Error: ESP does not have enough space to store OTA file. Please try flashing a minimal firmware (remove everything except ota)
So I needed to find another way to load the binary in the ESP 
As said before, there are many ways to flash ESP.
And also, yes this is still in Beta, so we just figure things out as we go…
Anyway…happy it works 
Might aswell ask you a question then 
You say you use a Wemos D1, do you use this with a logic level shifter? Someone else in this thread who uses a Wemos said he needed a level shifter. I’m planning on building two more advanced dongles with extra IR support and maybe RF based on a Wemos.
That exactly proves my point. If you don’t know why, chances are high you don’t know how. Let’s just assume, something goes wrong with this. Did you do a backup before you changed your ESPHome version to the one dudanov is offering? Did you do a backup of HA before doing all this?
I’m quite sure you didn’t. 
And now let’s assume something has gone wrong. The only people who could really help will most likely be the developers of this intergation. So their time goes into helping others, where it should/could go into developing the integration. You get the idea.
Besides the fact, that I personally wouldn’t want to be responsible for any damage you might do to your climate unit, if you pump the wrong voltage into it. What if this thing blows? I can only imagine what outcry that would be.
But let me just say, I’m glad it worked for you, and I hope it works flawlessly for you in the future. If you could report back any problems, that would be helpful to the developers as well.
@nvschilleman You should use a level shifter, as the Voltage seems to be important. As far as I can see, the D1 sends with 3.3V, whereas the A/C seems to need 5V (or was it vice versa?). Can’t you measure it with the original dongle? I would use a level shifter, before you damage either the D1 or the A/C.
nvschilleman As I wrote above, I use the WeMos D1 Rx and Tx pins. They are limited to 6V, then they are simply limited. How NodeMCUs from other manufacturers work, I can’t say, need to read the documentation
paddy0174 daily backup https://github.com/samccauley/addon-hassiogooglebackup#readme
Hey @aceindy,
Just to let you know that with the latest DEV ESPHome update, I could update the ESP01 by OTA without issues (with the previous version I had the same exact issue you have).
You may want to give it a shot
Cheers
So I’ve got the dev version of ESPHome installed but still getting this:
And I’m getting this when using the python method:
All my ESP-01’s flash OTA without problems, maybe erasing Them completely and flashing Them over UART once Will fix your issue, that’s what I did.
So what is the recommended Home Assistant ESPHome addon to use now?
Is it still the dev version?
I have tried it with and without the custom version entry in configuration with no changes in the outcome.
The “midea_ac” component is still not being recognized.
Would someone mind elaborating on what they are currently using with success?
Using this for the custom version just worked for me…
dudanov:midea-climate-support-wo-integrity-check
how did you get yours to work mine only shows TX in the logs,
im using a wemos D1 though
i think you have to use this repository:
that repository came out after nvschilleman had reported similar issues.
Where? here:
yea saw the same thing, I have the repo installed witch made it show up in HA and with a connect status, for the D1 mini.
How every wen I check the logs in ESPhome i only get a TX control in the log, as ican not control the unit
Blockquote
[21:21:52][D][midea_dongle:094]: TX: AA 22 AC 00 00 00 00 00 03 02 40 41 86 00 7F 7F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 66 C2
[21:21:53][D][midea_ac:050]: TX: control
[21:21:53][D][midea_dongle:094]: TX: AA 22 AC 00 00 00 00 00 03 02 40 41 86 00 7F 7F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 66 C2
[21:21:54][D][midea_ac:050]: TX: control
[21:21:54][D][midea_dongle:094]: TX: AA 22 AC 00 00 00 00 00 03 02 40 41 86 00 7F 7F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 66 C2
witch puzzles me a bit
Do you use a level shifter on the TX/RX pins of the Wemos?
no i do not wasn’t aware i need one, any suggestions for one ?
