New ESP32 board : Unable to compile the configuration

pergola.fabio · June 16, 2023, 12:55pm

Hi, i have bought a new board, installed addon, installed cp210x driver as documented, i give it a name, enter my ssid + password, then i select the com6 port in chrome (usb) , but then receive error below? Its just a basic config with ssid + secrets? whats wrong with it? there are no logs being created ?

paddy0174 · June 16, 2023, 12:59pm

Config and logs? What you showed is exactly what we don’t need to help you here.

Post your config for that device and the corresponding log while you try to compile.

pergola.fabio · June 16, 2023, 12:59pm

When i do a “skip this step” and use USB to this computer, again no logs here?

why cant i upload a simple config?

pergola.fabio · June 16, 2023, 1:00pm

its the default config created by esphome addon itself, didnt change it yet

esphome:
  name: pool
  friendly_name: pool

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "xx"

ota:
  password: "xx"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Pool Fallback Hotspot"
    password: "xx"

captive_portal:

and in secrets

# Your Wi-Fi SSID and password
wifi_ssid: "mywifi"
wifi_password: "xx"

pergola.fabio · June 16, 2023, 1:02pm

and the file log_pool_compile.txt is just empty

pergola.fabio · June 16, 2023, 1:19pm

hmm, got it to work, when accessing my HA instance on DNS https:// … it doesnt work, when i use http:// local ip , then it works, seems the addon doesnt like https with ingress

pergola.fabio · June 16, 2023, 1:31pm

why doesnt it work or do anything if i’m connected to HA with my cloudflare dns? even the install button doesnt do anything, i need to access HA locally on ip

seems indeed a known issue with nginx

github.com/esphome/issues

ESPHOME and NGINX HA SSL proxy addon don't play nicely

opened 02:31PM - 04 Feb 20 UTC

closed 05:39PM - 23 May 21 UTC

dedepene

stale

**Operating environment/Installation (Hass.io/Docker/pip/etc.):**  hassio running on Ubuntu 18.04.2 LTS **ESP (ESP32/ESP8266, Board/Sonoff):**  **Affected component:**  **Description of problem:** This whole thing started when I installed the SSL proxy addon. Basically, if accessing HA via domain name and SSL ESPHome loads the web UI but whatever i click from there I get "terminated process" and nothing happens. If I reach the HA instance via local ip over http (no ssl) - it's all good. Getting these errors all the time: ``` 2020-02-04 16:10:28 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing. 2020-02-04 16:10:57 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing. 2020-02-04 16:11:03 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing. ``` ``` 20-02-04 14:00:07 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:09 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:13 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:15 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:19 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:21 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:25 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:27 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:31 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:33 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:37 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:39 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:43 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:45 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:49 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:51 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:55 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:00:57 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:01:01 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:01:03 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace 20-02-04 14:01:07 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status', url='http://172.30.32.1:62520/ace ``` from the ESPHOME addon log: ``` WARNING 403 GET /ace (0.0.0.0) 3.11ms WARNING 403 GET /ace (0.0.0.0) 2.01ms WARNING 403 GET /ace (0.0.0.0) 2.61ms WARNING 403 GET /ace (0.0.0.0) 1.50ms WARNING 403 GET /ace (0.0.0.0) 1.81ms WARNING 403 GET /ace (0.0.0.0) 2.45ms ``` **Problem-relevant YAML-configuration entries:** ```yaml PASTE YAML FILE HERE ``` **Logs (if applicable):**  ``` PASTE DEBUG LOG HERE ``` **Additional information and things you've tried:**

github.com/esphome/issues

Ingress is not working in rev 1.13.x

opened 08:18AM - 01 Jun 19 UTC

ppmt

Project: Home Assistant Addon

**Operating environment/Installation (Hass.io/Docker/pip/etc.):** Hass.io Ad…d-on: ESPHome ESPHome Hass.io add-on for intelligently managing all your ESP8266/ESP32 devices. Add-on version: 1.13.2 You are running the latest version of this add-on. System: null (amd64 / qemux86-64) Home Assistant version: 0.93.2 Supervisor version: 165 **ESP (ESP32/ESP8266, Board/Sonoff):** ESP32 Webcam (AI-thinker) ESP32 Dev kits **Affected component:** Can't access webui via ingress **Description of problem:** Since the upgrade from 1.12.2 to 1.13.1 and after activating ingress I can no longer see the logs or compile my ESP modules. Instead I get some errors in the addon logs: WARNING 403 GET /ace (0.0.0.0) 2.93ms WARNING 403 GET /ace (0.0.0.0) 1.90ms WARNING 403 GET /ace (0.0.0.0) 1.74ms WARNING 403 GET /ace (0.0.0.0) 1.72ms WARNING 403 GET /ace (0.0.0.0) 1.64ms WARNING 403 GET /ace (0.0.0.0) 1.62ms WARNING 403 GET /ace (0.0.0.0) 2.74ms WARNING 403 GET /ace (0.0.0.0) 8.31ms **Problem-relevant YAML-configuration entries:** no problem with yaml configuration **Traceback (if applicable):** n/a **Additional information and things you've tried:** The workaround is to reactivate port 6052 in the addon and to use it rather than the ingress links. Thank you to user CBRHerms from the HA community. [Link to relevant HA community post](https://community.home-assistant.io/t/cant-upload-firmware-since-v1-13-1/119490)