I started mucking about with ESPHome yesterday and setup a WROOM with an AHT22 temp/humidity sensor. Running the wizard and adding the configs is easy-peasy. I started to have issues as soon as I wanted to flash.

  • If the AHT22 is plugged in, I cannot flash the device over USB.
  • I can check the serial logs once the device is flashed and then plug in the AHT22 once the device is booted and get readings, but
  • Once I unplug the ESP32 from the serial port and plug it into a power supply, I got nothing. No network activity at all.
  • Unplug the AHT22, plug into the power source, wait a few seconds, plug in the AHT22 has seemed to work correctly this morning and HA is pulling data but I tried that last night a few times and it didn’t work – so unsure why it’s working this morning other than strange timing when I’m plugging the thing back in.

I am using the basic esp32dev firmware, which I am assuming works because it DOES work, eventually, but I’m not confident I’m using the right base but I cannot figure out which one to use.

  • CondorWonder
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 months ago

    Make sure you’re not using any of the strapping pins for the interface with the AHT22 - take a look at https://esp32.com/viewtopic.php?t=5970 for a read. It basically means leaving GPIOs 12, 0, 2, 4, 15, 5 floating during boot or the esp will not boot correctly.

    These pins control the boot process (like going to the boot loader instead of your code).

    • Aniki 🌱🌿@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      5 months ago

      Patched, flashed, and didn’t crash! That also explains why WLED project switched to pin 18 or whatever by default. This is a huge fix and I really appreciate it!

    • Aniki 🌱🌿@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      3
      ·
      5 months ago

      I think you nailed it. It explains both the issues flashing and booting. I’ll have to muck about with other pins and see if that fixes it.