WIKI ATOMS3 LITE implementation for Mitsubishi HP

[Marc911H]

I want to share my successful implementation in Home Assistant

I have Air/Air Mitsubishi MSZ-AP20VGK which comes with wifi module & MELCloud. But I wanted to move the wifi module to other HP.

Thanks to a MELCloud problem I start to look around for solutions.

Hardware

I landed on the https://github.com/fonske/esphome-ecodan-hp project with some "sexy" hardware, the solution looks very clean.

So I purchased 5 ATOMS3 LITE & Seeed Studio Grove - 4 pin Female Jumper to Grove 4 pin Conversion Cable (5 PCs per PAck)

The other side of the cable is supposed to be a a ST PAP-05V-S connector. I heard that it was difficult to build the connector specially if you don't have the right crimping pliers that are around 500€.
What I did : I removed the hard black plastic, put some insulation tape around the metallic part and with a simple pliers I "closed" carefully the female connector hole to match the pin width of the CN105.

I checked the pin & they match the picture.

Pin mapping (from left to right)

grove	cn105
pin 1 - black (gnd)	pin 4 - black (gnd)
pin 2 - red (5v)	pin 3 - red (5v)
pin 3 - white (GPIO 2)	pin 2 - white (Tx)
pin 4 - yellow (GPIO 1)	pin 1 - yellow (Rx)

Note: pin 5 (12v) on the cn105 is not used.

Software

I was looking to use ESPHOME with Home Assistant, I did not want to use MQTT. Keep Simple & native as possible.

I found this great project !

On the software side most of it still a mystery for me. ESPHOME act as a compiler & seem to have ESP library or link to.

What I got is that I need 1 yaml file to use the library that this project as created.
The API key generated when you click in new device in ESPHOME will help you to setup a secure connection between Home Assistant & the ESP32 S3 board.
There is also a secrets file where you store you wifi ssid & password

This is my device.yaml file (you need one for each device)

device.yaml
(remove the ".txt")

Note : compare to the project I needed to change

• PINs for rx & tx
• board: esp32-s3-devkitc-1
• framework type to arduino

Install it & then it works it even create a a web-server ... miracle.

You can then install you hardware in the HP for that you need to find the CN105 connector on the board somewhere.

I hope this helps

Don't hesitate to ask question.

Marc

[akifbayram]

This worked for me! Thank you. I made some changes since I'm using a remote sensor through Home Assistant. Also, my unit is one of five connected to one outdoor unit so some sensors aren't reported (compressor, sub_mode).

Tested with an MVZ-A18AA7:
heatpump-test.yaml

[fonske]

Hi.

I noticed you forgot or took out the code of the pushbutton G41 on the Atom s3 lite (binary_sensor in the code)
Also using a m5stack grove cable with a cn105 connector on the other end, the pins are tx_pin: GPIO02 and rx_pin:GPIO01. Tnx @akifbayram
I dont own a mitsubishi electric air to air heatpump, so i cant check the heatpump functions, but here is the adjusted code:
https://github.com/fonske/MitsubishiCN105ESPHome/blob/main/me_airco_atom_s3_lite.yaml

[herbod-nl]

Hello, I have a MSZ-EF25VGKW ZEN and have connected it with a Atoms3. ESPhome connects to the Atom but the Atom not to the airco. I have tried changing the tx/rx which did not help. any idea what I can do?

[echavet]

Hello, I have a MSZ-EF25VGKW ZEN and have connected it with a Atoms3. ESPhome connects to the Atom but the Atom not to the airco. I have tried changing the tx/rx which did not help. any idea what I can do?

Hello @herbod-nl,

We need to see your complete yaml config file to be able to help you.
First question for everyone in this thread: why do you force the framework type to Arduino whereas the esp in the atom is esp32s3?

[herbod-nl]

thanks for your reply. With esp32 I get an error with install. see image

[herbod-nl]

