Cannot connect to heatpump - tested with D1 mini, #85
Comments
|
I'm having the same problem still after adding a 3.3V regulator to a D1 mini, as documented in #70 I'm getting exactly the same result, it is getting no reply from the heatpump. If I use the code from GeoffDavis repository set to 2400 baud I can send commands and the heatpump responds so I know that is the correct baud rate and at least the TX line is working. I wonder if we also need the resistors as shown here in the SwiCago info?
|
|
I've just now added 10kOhm resistors as above, between the RX and TX lines to the 5V line, but no change in behaviour. On the D1 Mini I am measuring 3.56v across the RX pin and 3.3V across TX, which seems a little odd. I've triple checked my connections and it all seems correct. I've tried a third D1 Mini, but not luck, so I doubt the devices are faulty. I also gave mitsubishi2mqtt a go, and it can't connect either. So it's not the code, but hoping we can pool info and solve it |
Well, if you're sure that: then I'm afraid you don't have many options left! What happened to me once, when I was using a specific connection scheme with both a heat pump and a Raspberry Pi (for collecting logs) connected to two different UARTs on the controller, was that I couldn't get the controller to read the heat pump responses either. My error was using the Raspberry Pi's ground for the controller instead of the heat pump's ground. It's really important for both sides of the UART to share the same ground. I think the most crucial thing is to ensure a nice and stable ground connection between the two. So, I would try using a pull-down resistor rather than a pull-up. However, I must admit my knowledge of hardware electronics is very limited, so this could also be a terrible piece of advice! edit: I see you're using v1.2.2. You should use the latest version.. |
|
I have tested 👍 these setups: esp8266:
board: d1_mini
uart:
id: HP_UART
baud_rate: 2400
tx_pin: 1
rx_pin: 3esp32:
board: esp32doit-devkit-v1
framework:
type: esp-idf
uart:
id: HP_UART
baud_rate: 2400
tx_pin: GPIO17
rx_pin: GPIO16esp32:
board: esp32-s3-devkitc-1
framework:
type: esp-idf
variant: esp32s3
uart:
id: HP_UART
baud_rate: 2400
tx_pin: GPIO17
rx_pin: GPIO18 |
|
Could you add pictures of your setup for each controllers ? Today I only use esp32 with esp-idf. I've never seen any setup working with a baudrate different of 2400. |
|
Thanks for your suggestions. I have reversed the connection for the 10kOhm resistors so they connect to the GND as a pull down resistor, but it's still the same. The board I am using is this one https://www.aliexpress.com/item/1005005121150737.html I have tried 3 of them, so unlikely it's a faulty board. I may end up just getting ESP32 board as others have had problems with ESP8266, or seeing if I can order the one you use. I am using this setup: Also I use this for the components, I thought that means I am using the latest, v 1.3? If not, do I just download the latest release zip file and how do I install it? I thought it did it at install/build time using the external component, but I'm quite new to this. |
|
Got it working at last ! I used the Atom Echo and carefully reviewed the wiring again (like for the 99th time...) and it was recognized immediately. I suspect there may have been contact issues with the dupont connectors previously. The equipment used for this test setup:
For now it looks like this:
Thanks for the work you put into this ! It means I will be able to dump the unreliable Melcloud service. |
|
So I've tried various things all morning and decided to give up on this D1 Mini I have. I've ordered both Atom Lite and a generic ESP32 board. Will give them both a go in a few weeks when they arrive and fingers crossed it all come right. Thanks for the help so far |
|
I have no luck communicating with a MSZ-LN25VGW. I have tried two different ESP32WROOM boards. Tried changing baud rates up to 9600, no luck. IT just tries to reconnect every 4 seconds. The ESP is wired straight from CN105 port, no resistors.I still have a D1 mini to try when I get the energy. My config down below. substitutions:
name: mitsubishi
friendly_name: Mitsubishi
esphome:
name: ${name}
friendly_name: ${friendly_name}
esp32:
board: esp32dev
framework:
type: esp-idf
uart:
id: HP_UART
baud_rate: 2400
tx_pin: GPIO17
rx_pin: GPIO16
external_components:
- source: github://echavet/MitsubishiCN105ESPHome
# refresh: 0s
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "XXX"
password: "YYY"
captive_portal:
# Enable logging
logger:
hardware_uart: UART1
level: INFO
logs:
EVT_SETS : INFO
WIFI : INFO
MQTT : INFO
WRITE_SETTINGS : INFO
SETTINGS : INFO
STATUS : INFO
CN105Climate: WARN
CN105: INFO
climate: WARN
sensor: WARN
chkSum : INFO
WRITE : WARN
READ : WARN
Header: INFO
Decoder : INFO
CONTROL_WANTED_SETTINGS: INFO
# level: DEBUG
# logs:
# EVT_SETS : DEBUG
# WIFI : INFO
# MQTT : INFO
# WRITE_SETTINGS : DEBUG
# SETTINGS : DEBUG
# STATUS : INFO
# CN105Climate: WARN
# CN105: DEBUG
# climate: WARN
# sensor: WARN
# chkSum : INFO
# WRITE : WARN
# READ : WARN
# Header: INFO
# Decoder : DEBUG
# CONTROL_WANTED_SETTINGS: DEBUG
# Enable Home Assistant API
api:
encryption:
key: "XYXY"
services:
- 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(hp).set_remote_temperature(temperature);'
# - lambda: 'id(hp).set_remote_temperature((temperature - 32.0) * (5.0 / 9.0));'
- service: use_internal_temperature
then:
- lambda: 'id(hp).set_remote_temperature(0);'
ota:
password: "12345"
# Enable Web server.
web_server:
port: 80
# Sync time with Home Assistant.
time:
- platform: homeassistant
id: homeassistant_time
# Text sensors with general information.
text_sensor:
# Expose ESPHome version as sensor.
- platform: version
name: ${name} ESPHome Version
# Expose WiFi information as sensors.
- platform: wifi_info
ip_address:
name: ${name} IP
ssid:
name: ${name} SSID
bssid:
name: ${name} BSSID
# Sensors with general information.
sensor:
# Uptime sensor.
- platform: uptime
name: ${name} Uptime
# WiFi Signal sensor.
- platform: wifi_signal
name: ${name} WiFi Signal
update_interval: 120s
# Create a button to restart the unit from HomeAssistant. Rarely needed, but can be handy.
button:
- platform: restart
name: "Restart ${friendly_name}"
climate:
- platform: cn105
id: hp
name: "${friendly_name}"
icon: mdi:heat-pump
visual:
min_temperature: 15
max_temperature: 31
temperature_step:
target_temperature: 1
current_temperature: 0.1
compressor_frequency_sensor:
name: ${name} Compressor Frequency
vertical_vane_select:
name: ${name} Vertical Vane
horizontal_vane_select:
name: ${name} Horizontal Vane
isee_sensor:
name: ${name} ISEE Sensor
remote_temperature_timeout: 30min
debounce_delay : 500ms
update_interval: 4s |
|
Try to remove the
from your log section You must take care either to use a different UART for logs and for the heat pump, or to disable logging to UART.
Look at the UART numbers and their corresponding Rx and tx pin numbers: https://docs.espressif.com/projects/esp-at/en/latest/esp32/Get_Started/Hardware_connection.html |
|
Thanks for your help. I removed Hardware_uart: UART1And added logger:
baud_rate: 0Something changed in the writeback in the log, but still no communication. Then I changed tx_pin: GPIO17
rx_pin: GPIO16After googling ESP32 WROOM 32 pin out diagram. tx_pin: GPIO1
rx_pin: GPIO3Now its working, woohoo :) |
|
Same issue here with the LOLIN Wemos D1 Mini V4.0.0 I have not been successful with any config. |
Yes it is known that this controller cannot connect with heatpump |
👍 I didn't know that. 🫤 I switched it with an AZDelivery board and everything works as expected. |
The issue with the d1 mini v4 compared to the earlier v1.0.0 board is that there is no resistor on the board between the rx pin and the ch340c usb controller chip. Without this resistor when the AC unit tries to pull this line to ground it is unable to get the voltage to drop low enough because current backfeeds from the usb controller. You can modify the board by lifting pin 2 of the usb controller and either leaving it disconnected along with adding a 10k pull up resistor between the RX(GPIO3) and VBUS OR you can put a 470ohm resistor between the lifted pin 2 on the usb controller and the RX(GPIO3) pin to match the wiring of the earlier v1 board It is also worth noting that you cannot easily use the alternate UART pins on GPIO 13/15 without both providing a pull resistor on those pins but also ensuring that GPIO15 is not pulled up during startup or the board will not boot. I'm just data dumping here, because I've been struggling with a bunch of these v4 boards that bought in bulk and it was maddening see many reports of them not working, but without any concrete advice on how to work around their failing edit: For reference, this is the relevant part of the circuit on various esp32 modules which are reported as working.
You can see the the 470ohm resistors in line. This one also has an led wired in which blinks when it is using the usb for serial comms |
|
Very happy to report that this is finally working for me. All I did was order a ESP32 board, connected it to the VIN (5V) and GND with GPIO16 and 17 and it's working perfectly. No resisters or voltage regulator needed. This is the board I ordered |
I have a Lolin V3.1.0 and can't seem to be able to get it working either. Is that controller known to be not working as well? |
|
Yes ! I'm not surprised, the UART communication between the chip and the heat pump is quite sensitive. It requires a stable and very clean power supply. Ultimately, few chips are clean enough to establish reliable communication. |
This board also has a bare connection between its USB controller and the uart0 Rx pin, it should work with a small rewire as I detailed in my previous comment. |
Let's walk through some logic here. A 2000$ up to 30,000$ HVAC system and people keep wanting to save 5$ on controllers. Does this make sense to anyone? Hell, it is a free country, as they say... Stop buying junk from randos on the internet: the adafruit, m5, and lilygo are more money, but we are talking less than 10$ more and they just work. I use ONLY m5 because they by and large contain the same plugs, which makes them easy to use, they mostly contain battery controls, and come in nice cases. Adafruit get a thumbs down from me because of the power issues they build into their products; which are solved in the m5. I have never had an issue with an m5 device. I use the stamps (orange ones). I even have other sensors on them and they never fail. |
|
@drawks @disruptivepatternmaterial So thanks for the product recommendation! // EDIT: Got it working now on first try with an AZ-Delivery board as well (like @marsavela). |
|
@disruptivepatternmaterial I'm not sure the issues of this project is the place to debate the relative value proposition of the various microcontrollers. They are all very similar, cost has very little to do with it. The entire market of knock off d1 controllers are trace and component identical to the more expensive original wemo design, they contain the same flaw as that design. It is nice that this project does maintain a list of controllers which are known to work with no additional circuitry, beyond that I don't think it contributes anything to the project to imply that people are having problems because they are "buying junk from randos on the internet". There are plenty of 15 dollar parts that don't work and there are plenty of 3 dollar ones that do. |
I've been trying to connect to my MSZ-AP25VGK (wall unit with built-in WiFi) using
The D1 mini was setup correctly in ESPHome (2024.4.2) but the logs showed
[E][CN105:032]: --> Heatpump did not reply: NOT CONNECTED <--
[I][CN105:033]: Trying to connect again...
[W][CN105:157]: Heatpump has not replied for 40 s
[I][CN105:158]: We think Heatpump is not connected anymore
[I][CN105:093]: setupUART() with baudrate 2400
Both ESP32 devices gave similar output:
[16:44:29][I][app:100]: ESPHome version 2024.4.2 compiled on May 1 2024, 16:31:16
[16:44:29][E][CN105:317]: sync impossible: heatpump not connected
[16:44:29][E][CN105:317]: sync impossible: heatpump not connected
but when I powered them on, the horizontal vane of the MSZ opened and closed, so there must be something going on. I tried three different baud rates : 2400, 4800 and 9600. All gave the same result.
Config for the D1 mini (I removed the wifi setup and api key info):
Config for the ESP32 (in this case the Atom):
I did read #70, so I will be getting a voltage regulator for the D1 mini, but I thought this wouldn't be necessary for the ESP32 devices?
Is there anything else I'm missing?
thanks,
Hans
The text was updated successfully, but these errors were encountered: