Lcd_gpio seems to break ESPHome api connection

ESPHome
1

I’m using the same code with not much changes since few months. It seems after recent ESPHome update to 2024.11.3 and I uploaded an updated code, it breaks api connection and my display shows gibberish.
I dig down to the problem with lcd_gpio section. I add this code snippet, api breaks, I remove this, everything works.

esp8266:
  board: nodemcuv2
display:
  - platform: lcd_gpio
    data_pins: 
      - GPIO13
      - GPIO12
      - GPIO14
      - GPIO16
    dimensions: 16x2
    enable_pin: GPIO15
    rs_pin: GPIO0

dashboard logs shows like:

INFO ESPHome 2024.11.3
INFO Reading configuration /config/esphome/pmpctrl.yaml...
INFO Detected timezone 'Asia/Calcutta'
INFO Starting log output from 10.182.39.158 using esphome API
WARNING Can't connect to ESPHome API for pmpctrl @ 10.182.39.158: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='10.182.39.158', port=6053))]: [Errno 111] Connect call failed ('10.182.39.158', 6053) (SocketAPIError)
INFO Trying to connect to pmpctrl @ 10.182.39.158 in the background

I see the device gets ip and I can ping the device too.

Any one any clue please?

2

This looks suspicious.
GPIO 0 is not a great pin to use

3

may be you are right. But I can say, same config was working since last few months without issue. I had to use this since I was out of pin.
And, as you said, I tried with GPIO5, GPIO4. NO LUCK…!!!
I tried going back to esphome 2024.8.x. Same issue.
Now I doubt it may be broken from HA end.

4

Not sure why, but this trick worked - ESP32 Logs & Connection to Home Assistant/ESPHome don't work when `lcd_gpio` display device is defined · Issue #5469 · esphome/issues · GitHub
I already had lambda earlier too, but dont know why it broke meantime. Set everything up, and I have an working code. Fingers crossed.!