Here is the yaml i have used : https://github.com/fonske/MitsubishiCN105ESPHome/blob/main/me_airco_atom_s3_lite.yaml

I have also tried below with the result mentioned en the previous post.
esp32:
board: esp32-s3-devkitc-1
#board: esp32doit-devkit-v1
framework:
#type: arduino
type: esp-idf
version: latest

[herbod-nl]

I am not sure how it is your cable on the AtomS3 side but on the Airco side the yellow & white is swapped compare to what I did. uart: tx_pin: GPIO1 should be the white cable on the side of the AtomS3

Make sure also you test your cable contact (very easy to mess it up, if you did it yourself)

There is connection so the cables must be correct :-)

[echavet]

I'm not sure I understand, you did solve the issue by setting the edp-idf as the underlying framework?
You finally managed to compile thanks to a preliminary clean ?

Thanks for the feedback.

[herbod-nl]

I got it working bij changing

esp32:
board: esp32-s3-devkitc-1
#board: esp32doit-devkit-v1
framework:
#type: arduino
type: esp-idf <-------------------
version: latest

to

esp32:
board: esp32-s3-devkitc-1
#board: esp32doit-devkit-v1
framework:
type: arduino <--------------------
#type: esp-idf
version: latest

And than klik install.

I hope this answers your question.

Now I can controle the airco with ESPhome in HA and also with the Melcloud app (for my wife).

In home assistant was the auto option missing, this is available in the Melcloud app.
I could ad it bij adding auto.
supports:
mode: [COOL, HEAT, FAN_ONLY, DRY, AUTO]

Now I am still missing the controls for the horizontal vane
Any idea how to add it?

and energy consumption.

[disruptivepatternmaterial]

So when you change frameworks are you essentially doing what @echavet suggested - blowing away the build files and starting again. I'd bet with a 85.6% confidence that you'd have the same result if you switched back to ESP-IDF now.

I have everything in docker - and sometimes it helps to just blow away the container and start again when strange stuff happens.

Are you not showing us the field labled horizontal? That is what the drop down in the screenshot says...so maybe I'm misunderstanding something.

[herbod-nl]

So when you change frameworks are you essentially doing what @echavet suggested - blowing away the build files and starting again. I'd bet with a 85.6% confidence that you'd have the same result if you switched back to ESP-IDF now.

I have everything in docker - and sometimes it helps to just blow away the container and start again when strange stuff happens.

Are you not showing us the field labled horizontal? That is what the drop down in the screenshot says...so maybe I'm misunderstanding something.

I switched back to ESP-IDF and got the same issue as mentioned in my first post. Going back to arduino made it work again.
I don't think you misunderstanding something, I am not explaining it wel..

in the melcloud app there are horizontal and vertical vane selection. In homeassistant only the vertical.
Looking in the yaml file i found:

vertical_vane_select:
  name: Vertical Vane
# horizontal_vane_select:   <-----------------     I have removed the #
  # name: Horizontal Vane  <-----------------     I have removed the #
isee_sensor:
  name: ISEE Sensor
remote_temperature_timeout: 30min
debounce_delay : 500ms
update_interval: 4s
supports:
  mode: [COOL, HEAT, FAN_ONLY, DRY, AUTO]
  fan_mode: [AUTO, QUIET, LOW, MEDIUM, HIGH]
  swing_mode: ["OFF", VERTICAL] 

By removing the # the horizontal vane option appeared in homeassistant but the airco is not responding to it.

I can't find how to enable the sensor energery

[echavet]

For info on your esp-idf pb, chatGPT can help:

The error message indicates that there is an issue with running the kconfig tool during the build process of the ESP-IDF components for your ESP32 project in PlatformIO. The specific error fatal: not a git repository (or any of the parent to mount point) suggests that the build process is trying to perform a Git operation in a directory that is not a Git repository.

Here are the steps to resolve this issue:

