ESP8285 won't connect to wifi since last update

landolfi · March 20, 2026, 5:23pm

Not sure where to go with this, but 1 ESP8285 that worked before the last ESPHome Builder update and another spare, new ESP8285 accept the YAML that previously worked on Device 1 but, neither Device 1 nor 2 will connect to wifi now. I am hesitant to update the other working ESP8285s I have for fear it will also cause them to stop working. Although install via USB TTL works on both devices, neither will connect to wifi after and there is nothing in the log output even when connected via cable. I also tried installing via USB TTL using the web interface to “Prepare for first use”. That gave me the error: “Improv Wi-Fi serial not detected” after the install allegedly succeeded.

Here is the previously working YAML:

esphome:
  name: "ir-remote-1"
  friendly_name: "ir-remote-1"
esp8266:
    board: esp01_1m
# Enable logging
logger:
  level: VERY_VERBOSE
# Enable Home Assistant API
api:
  encryption:
    key: !secret esphome_encryption_key
ota:
  - platform: esphome
    password: "6b157bcfdf170a4fc6a8e8cf9f9ea45d"
web_server:
  port: 80
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  reboot_timeout: 0s
  min_auth_mode: WPA2
  manual_ip:
    static_ip: 192.168.1.179
    gateway: 192.168.1.1
    subnet: 255.255.255.0
# Skips channel scanning for faster reconnection
  fast_connect: True
  # Prevents the ESP from going to sleep and missing signals
  power_save_mode: none
  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Remote1"
    password: "8charact3rs!"
captive_portal:
remote_receiver:
  pin:
    number: GPIO14
    inverted: true
  dump: all
binary_sensor:
  - platform: remote_receiver
    name: "Audio refresh"
    panasonic:
      address: 0x2A4C
      command: 0x0280E466
remote_transmitter:
  pin:
    number: GPIO4
  carrier_duty_percent: 50%
button:
  - platform: template
    name: "Denon Power"
    on_press:
      - remote_transmitter.transmit_pronto:
          data: 0000 006D 000D 0000 005D 0016 002E 0016 0017 0017 002F 0018 0016 0017 002E 0016 0018 0017 0016 0018 002D 0017 0017 0019 0016 0018 0017 0017 0016 0181
          repeat:
              times: 5
              wait_time: 10ms
  - platform: template
    name: "Sony Power"
    on_press:
#      - remote_transmitter.transmit_pronto:
#          data: 00000 0070 0000 0032 0080 0040 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0ACD 
       - remote_transmitter.transmit_sony:
           data: 0x00000A90
           nbits: 12
           repeat:
              times: 3
              wait_time: 40ms
  - platform: template
    name: "Denon Mute"
    on_press: 
      - remote_transmitter.transmit_pronto: 
          data: 0000 0070 0000 0032 0080 0040 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0010 0010 0030 0010 0030 0010 0030 0010 0010 0010 0ACD 
          repeat:
              times: 5
              wait_time: 10ms
  - platform: template
    name: "E28 Power"
    on_press:
      - remote_transmitter.transmit_pronto:
          data: 0000 006D 0022 0000 015D 00AD 0015 0017 0015 0041 0015 0041 0015 0041 0015 0017 0015 0041 0015 0041 0015 0041 0015 0041 0015 0042 0014 0041 0015 0018 0014 0018 0014 0018 0014 0018 0014 0041 0015 0018 0014 0018 0014 0042 0014 0042 0014 0042 0014 0018 0014 0042 0014 0018 0014 0018 0014 0018 0014 0018 0014 0018 0014 0042 0014 0042 0014 0042 0014 0018 0014 0181
          repeat:
              times: 5
              wait_time: 10ms
  - platform: template
    name: "Samsung Power"
    on_press: 
      - remote_transmitter.transmit_samsung:
          data: 0xE0E040BF
          nbits: 32
          repeat:
            times: 3
            wait_time: 40ms

neel-m · March 20, 2026, 8:13pm

There is literally no log output, or nothing you think is important?

If there is literally no log output that seems very bad.

If it was mine, I would connect it to a PC running a terminal emulator (putty or teraterm) so I could see the USB serial output from at least the boot loader.

You have a static IP address. Some people like them. I do not. I do have a router that let’s me assign the same address to particular devices. With static IPs assigned by the device it is too easy to get two that have the same address, which rarely works well.

bdraco · March 20, 2026, 10:07pm

landolfi · March 21, 2026, 2:33am

Great idea to connect via serial–On Board 2 I saw a bunch of attempts to correct to my network and lots of “wifi took a long time for an operation (XXms), max is 30ms”. The main reason I had a static IP is I have an ASUS mesh network and each of these devices is located near the “seam” of the coverage areas, so they were constantly having trouble connecting to wifi and maintaining the connection with a dynamic IP.

Anyway, Board 2 now works. I wasted a lot of time because these ESP8285 boards seem to need a strong wifi signal, I was spinning my wheels until I decided to move it closer to the main router, at which time I was able to initialize it, then copy and paste the old device YAML to a new uniquely named device, and then it all worked. I also wasted a lot of time trying to re-use the name ir-remote-1, which seems to have been the cause of the “ESPHome encryption key is invalid” error I was gettting. So moral of the story seems to be: When replacing an ESP8285, make sure you have a solid wifi signal in your setup location and don’t try to re-use a previously used device name. Instead, set up a new device with a unique name and then copy and paste the YAML from the old device.

As for Board 1, I think I may have damaged it when I first got it through some bad TTL connections and the latest update caused it to finally fail.

Thanks for the suggestions.

neel-m · March 21, 2026, 4:38am

Glad you figured out the issue.

Nick4 · March 22, 2026, 9:49am

Hi, good that it got solved!

Also: please take the time to mark the post that holds the solution.
You do that by selecting the three dots under the post:

Then select the check box:

By doing so:

this thread can be useful to other users as well (this thread comes up as solution when starting a thread which is similar to yours).
this prevents that someone else steps in trying to help

Thanks for giving back to the community!

landolfi · March 22, 2026, 12:43pm

UPDATE: I was also able to get allegedly DOA Board 1 working using the same process. So this seems to be how to install or replace an ESP8285 using ESPHome if your install location has a dicey wifi signal:

If the board you are setting up already exists, delete the original board from ESPHome.
Give the board a unique name. If you are replacing one, do not re-use the same name you used for the one you deleted.
Prepare the board using the ESPHome new device setup option and install with direct cable connection. After setup is complete, ignore message saying that the board was installed but couldn’t be connected to over the network.
Move the newly set up board to a strong wifi signal location. Board will connect to wifi.
Edit new board’s YAML as desired.
Install wirelessly.