#esphome - devices going unavailable after flash

2 messages · Page 1 of 1 (latest)

cunning haven
#

Hi. I have a number of ESP8266s connected to my heat pumps and using this firmware: https://github.com/echavet/MitsubishiCN105ESPHome

So far, so good. They've been reliably operating since I set them up last month. This morning, I needed to add something to the YAML of one device, and used ESPHome to flash the device wirelessly. Suddenly, the device keeps going unavailable every couple minutes, making the HVAC controls nearly unusable.

I've been trying various troubleshooting steps. I tried updating all devices and now every device, even ones with completely unmodified YAMLs, are throwing this error:

WARNING hp-sun @ 192.168.1.171: Connection error occurred: [Errno 104] Connection reset by peer INFO Processing unexpected disconnect from ESPHome API for hp-sun @ 192.168.1.171 WARNING Disconnected from API WARNING Can't connect to ESPHome API for hp-sun @ 192.168.1.171: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.171', port=6053))]: [Errno 111] Connect call failed ('192.168.1.171', 6053) (SocketAPIError) INFO Trying to connect to hp-sun @ 192.168.1.171 in the background

My nice HVAC setup has been reduced to its knees. Help!

GitHub

ESPHome firmware inspired by GeoffDavis’s esphome-mitsubishiheatpump, directly integrating the SwiCago library within its codebase. - echavet/MitsubishiCN105ESPHome

#

I'll add that the devices are still showing as "online" in the ESPHome add-in and in my router.