1. Verify Git Repository:
   Ensure that the ESP-IDF repository is correctly initialized and available. Navigate to the ESP-IDF directory and check if it is a valid Git repository:

   cd /data/build/airco-slaapkamer
   git status

   If this directory is not a Git repository, you may need to initialize it or clone the ESP-IDF repository again.

2. Reinstall ESP-IDF Components:
   Sometimes reinstalling the ESP-IDF components can resolve configuration issues. Run the following commands to reinstall:

   pio pkg uninstall -g framework-espidf
   pio pkg install -g framework-espidf

3. Check CMake Configuration:
   There might be an issue with the CMake configuration. Make sure the kconfig file and the related environment are correctly set up. You can try running CMake manually to see if there are specific errors:

   cd /data/build/airco-slaapkamer
   cmake -S . -B build

4. Ensure Python Environment:
   Verify that the Python environment used by PlatformIO is correctly configured and all necessary packages are installed:

   pio system info

5. Update PlatformIO:
   Ensure that you are using the latest version of PlatformIO and its packages:

   pio upgrade
   pio update

6. Check for Environment Variables:
   Make sure that the environment variables required by ESP-IDF are correctly set. This includes paths to toolchains and other configurations:

   export IDF_PATH=~/esp/esp-idf
   export PATH="$PATH:$IDF_PATH/tools"

By following these steps, you should be able to identify and resolve the issue causing the build failure. If the problem persists, please provide additional details or context about your setup and the specific configuration files being used.

[tmchow]

Having trouble with this.. I've got an Atom S3 Lite and i'm not able to get any info from the minisplit.

As mentioned above, I reversed the wires for Tx and Rx since it's the Atom s3 but not sure if that's correct in all cases or contingent on the heatpump. How do I know for sure?

My config is based on all the info above and i use type: arduino otherwise I cannot install the config, I get a Cmake error if I use esp-idf.

substitutions:
  name: my-room-climate
  friendly_name: My Room Climate

esphome:
  name: ${name}
  friendly_name: ${friendly_name} 

esp32:
  board: esp32-s3-devkitc-1
  framework:
    #type: arduino
    type: esp-idf
    version: latest

light:
  - platform: esp32_rmt_led_strip
    name: Led
    id: led
    internal: true
    rgb_order: GRB
    pin: 35
    num_leds: 4
    rmt_channel: 1
    chipset: ws2812
    restore_mode: ALWAYS_ON

uart:
  id: HP_UART
  baud_rate: 2400
  tx_pin: GPIO1
  rx_pin: GPIO2

# Default logging level
logger:
  level: INFO

external_components:
  - source: github://echavet/MitsubishiCN105ESPHome

api:
  encryption:
    key: !secret esp_encryption_key
  services:
    - service: reboot
      then:
        - logger.log: "Reboot in progress..."
        - lambda: |-
            ESP.restart();
ota:
  - platform: esphome
    password: !secret ota_password

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "My-Room-Atom-S3-Lite"
    password: !secret wifi_password

captive_portal:

web_server:
  port: 80

# Sync time with Home Assistant.
time:
  - platform: homeassistant
    id: homeassistant_time

# Create a button to restart the unit from HomeAssistant. Rarely needed, but can be handy.
button:
  - platform: restart
    name: "Restart ${friendly_name}"

# Climate entity configuration
climate:
  - platform: cn105
    name: "My Room Climate"
    icon: mdi:heat-pump
    compressor_frequency_sensor:
      name: ${name} Compressor Frequency
    vertical_vane_select:
      name: ${name} Vertical Vane
    horizontal_vane_select:
      name: ${name} Horizontal Vane
    debounce_delay : 500ms
    update_interval: 4s  # update interval can be ajusted after a first run and logs monitoring* 

text_sensor:
  - platform: wifi_info
    ip_address:
      name: IP
    ssid:
      name: SSID
    bssid:
      name: BSSID

  - platform: version
    name: Version
    hide_timestamp: true
    disabled_by_default: false
    icon: mdi:new-box
    entity_category: diagnostic

