EPOL not booting properly after recent update

[xkoldxx]

After a recent ESPHome update my EPOL has stop booting

[12:04:50]abort() was called at PC 0x401be656 on core 0
[12:04:50]
[12:04:50]
[12:04:50]Backtrace: 0x400830ce:0x3ffe62f0 0x4009240d:0x3ffe6310 0x400985c2:0x3ffe6330 0x401be656:0x3ffe63a0 0x401bd203:0x3ffe63c0 0x401bd16a:0x3ffe63e0 0x400de631:0x3ffe6400 0x400fc399:0x3ffe6420 0x400fcd51:0x3ffe6440 0x40125dea:0x3ffe6460 0x40125d87:0x3ffe6480
[12:04:50]
[12:04:50]
[12:04:50]
[12:04:50]
[12:04:50]ELF file SHA256: d6a3b1bdac8b12b3
[12:04:50]
[12:04:50]Rebooting...

[EverythingSmartHome]

Do you happen to have internet blocked on the device?

[xkoldxx]

double checked my fw rules and no there is access to the internet on my IOT netowrk

[EverythingSmartHome]

Can you try connecting it to the main SSID just to confirm? There is a bug in ESPHome that causes a boot loop like this when it can't reach GitHub

[xkoldxx]

i just migrated to the main network - still the same issue

[EverythingSmartHome]

Can you flash from the user guide again to check it works?

[xkoldxx]

I have flashed it from there several times

• i even got a replacement sensor and still didnt work

Heres my current cfg

substitutions:
name: "office-epol-sensor"
friendly_name: Office EPOL Sensor
packages:
EverythingSmartTechnology.Everything_Presence_Lite: github://everythingsmarthome/everything-presence-lite/everything-presence-lite-ha.yaml@main

esphome:
name: ${name}
name_add_mac_suffix: false
friendly_name: ${friendly_name}
api:
encryption:
key: **************

wifi:
ssid: !secret main_wifi_ssid
password: !secret main_wifi_password

mdns:

[EverythingSmartHome]

Which version are you flashing?

[xkoldxx]

version of EPL or ESPHome? EPL your site said 1.10 i think HA ESPHome didnt state but im running latest

…

On Fri, Sep 20, 2024 at 1:40 PM Everything Smart Home < ***@***.***> wrote: Which version are you flashing? — Reply to this email directly, view it on GitHub <#170 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKGGQZJX3Q3MKGJ3ICROKCTZXSB3DAVCNFSM6AAAAABOSWHFXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGU4DMMBRHE> . You are receiving this because you authored the thread.Message ID: ***@***.*** .com>

-- Sincerely, James Kirkpatrick

[EverythingSmartHome]

No I mean Bluetooth or non bluetooth?

[xkoldxx]

I run it with BLE but today I tried without but same error James Kirkpatrick

…

On Mon, Sep 23, 2024 at 12:16 Everything Smart Home < ***@***.***> wrote: No I mean Bluetooth or non bluetooth? — Reply to this email directly, view it on GitHub <#170 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKGGQZJRY3HQGB2E2A5IKITZYBSH5AVCNFSM6AAAAABOSWHFXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRZGE2TONBVGQ> . You are receiving this because you authored the thread.Message ID: ***@***.*** .com>

[EverythingSmartHome]

Can you post the startup logs from the device in full?

[xkoldxx]

[
office-epol-sensor_logs (1).txt
](url)

[xkoldxx]

office-epol-sensor_logs (1).txt

[EverythingSmartHome]

It looks like internet is blocked in some way, there is an unfortunate bug in ESPHome that will cause a loop like this when internet is blocked and the device tries to check for updates on GitHub

[xkoldxx]

What makes you say that this is the only esp device that doesn’t work I onboarded 6 new esp devices today no issues My opnsense firewall allows my IOT to iNet James Kirkpatrick

…

On Mon, Oct 28, 2024 at 17:53 Everything Smart Home < ***@***.***> wrote: It looks like internet is blocked in some way, there is an unfortunate bug in ESPHome that will cause a loop like this when internet is blocked and the device tries to check for updates on GitHub — Reply to this email directly, view it on GitHub <#170 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKGGQZPMQU5HY2O4DE72IB3Z53FAFAVCNFSM6AAAAABOSWHFXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBSHE2DOMZUGM> . You are receiving this because you authored the thread.Message ID: ***@***.*** .com>

[EverythingSmartHome]

It only applies to devices that use the mew manufacturer updates components, most other devices don't.

It doesn't need to just be a firewall rule, it could be a misconfigured primary DNS server