Salt78
commented
2 years ago I am having the same issue.
Closed jdgarcia99 closed 1 year ago
Salt78
commented
2 years ago I am having the same issue.
sitexw
commented
2 years ago I have exactly the same problem...
Log:
[19:44:05]ets Jun 8 2016 00:22:57
[19:44:05]
[19:44:05]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[19:44:05]configsip: 0, SPIWP:0xee
[19:44:05]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[19:44:05]mode:DIO, clock div:2
[19:44:05]load:0x3fff0018,len:4
[19:44:05]load:0x3fff001c,len:1044
[19:44:05]load:0x40078000,len:8896
[19:44:05]load:0x40080400,len:5828
[19:44:05]entry 0x400806ac
[19:44:05][I][logger:214]: Log initialized
[19:44:05][C][ota:458]: There have been 3 suspected unsuccessful boot attempts.
[19:44:05][D][esp32.preferences:114]: Saving preferences to flash...
[19:44:05][I][app:029]: Running through setup()...
[19:44:05][I][MitsubishiHeatPump:063]: ESPHome MitsubishiHeatPump version 2.3.2
[19:44:05][C][MitsubishiHeatPump:416]: Setting up UART...
[19:44:05][C][MitsubishiHeatPump:428]: Intializing new HeatPump object.
[19:44:05][C][MitsubishiHeatPump:455]: hw_serial(0x3ffc19c8) is &Serial(0x3ffc1a00)? NO
[19:44:05][C][MitsubishiHeatPump:457]: Calling hp->connect(0x3ffc19c8)
... wait 5-10s ...
[19:44:10]E (10205) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
[19:44:10]E (10205) task_wdt: - loopTask (CPU 1)
[19:44:10]E (10205) task_wdt: Tasks currently running:
[19:44:10]E (10205) task_wdt: CPU 0: IDLE0
[19:44:10]E (10205) task_wdt: CPU 1: IDLE1
[19:44:10]E (10205) task_wdt: Aborting.
[19:44:10]abort() was called at PC 0x40151b18 on core 0
[19:44:10]
[19:44:10]ELF file SHA256: 0000000000000000
[19:44:10]
[19:44:10]Backtrace: 0x40088ac8:0x3ffbf810 0x40088d45:0x3ffbf830 0x40151b18:0x3ffbf850 0x40087205:0x3ffbf870 0x40168e5f:0x3ffbc160 0x40153423:0x3ffbc180 0x4008b505:0x3ffbc1a0 0x40089d56:0x3ffbc1c0
[19:44:10]
[19:44:10]Rebooting...Config:
esphome:
name: esp-test
esp32:
board: nodemcu-32s
#...
external_components:
- source: github://geoffdavis/esphome-mitsubishiheatpump
climate:
- platform: mitsubishi_heatpump
name: "Test clim"
hardware_uart: UART2Env:
mattatcha
commented
2 years ago FYI, I ran into the same issue when rx,tx weren't connected to the configured uart port.
sitexw
commented
2 years ago I must admit that I had doubts about my RX and TX connections when I did the tests. My connection wasn't exactly the right one, so I had to scrape it off with a cutter. Visually, it fits well, but I'm not 100% sure that the connections are made...
I'll try to get the correct connector and let you know.
MarkoPaasila
commented
2 years ago I can confirm that connecting to the heatpump solves this problem for me.
Stendec1
commented
2 years ago Just got it up-and-running on the AZ-Delivery D1 Mini ESP32 using UART0. You have to swap the RX & TX connection!!
Following is my ESPHome configuration file for this device:
esphome:
name: ${name}
esp32:
board: lolin_d32
variant: ESP32
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: ${name}
password: !secret wifi_password
# Note: if upgrading from 1.x releases of esphome-mitsubishiheatpump, be sure
# to remove any old entries from the `libraries` and `includes` section.
#libraries:
# Remove reference to SwiCago/HeatPump
#includes:
# Remove reference to src/esphome-mitsubishiheatpump
captive_portal:
# Enable logging
logger:
# ESP8266 only - disable serial port logging, as the HeatPump component
# needs the sole hardware UART on the ESP8266
baud_rate: 0
# Enable Home Assistant API
api:
services:
- service: set_remote_temperature
variables:
temperature: float
then:
- lambda: 'id(hp).set_remote_temperature(temperature);'
- service: use_internal_temperature
then:
- lambda: 'id(hp).set_remote_temperature(0);'
ota:
password: !secret 'esphome_api_password'
# 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: 60s
- platform: homeassistant
name: Temperature Sensor From Home Assistant
entity_id: sensor.ble_temperature_a4c13818705a
on_value:
- then:
- lambda: !lambda |-
id(hp).set_remote_temperature(x);
disabled_by_default: false
force_update: false
accuracy_decimals: 1
state_class: ''
external_components:
- source: github://geoffdavis/esphome-mitsubishiheatpump
climate:
- platform: mitsubishi_heatpump
name: "${friendly_name}"
id: hp
# ESP32 only - change UART0 to UART1 or UART2 and remove the
# logging:baud_rate above to allow the built-in UART0 to function for
# logging.
hardware_uart: UART0
baud_rate: 2400
disabled_by_default: false
visual: {}
update_interval: 500ms
substitutions:
name: mitsubishi-hvac-livingroom
friendly_name: livingroom_HVAC Did some further digging and found several issues that I have tackled, resulting in a flawless operation for 2 days on 2 units.
1) Swap RX & TX lines. 2) revert back to 'nodemcu-32s' board and use level converters for RX & TX lines. 3) Disable web_server ( very important as it eats away necessary memory!! )
The web_server component creates a simple web server on the node that can be accessed through any browser and a simple [REST API](https://esphome.io/web-api/index.html). Please note that enabling this component will take up a lot of memory and can lead to problems, especially on the ESP8266.
Current YAML:
esphome:
name: ${name}
esp32:
board: nodemcu-32s
variant: ESP32
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: ${name}
password: !secret wifi_password
# Note: if upgrading from 1.x releases of esphome-mitsubishiheatpump, be sure
# to remove any old entries from the `libraries` and `includes` section.
#libraries:
# Remove reference to SwiCago/HeatPump
#includes:
# Remove reference to src/esphome-mitsubishiheatpump
captive_portal:
# Enable logging
logger:
level: NONE
# ESP8266 only - disable serial port logging, as the HeatPump component
# needs the sole hardware UART on the ESP8266
baud_rate: 0
#hardware_uart: UART1
# Enable Home Assistant API
api:
ota:
password: !secret 'esphome_api_password'
# 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: 60s
# You could use a Bluetooth temperature sensor
- platform: xiaomi_lywsdcgq
mac_address: "58:2D:34:3A:5B:F8"
humidity:
name: "LYWSDCGQ Humidity"
battery_level:
name: "LYWSDCGQ Battery Level"
temperature:
name: "LYWSDCGQ Temperature"
on_value:
then:
- lambda: !lambda |-
id(hp).set_remote_temperature(x);
esp32_ble_tracker:
external_components:
- source: github://geoffdavis/esphome-mitsubishiheatpump
climate:
- platform: mitsubishi_heatpump
name: "${friendly_name}"
id: hp
# ESP32 only - change UART0 to UART1 or UART2 and remove the
# logging:baud_rate above to allow the built-in UART0 to function for
# logging.
hardware_uart: UART0
baud_rate: 2400
disabled_by_default: false
visual: {}
update_interval: 500ms
uart:
tx_pin: 1
rx_pin: 3
baud_rate: 2400
rx_buffer_size: 512
button:
- platform: restart
name: Restart
entity_category: config
disabled_by_default: false
device_class: restart
- platform: shutdown
name: Shutdown
entity_category: config
disabled_by_default: false
icon: mdi:power
switch:
- platform: safe_mode
name: "Living Room Restart (Safe Mode)"
substitutions:
name: mitsubishi-hvac-livingroom
friendly_name: livingroom_HVAC
Andreastap
commented
2 years ago Hi Stendec1, I was inspired by your configuration but once sent these errors occur, how come you can help me ???
INFO Successfully compiled program. INFO Resolving IP address of mitsubishi-hvac-livingroom.local ERROR Error resolving IP address of mitsubishi-hvac-livingroom.local. Is it connected to WiFi? ERROR (If this error persists, please set a static IP address: https://esphome.io/components/wifi.html#manual-ips) ERROR Error resolving IP address: Error resolving address with mDNS: Did not respond. Maybe the device is offline., [Errno -5] No address associated with hostname
Stendec1
commented
2 years ago Hi @Andreastap, using DHCP with .local addresses gives problems sometimes, with me as well. I therefor have reverted to specify a fixed address in the yaml wifi section:
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: ${name}
password: !secret wifi_password
manual_ip:
# Set this to the IP of the ESP
static_ip: 192.168.XXX.XXX
# Set this to the IP address of the router. Often ends with .1
gateway: 192.168.XXX.XXX
# The subnet of the network. 255.255.255.0 works for most home networks.
subnet: 255.255.255.0
dns1: 192.168.XXX.XXX
dns2: 192.168.XXX.XXX
Give it a try.
MarkSmithAU
commented
2 years ago Has anyone ever got this to work with UART2 (ideally) or UART1 (soldering required on a nodemcu32)? It seems like it might be electrical (level shifter required) or there is a bug in the code that's not actually selecting the correct UART specified in the configuration?
geoffdavis
commented
2 years ago @MarkSmithAU The readme notes that you have to use a level shifter or a voltage divider. The mitsubishi board uses 5V TTL logic, while the ESP8266 and ESP32 use 3.3V TTL logic.
juan11perez
commented
2 years ago I was able to get standard ESP32 working with the above from @Stendec1. It's been running for a few days now without issue.
No level snifter. Just direct connection. This is my yaml.
# https://github.com/geoffdavis/esphome-mitsubishiheatpump
substitutions:
name: "entranceac"
friendly_name: entrance
esphome:
name: ${name}
# esp32:
# board: esp32dev
# framework:
# type: arduino
esp32:
board: nodemcu-32s
variant: ESP32
# Enable Home Assistant API
api:
ota:
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
use_address: ${name}
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Esphome-Web-145048"
password: "12345678"
captive_portal:
external_components:
- source: github://geoffdavis/esphome-mitsubishiheatpump
# Enable logging
logger:
# # ESP8266 only - disable serial port logging, as the HeatPump component
# # needs the sole hardware UART on the ESP8266
baud_rate: 0
# Enable Web server.
web_server:
port: 80
# MQTT
# mqtt:
# broker: 192.168.99.100
# port: 1883
# topic_prefix: ${name}
# username: !secret mqtt_username
# password: !secret mqtt_password
# 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: ${friendly_name} ESPHome Version
# Expose WiFi information as sensors.
- platform: wifi_info
ip_address:
name: ${friendly_name} IP
ssid:
name: ${friendly_name} SSID
bssid:
name: ${friendly_name} BSSID
# Sensors with general information.
sensor:
# Uptime sensor.
- platform: uptime
name: ${friendly_name} uptime
# WiFi Signal sensor.
- platform: wifi_signal
name: ${friendly_name} wifi signal
update_interval: 60s
# Or you could use a HomeAssistant sensor
# - platform: homeassistant
# name: "Temperature Sensor From Home Assistant"
# entity_id: sensor.master_temperature
# on_value:
# then:
# - lambda: 'id(${friendly_name}).set_remote_temperature(x);'
# - platform: xiaomi_lywsdcgq
# mac_address: "4C:65:A8:DD:72:4E"
# humidity:
# name: ${friendly_name} humidity
# battery_level:
# name: ${friendly_name} battery
# temperature:
# name: ${friendly_name} temperature
# on_value:
# then:
# - lambda: !lambda |-
# id(${friendly_name}).set_remote_temperature(x);
# https://esphome.io/components/esp32_ble_tracker.html
esp32_ble_tracker:
scan_parameters:
active: true
# https://esphome.io/components/bluetooth_proxy.html
bluetooth_proxy:
climate:
- platform: mitsubishi_heatpump
name: "${friendly_name}"
# ESP32 only - change UART0 to UART1 or UART2 and remove the
# logging:baud_rate above to allow the built-in UART0 to function for
# logging.
id: ${friendly_name}
visual:
min_temperature: 16
max_temperature: 31
temperature_step: 1.0
supports:
mode: [COOL, DRY, FAN_ONLY]
fan_mode: [AUTO, LOW, MEDIUM, HIGH]
swing_mode: ['OFF', VERTICAL]
hardware_uart: UART0
baud_rate: 2400
disabled_by_default: false
update_interval: 500ms
uart:
tx_pin: 1
rx_pin: 3
baud_rate: 2400
rx_buffer_size: 512
button:
- platform: restart
name: ${friendly_name} restart
entity_category: config
disabled_by_default: false
device_class: restart
id: entrance_restart
- platform: shutdown
name: ${friendly_name} shutdown
entity_category: config
disabled_by_default: false
icon: mdi:power
id: entrance_shutdown
# interval:
# - interval: 60s
# then:
# - wait_until:
# condition:
# wifi.connected:
# timeout: 8s
# - if:
# condition:
# wifi.connected:
# then:
# - switch.turn_off: blue_led
# else:
# - button.press: entrance_restart
switch:
- platform: gpio
id: blue_led
pin:
number: GPIO13
inverted: trueThe readme notes that you have to use a level shifter or a voltage divider. The mitsubishi board uses 5V TTL logic, while the ESP8266 and ESP32 use 3.3V TTL logic.
Thanks for Replying @geoffdavis . I did further research and found that UART2 is likely used by the SPI to access the flash and UART1 is broken - multiple threads on multiple forums. I ended up getting more appropriately sized esp8266 modules and they have worked flawlessly. It was not a level shift/voltage divider issue; I am using pullup resistors and removed an other inputs from the usb-serial chip on the board so they don't clash with the aircon's output which seems to be an open collector configuration.
geoffdavis
commented
1 year ago @MarkSmithAU wow, interesting.
I'm using the little cheesy ESP01S boards with a perf-board breakout, rather than any of the D1 mini or nodemcu style boards.
Hi
I'm trying to use this component with an ESP32 like this https://www.az-delivery.de/es/collections/mikrocontroller/products/esp32-d1-mini
Compilation and upload through ESPHome-Flasher is ok, but once uploaded the module is constantly rebooting
Here is an example of logs:
This is my ESPHome configuration file for this device:
Any Idea?
Thanks in advance!
NOTE: Same code with UART0 works in an ESP8266, obviously changing the type of board used