# Sensors with general information.
sensor:
  # Uptime sensor.
  - platform: uptime
    name: "Uptime"
    disabled_by_default: false
    force_update: false
    unit_of_measurement: s
    icon: mdi:timer-outline
    accuracy_decimals: 0
    device_class: duration
    state_class: total_increasing
    entity_category: diagnostic
    update_interval: 60s

  - platform: internal_temperature
    name: Internal Esp temperature
    entity_category: diagnostic

  - platform: wifi_signal # Reports the WiFi signal strength/RSSI in dB
    name: Signaal dB
    id: wifi_signal_db
    update_interval: 60s
    entity_category: diagnostic

  - platform: copy # Reports the WiFi signal strength in %
    source_id: wifi_signal_db
    name: Signaal %
    filters:
      - lambda: return min(max(2 * (x + 100.0), 0.0), 100.0);
    unit_of_measurement: " %"
    entity_category: diagnostic
    device_class: ""

switch:
  - platform: template
    id: eps32_s3_led_switch
    name: Led switch #${led_switch}
    optimistic: true
    restore_mode: RESTORE_DEFAULT_ON 
    lambda: return id(eps32_s3_led_switch).state;
    turn_on_action:
      - light.turn_on:
          id: led
          brightness: !lambda |-
            // output value must be in range 0 - 1.0
            return id(led_brightness).state / 100.0;
    turn_off_action:
      - light.turn_off:
          id: led


number:
    ## Set led brightness
  - platform: template
    id: led_brightness
    name: Led brightness #${led_brightness}
    icon: mdi:toggle-switch-variant
    mode: slider
    entity_category: config
    optimistic: true
    min_value: 0
    max_value: 100
    step: 10
    initial_value: 70
    restore_value: yes
    unit_of_measurement: "%"
    on_value:
      then:
        - if:
            condition:
              - light.is_on: led
            then:
              - light.turn_on:
                id: led
                brightness: !lambda |-
                  // output value must be in range 0 - 1.0
                  return id(led_brightness).state / 100.0;

I don't even know where to start on this...

[akifbayram]

Try reversing tx and rx pins.

uart:
  id: HP_UART
  baud_rate: 2400
  tx_pin: GPIO2
  rx_pin: GPIO1

[tmchow]

Try reversing tx and rx pins.

uart:
  id: HP_UART
  baud_rate: 2400
  tx_pin: GPIO2
  rx_pin: GPIO1

That was it! Thank you.

[tmchow]

I’ve got two problems.

First, without remote temperature sensor, my unit is reporting a current temp of 0 degrees celcius for some reason.

Screenshot from the web server:

(In HA since it’s reporting in Fahrenheit it says it’s 32F). I expected this to work right out of the box so confused why it’s not.

If i turn debug logging on, there's this portion of output which shows it's not able to get the current temp:

[20:26:16][D][SETTINGS:098]: [current]-> [power: OFF, target °C: 23.0, mode: COOL, fan: 4, vane: SWING, wvane: |]
[20:26:16][D][SETTINGS:098]: [received]-> [power: OFF, target °C: 23.0, mode: COOL, fan: 4, vane: SWING, wvane: |]
[20:26:16][D][EVT_SETS:057]: [wanted]-> [power: -, target °C: -1.0, mode: -, fan: -, vane: -, wvane: -, hasChanged ? ->  NO, hasBeenSent ? ->  NO]
[20:26:16][D][SETTINGS:079]: [climate]-> [mode: OFF, target °C: 23.0, fan: HIGH, swing: VERTICAL]
[20:26:16][V][CN105:239]: updating action back to espHome...
[20:26:16][D][CN105:267]: Climate mode is: 0
[20:26:16][D][CN105:268]: Climate action is: 0
[20:26:16][D][climate:396]: 'My Room Climate' - Sending state:
[20:26:16][D][climate:399]:   Mode: OFF
[20:26:16][D][climate:401]:   Action: OFF
[20:26:16][D][climate:404]:   Fan Mode: HIGH
[20:26:16][D][climate:416]:   Swing Mode: VERTICAL
[20:26:16][D][climate:419]:   Current Temperature: 0.00°C
[20:26:16][D][climate:425]:   Target Temperature: 23.00°C
[20:26:16][D][CYCLE:285]: 3a: Sending room °C request (0x03)

Second, issue with remote temp sensor setup.
I'm confused on how to get remote temperature working. I've got zigbee sensors in better places for more accurate temp that at the minisplit. The sensor is HA is sensor.living_room_temperature.

In my config I have this, which is based on the repo's readme:

api:
  encryption:
    key: !secret esp_encryption_key
  services:
    - service: reboot
      then:
        - logger.log: "Reboot in progress..."
        - lambda: |-
            ESP.restart();
    - service: set_remote_temperature
      variables:
        temperature: float
      then:
## Select between the C version and the F version
## Uncomment just ONE of the below lines. The top receives the temperature value in C,
## the bottom receives the value in F, converting to C here.
        - lambda: 'id(living_room_climate).set_remote_temperature(temperature);'
#        - lambda: 'id(living_room_climate).set_remote_temperature((temperature - 32.0) * (5.0 / 9.0));'
    - service: use_internal_temperature
      then:
        - lambda: 'id(living_room_climate).set_remote_temperature(0);'

#Remote temperature sensor
  - platform: homeassistant
    id: current_temp
    entity_id: sensor.living_room_temperature
    internal: true
    on_value:
      then:
        - lambda: |-
            id(living_room_climate).set_remote_temperature(x);

However, my temperature is being reported as 32F which is clearly incorrect. I'm missing something obvious, could use some pointers.

[akifbayram]

Regarding the second point, try this:

climate:
  - platform: cn105
    id: living_room_climate # add ID 
    name: "My Room Climate"
    icon: mdi:heat-pump
    compressor_frequency_sensor:
      name: ${name} Compressor Frequency
    vertical_vane_select:
      name: ${name} Vertical Vane
    horizontal_vane_select:
      name: ${name} Horizontal Vane
    debounce_delay : 500ms
    update_interval: 4s

This is my remote temperature sensor, for comparison:

sensor:
  - platform: homeassistant
    id: current_temp
    internal: true
    entity_id: sensor.selected_temperature_main
    on_value:
      then:
        - lambda: |-
            float temp_f = id(current_temp).state;
            float temp_c = (temp_f - 32.0) * (5.0 / 9.0);
            ESP_LOGI("custom", "Current Temp (F): %.1f, Temp (C): %.1f", temp_f, temp_c);
            id(hp).set_remote_temperature(temp_c);
    filters:
      - heartbeat: 10s

[tmchow]

@akifbayram Before i go down the remote sensor route, I want to make sure the internal temp sensor works to handle the case where the remote temp sensor fails to get a reading.

[ericvanbeurden]

flashed this and it works pretty ok on my 4x indoor MKZ-KT25VG & 2x outdoor MXZ-2F42VF
There are some problems and questions:

1. When the air-conditioner is off I see a yellow error in the log on the web interface.
   1:19:33 [W] [lookup:204] submode caution: value 16 not found, returning value at index 0

2. Compressor Frequency doesn't show while it is running in cooling mode (and I assume in any other mode).
   21:23:21 [I] [STATUS:132] [received]-> [room C°: 20.5, operating: YES, compressor freq: 0 Hz] 21:23:21 [I] [STATUS:132] [current]-> [room C°: 21.0, operating: YES, compressor freq: 0 Hz]
   This could be since I have 2 indoor units connected to 1 outdoor unit. I saw somebody posting about this but his solution wasn't clear to me.

3. The horizontal vane wasn't enabled. I enabled it and also added horizontal to swing mode, however I don't see any reaction on my air conditioner.

horizontal_vane_select: #added name: Horizontal Vane #added swing_mode: ["OFF", VERTICAL, HORIZONTAL] #horizontal

