No connection to Wi-Fi and no services exposed after unrelated YAML configuration change

[wsw70]

Operating environment/Installation (Hass.io/Docker/pip/etc.):

ESPHome dashboard running in a docker container:

esphome:
    container_name: esphome
    image: esphome/esphome
    volumes:
      - /etc/docker/data/esphome:/config
    network_mode: host

ESP (ESP32/ESP8266, Board/Sonoff):

Sonoff Basic

ESPHome version (latest production, beta, dev branch)

1.14.5

Affected component:

The TCP/IP stack

Description of problem:

I have many identical Sonoff Basic running with the following configuration (this is the output from the validate function on the dashboard which seem to represent the complete configuration compiled in (MYDOMAIN and MYPASSWORD are redacted):

INFO Reading configuration /config/switch02.yaml...
INFO Detected timezone 'CET' with UTC offset 1 and daylight savings time from 28 March 02:00:00 to 31 October 03:00:00
INFO Configuration is valid!
substitutions:
  name: switch02
esphome:
  name: switch02
  platform: ESP8266
  board: esp8285
  includes: []
  esp8266_restore_from_flash: false
  board_flash_mode: dout
  platformio_options: {}
  build_path: switch02
  libraries: []
  arduino_version: espressif8266@2.2.3
binary_sensor:
- platform: gpio
  pin:
    number: 0
    mode: INPUT_PULLUP
    inverted: true
  name: switch02
  on_press:
  - then:
    - switch.toggle:
        id: relay
switch:
- platform: gpio
  name: switch02
  pin:
    number: 12
    inverted: false
    mode: OUTPUT
  id: relay
  interlock_wait_time: 0ms
  restore_mode: RESTORE_DEFAULT_OFF
status_led:
  pin:
    number: 13
    inverted: true
    mode: OUTPUT
sensor:
- platform: wifi_signal
  name: switch02
  update_interval: 60s
  force_update: false
  unit_of_measurement: dB
  accuracy_decimals: 0
  icon: mdi:wifi
wifi:
  domain: .MYDOMAIN
  ap:
    ssid: switch02
    password: MYPASSWORD
    ap_timeout: 1min
  output_power: 20.0
  power_save_mode: NONE
  reboot_timeout: 15min
  fast_connect: false
  networks:
  - ssid: WUSR
    password: MYPASSWORD
    priority: 0.0
  use_address: switch02.MYDOMAIN
captive_portal: {}
logger:
  esp8266_store_log_strings_in_flash: true
  hardware_uart: UART0
  baud_rate: 115200
  logs: {}
  level: DEBUG
  tx_buffer_size: 512
ota:
  safe_mode: true
  port: 8266
  password: ''
time:
- platform: sntp
  servers:
  - 192.168.10.1
  timezone: CET-1CEST-2,M3.4.0/2,M10.5.0/3
api:
  port: 6053
  reboot_timeout: 15min
  password: ''

I wanted to add the following configuration to a test switch

text_sensor:
  - platform: version
    name: "ESPHome version"
  - platform: template
    name: "Configuration version"
    lambda: |-
      return {"1"};

After compilation (though the dashboard) and successful upload, the Sonoff

• refuses to connect to the WiFi
• the LED is blinking
• it reacts to the mechanical push of its button

After a moment the fallback AP fires up and

• I can connect to it from my laptop, I receive the 192.168.4.2 IP address
• and that's all, none of the ports on the Sonoff are available

Note that this specific test device also had web_server: in its configuration (the config dump above is from another device, configured exactly the same way except for that specific entry - I use multi-layered configuration files), so I would expect to see at least ports 80, 6053 and 8266 to be available. They are not.

I am opening this bug report because I saw several other discussions about some unexpected YAML changes (not related to networking but for instance to logger:) impacting the ability to connect to the Wi-Fi.

I will reflash my device with the previous settings, and then with the new ones (with text_sensor) and see how it goes.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[wsw70]

It seems that others have the same issue: https://www.reddit.com/r/homeautomation/comments/kcbaik/is_esphome_v_1152_or_1153_with_web_server/

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.