Headsup for users of my esphome implementation. We (me and David Woodhouse) have proxy mode working with the heishamon board (but should work on all esp32 with some levelshifters). We still need to do some testing, but you can run the esp and the melcloud wifi adapter together. You can even change setting from the esp. It needs a bit more testing and will be merged to main after testing.
more info about heishamon: https://www.tindie.com/products/thehognl/heishamon-communication-pcb/
current experimental impl: GitHub - gekkekoe/esphome-ecodan-hp at proxy
1 Like
It has been merged, see img folder for schematics. mini howto: esphome-ecodan-hp/proxy.md at main Ā· gekkekoe/esphome-ecodan-hp Ā· GitHub
1 Like
I know this is an old one but had the same problem and found the solution. The UI generates incorrect code, it should be:
action:
- action: water_heater.set_temperature
metadata: {}
data:
temperature: 53
target:
entity_id: water_heater.john_xxx - action: water_heater.set_operation_mode
metadata: {}
data:
operation_mode: force_hot_water
target:
entity_id: water_heater.john_xxx
This is just great. Iāll try in a few days. I guess unless I can find a male, wired CN105 connector, the only option is cutting and soldering the WiFi adapter cableā¦
https://www.digikey.nl/nl/products/detail/jst-sales-america-inc/B05B-PASK-1/926741
cn105 is just a standard B05B-PASK-1 socket
I lost my job so I need something to do, thought I would test ESP!
There are several projects on github and some are refrenced in this thread. Any recommendations on which project to try out? Im quite new to ESP in general but happy to learn!
Depends on what you would like to have. If you want to keep the melcloud running, then my project is the only option currently: GitHub - gekkekoe/esphome-ecodan-hp: ESPHome Ecodan heatpump
Another option thatās has comparable features is GitHub - F1p/Mitsubishi-CN105-Protocol-Decode: Mitsubishi Ecodan Air Source Heat Pumps CN105 Protocol to MQTT for Home Assistant
But the hardware is mostly the same, and you can try different firmwares. I would recommend the m5stack atom s3 lite from my project page (or heishamon v5 if you need proxy) as hardware.
Thanks for the info! 
The parts are cheap, about 9 euro but 18 euro in shipping, ouch 
Gonna see if i can find parts somewhere else but great work on your guide/readme!
If I get it running, I might contribute a swedish translation, the least I can do.
yeah you might find a local m5stack supplier in Swedenā¦ also digikey has free shipping if you order more than 50 euros
@gekkekoe In the wiring instructions for S3 Atom Lite with proxy you say
Select the
esp32s3-atoms3.yamlas configuration inecodan-esphome.yaml. Build and flash the firmware
but thereās no esp32s3-atoms3.yaml file in confs. Since Iām now using āesp32s3.yamlā for my S3 Atom Lite, should I use the one named ā esp32s3-proxy.yamlā? Thanks
correct, I will fix the docs (fixed, and also added ftc controller firmware & date time)
I get this error when validatingā¦
uart: [source /data/packages/224a9af1/confs/esp32s3-proxy.yaml:26]
- id: uart_ecodan
rx_pin:
number: 2
mode:
input: True
pullup: True
output: False
open_drain: False
pulldown: False
inverted: False
ignore_pin_validation_error: False
ignore_strapping_warning: False
drive_strength: 20.0
tx_pin:
number: 1
mode:
output: True
input: False
open_drain: False
pullup: False
pulldown: False
inverted: False
ignore_pin_validation_error: False
ignore_strapping_warning: False
drive_strength: 20.0
baud_rate: 2400
parity: EVEN
stop_bits: 1
rx_buffer_size: 256
data_bits: 8
- id: uart_proxy
rx_pin:
Cannot resolve pin name 'GPI38' for board esp32-s3-devkitc-1.
number: GPI38
mode:
input: True
pullup: True
tx_pin:
Cannot resolve pin name 'GPI39' for board esp32-s3-devkitc-1.
number: GPI39
mode:
output: True
GPIO38 and 39, I think I made an small error there. Iāve fixed it and test compiled it, should be okay now