Open catgiggle opened 1 year ago
I have similar issues to the above on the same device with OTA update, I was on Tasmota, converted perfectly fine to ESP Home but needed to change a couple of things in the YAML.
OTA update fails, it says OTA Update in Progress 0.1% then you get an error500 on the deviceip/update page a few seconds later. Tried manual flash as well as through the ESP Home dashboard wirelessly.
I am going to flash manually on it's pins to work around it, but has anybody worked this out?
My YAML for info (wifi and security key sections removed)
esphome: name: sw01-kitchen friendly_name: KITCHEN
esp32: board: esp32dev framework: type: arduino
web_server: port: 80
BL0939 Power Monitoring Configuration Disable logging over serial logger: baud_rate: 0
uart: tx_pin: GPIO25 rx_pin: GPIO26 baud_rate: 4800 parity: NONE stop_bits: 2
sensor:
BL0939 Sensors platform: bl0939 update_interval: 30s voltage: name: 'Input Voltage' current_1: name: 'Relay Current 1' current_2: name: 'Relay Current 2' active_power_1: name: 'Relay Active Power 1' active_power_2: name: 'Relay Active Power 2' energy_1: name: 'Relay Energy 1' energy_2: name: 'Relay Energy 2' energy_total: name: 'Relay Energy Total' Misc Sensors platform: wifi_signal name: "WiFi Signal" update_interval: 30s platform: uptime name: "Device Uptime" update_interval: 120s Relay Configuration Port 1 WASHINGMACHINE Port 2 TUMBLEDRYER binary_sensor:
platform: gpio pin: number: GPIO00 mode: INPUT_PULLUP inverted: True name: "button0"
on_press: switch.toggle: relay switch.toggle: relay2 platform: gpio pin: number: GPIO32 mode: INPUT_PULLUP inverted: True name: "button1"
on_press: switch.toggle: relay platform: gpio pin: number: GPIO33 mode: INPUT_PULLUP inverted: True name: "button2"
on_press: switch.toggle: relay2 switch:
platform: gpio name: "WASHING MACHINE" pin: GPIO27 id: relay platform: gpio name: "TUMBLE DRYER & DISHWASHER" pin: GPIO14 id: relay2 platform: restart name: "Restart Device" status_led: pin: number: GPIO13 inverted: yes
text_sensor:
platform: version name: "Version"
Update...
So I flashed ESP Home directly on, no change from the above config really just changed a name to make a difference, flashed perfectly!
Only thing I can think of is it is something to do with migrating from Tasmota to ESP Home originally, all I did to go to ESP Home was a manual install binary, then used Tasmota firmware upgrade like I have done loads of times on my non ESP32 devices.
Device history...
Originally I flashed from the default Sonoff firmware to Tasmota (flashed using serial interface not DIY mode). I migrated from Tasmota to ESP Home after it had been running fine for several weeks. This time around I flashed the ESPHome binary directly over serial and it worked from both the update button AND the dashboard updating.
Problem solved for me, so might be useful if anybody else encounters it.
The problem
I have an issue with updating my Sonoff Dual R3 via OTA. Firstly, I created a YAML configuration (below) and tried to flash it to the Dual R3 through USB and ESPhome Web, but without success. Therefore, I compiled the configuration to a Legacy BIN file (Install > Manual download > Legacy format) and then initialized the Dual R3 through Tasmota Installer (https://tasmota.github.io/install/) and updated the firmware through the interface provided by the device (http://192.168.4.1/up) to EspHome (I uploaded the Legacy BIN file). Up to this point, the Dual R3 is working correctly, showing up in Home Assistant, providing the button and sensor according to the YAML configuration. However, when I try to update the firmware via OTA, it only causes the Dual R3 to restart (log below).
I am using ESPhome run through Docker from the official image (https://hub.docker.com/r/esphome/esphome). It's worth noting that I have many other devices and do not have any problems with updating via OTA. However, this is my first device on ESP32.
Which version of ESPHome has the issue?
2023.2.2
What type of installation are you using?
Docker
Which version of Home Assistant has the issue?
2022.11.5
What platform are you using?
ESP32
Board
esp32dev
Component causing the issue
ota
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response