ESPHome on wemos D1 mini lite losing its brains

Hi All,

I have many ESPHome devices all over my house that have been working flawlessly for years… except one.

The one that monitors my doorbell, a PIR sensor and a DS18S20 temperature sensor loses it’s brains every few weeks. Just resetting it doesn’t bring it back. It needs to be reflashed over USB.

At first I thought it was the inductive kick from the doorbell coil, but I finally got around to testing for this, and I can’t find any signs that thats a problem.

I also think it probably lost it’s brains at least once when there were no button presses, but I can’t guarantee that.

I’m going to try reinstating it without the doorbell button connected at all and see what happens, but since it can be weeks before it dies, it’s worth asking the question;

Has anyone seen this problem before that ESPHome can brick itself?

Code below:

esphome:
  name: doorbell
  platform: ESP8266
  board: esp8285

wifi:
  ssid: '#######'
  password: '#######'

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

binary_sensor:
  - platform: gpio
    name: "button"
    pin:
      number: GPIO16
      inverted: True
      #mode: INPUT_PULLUP

  - platform: gpio
    name: "Doorbell"
    pin:
      number: GPIO4
      inverted: False
      #mode: INPUT_PULLUP
  - platform: gpio

    name: "PIR Entry"
    pin:
      number: GPIO0
      inverted: True
      #mode: INPUT_PULLUP


switch:
  - platform: gpio
    pin:
        number: GPIO15
    restore_mode: RESTORE_DEFAULT_OFF
    name: "Spare Output"

dallas:
  - pin: GPIO13

sensor:
  - platform: adc
    pin: A0
    name: "Doorbell Battery"
    update_interval: 60s

  - platform: dallas
    index: 0
    name: "Hallway Temperature"

Could just be bad flash memory on the ESP chip. Do you have another ESP board to try?

I have one of my Wemos D1 Mini’s which recently started dropping off the network / reconnecting every few minutes, constantly. I’ve re-flashed it multiple times via USB (because it doesn’t stay online long enough for OTA) but that hasn’t fixed it. Luckily they are cheap so I’ll soon swap it for a new one. Not sure what the cause was although it seemed to happen exactly when I added my second wifi AP… guessing a strange coincidence.

That’s a good point. I do have spares, so it’s an easy thing to try. But in a deployment of more than 130 others from the same batch (not running esphome) I’ve never seen the behaviour before.