I have this option in Melcloud, however on my remote I only have the option 1flow / 2 flow. (which I believe refers to the horizontal vane).
After enabling it I see the option appearing in the webinterface, however it doesn't react to actions on my remote. While changing the vertical vane on my remote reflects in the webinterface.

5. Fan mode is missing completely to adjust the speed of the fan. Not sure how to enable this.

Does anybody have suggestions for this?

[yettavr6]

Can you help me at all with the installation of the software onto the S3? I'm really not understanding it at all. I was able to load ESPHome onto the device, but that just gives me a web UI with only an option to load a project. It doesn't accept anything I download as a project. I installed Arduino IDE but none of the instructions I'm following make sense in there either. In HA, ESPHome basically has no options other than to add a device by IP address (which I was able do after connecting the device to my wifi using the web UI, but there's no where there to add the YAML or whatever the next step is). I found some command lines but I don't even know how to get to the ESPHome command line. I'm on a Mac FWIW.

[echavet]

If you have the cli esphome why do you flash with the webui?
Just use the command
esphome upload

[yettavr6]

I'd go back a step and try to get things working one step at a time again.

The typical best way to onboard a device is to have the ESPHome addon open in HomeAssistant, in Chrome (which supports WebSerial), and to have your device plugged into USB C.

From there, create a new device, give it a name, skip the automatic configuration, and just select the hardware type "ESP32-S3". It will create a default configuration, but "skip" installing it yet. From there, hit the "edit" button on your device to work on the configuration YAML file, which you can use these examples to build up.

One thing you may want to do is comment out external_components and the climate component at first. Install, selecting "connected to this computer" to upload to the device plugged into your computer (this is why we are using Chrome, WebSerial allows this). What you want to see is that the build compiles without fatal errors, uploads to the device, and that the device boots up, connects to the wifi, and start showing you some basic logs. If that isn't working, then any ESPhome troubleshooting forum can help. Once it is working there, then add the external_component and climate component back in.

So, i had read something of this sort, but I do not get those options in ESPHome in Home Assistant. When I click Add Device, it asks me for an IP address and port. There is no option to skip.

[yettavr6]

nevermind, I was confusing ESPHome addon with the ESPHome service. This is only my second day using HA :). Still not sure there's anything I can do now given the current state of my S3, endlessly rebooting

[phidauex]

HomeAssistant and ESPHome are extremely flexible, which is great, but sometimes the fact that there are 10 ways to do something makes it hard to pick the one way that works best for you. I'd recommend focusing on the ESPhome tab inside of HomeAssistant's main interface, and do your file editing and uploading from inside this environment. While your device is NOT working correctly, have it plugged into the same computer, and do the update with "Plug into this computer", which works fine on a Mac running Chrome:

After your device is working, and you simply want to update the firmware or make a small configuration change, then "Wirelessly" will work, which will send the update over the air.

You should easily be able to recover the S3, the installation protocol should force it into bootloader mode. If that isn't working, check the S3 documentation, some boards have a method where you hold down a boot button to force it into bootloader mode before updating. But it is extremely hard to "brick" an ESP32, you just need to get it back into the bootloader and push a good build.

[yettavr6]

OMG I GOT IT WORKING :D

So, as you said, I was able to recover by putting it into a bootloader mode using a button. I had read this earlier, but didnt realize there are two buttons on the Atom S3. There is one on the front and another on the side. It was the side button that did it. Once I got it in bootloader mode, I uploaded the firmware.factory.bin generated by creating a new device in the ESPHome addon in HA. After that flashed, I flashed the the firmware.factory.bin (instead of the firmware.bin) that I had compiled earlier, and everything is working. I'm so happy :).

Also, I wanted to mention that i bought the HY2.0-4P cable and the 5 pin connector, and then used a jeweler's screwdriver to remove one of the 4-pin connectors from the cable and replace it with the 5-pin connector. This way I didn't have to solder or crimp anything.