search

esphome / firmware

Holds firmware configuration files for projects that the ESPHome team provides.
https://esphome.io/projects
Apache License 2.0
158 stars 121 forks source link

abort after esp-x509-crt-bundle: Certificate validated #275

Open lukebarton opened 1 day ago

lukebarton commented 1 day ago

I'm an ESPHome noob but I've recently been working with ESP32 devices.

I have been using some bare ESP32 devices and some Everything Presence Lite ESP32 devices.

On the bare ESP32 devices, I had issues with the Bluetooth Proxy Ready-Made Project aborting (which may be related to https://github.com/esphome/firmware/issues/228). Some devices would be fine, some would constantly abort. I only worked around this by flashing directly from the ESPHome HA addon and then adding bluetooth_proxy: to the bare bones YAML. Whatever - it worked.

Now, one of my Everything Presence devices seems to be afflicted by the same issue. It's just constantly aborting immediately after the wifi connects. Live update: I just restarted my other Everything Presence device and it's now stuck in the same cycle. I haven't restarted these devices in a while.

[D][esp-idf:000][sys_evt]: I (6799) esp_netif_handlers: sta ip: 10.0.50.91, mask: 255.255.255.0, gw: 10.0.50.1

[I][wifi:617]: WiFi Connected!
[C][wifi:428]:   Local MAC: 10:06:1C:77:BA:20
[C][wifi:433]:   SSID: [redacted]
[C][wifi:436]:   IP Address: 10.0.50.91
[C][wifi:440]:   BSSID: [redacted]
[C][wifi:441]:   Hostname: 'everything-presence-lite-77ba20'
[C][wifi:443]:   Signal strength: -40 dB ▂▄▆█
[C][wifi:447]:   Channel: 1
[C][wifi:448]:   Subnet: 255.255.255.0
[C][wifi:449]:   Gateway: 10.0.50.1
[C][wifi:450]:   DNS1: 10.0.50.1
[C][wifi:451]:   DNS2: 0.0.0.0
[C][api:025]: Setting up Home Assistant API server...
[D][button:010]: 'get_mmwave_firmware' Pressed.
[D][switch:012]: 'mmWave Configuration Mode' Turning ON.
[I][app:062]: setup() finished successfully!
[D][esp-idf:000][wifi]: I (6932) wifi:
[D][esp-idf:000][wifi]: <ba-add>idx:1 (ifx:0, b6:8b:a9:43:be:7a), tid:6, ssn:2, winSize:64
[D][esp-idf:000][wifi]: 

[D][esp-idf:000]: I (7221) esp-x509-crt-bundle: Certificate validated

abort() was called at PC 0x401b6292 on core 0

Backtrace: 0x400830ce:0x3ffe6740 0x4009240d:0x3ffe6760 0x400985c2:0x3ffe6780 0x401b6292:0x3ffe67f0 0x401b4e3f:0x3ffe6810 0x401b4da6:0x3ffe6830 0x400dde6d:0x3ffe6850 0x400f9d7d:0x3ffe6870 0x400fa735:0x3ffe6890 0x40123b6a:0x3ffe68b0 0x40123b07:0x3ffe68d0

This was the same issue I was running into with the bare ESP32s w/ the Ready-Made BT Proxy firmware.

So it appears to me that the Ready-Made BT Proxy firmware and Everything Presence Lite firmware's share something in common that is causing this abort. What is not clear to me whether it's something related to my local network that's causing the issue.

Thoughts: It happens immediately after this certificate is validated. Is the abort related to the certificate? What certificate is being validated here - is it an external cert? If so, why might an external cert cause two separate ESPHome firmwares to abort with the same problem?

Any assistance appreciated.

lukebarton commented 1 day ago

And 30 minutes later, they're suddenly able to successfully boot again. Internet connectivity has been uninterrupted, but clearly something is bothering these ESP32 devices.