As per title. HA Supervised, Debian, PI 4, everything supported.
Wireless updates start and stop silently/fail during compiling (“Compiling .pioenvs/…”) without any warning/error, other than a button “retry” appearing on bottom right. I download logs, which just stop at the exact time of failure (logger level: DEBUG) without any warning and/or error. YAML validates and is/was always correct.
The funny thing is that nodes can be updated sucessfully via “Settings” of HA dashboard (when there is an update), so there must be something off with the addon itself.
Uninstalled and reinstalled ESPHome addon without fixing the issue.
Any thoughts?
How much memory your system have? By accident only 1GB?
Might be that the verbose
output from the add on is filling up the memory till death?
Did you try adding a process_limit
already to your yaml?
esphome:
...
compile_process_limit: 1
4GB
I have it on DEBUG (like always, never had an issue).
I’ll try it, but: a) Never had an issue in the past, b) the update should fail through HA settings too, if that were the culprit.
hence
But with 4GB of RAM their should be no problem at all if it isn’t filled up?

I have it on DEBUG (like always, never had an issue).
Not the logging from a esphome node but the log output from compiling is what I intended to say.
In any case what does the esphome add on log tells us?
These were my initial thoughts too, but it’s not that. ESPHome logs are almost empty, RAM is ok.
But I’ve made some progress: For some weird reason updates are succesfull when I connect to HA and ESPHome addon through local address (192.168…). The problem appears when I connect to HA and ESPHome through NginxProxyManager and a local address (homeassistant.john.local). But I’m not confident yet, I’m doing some tests. Normally this should’t matter at all, I don’t get it…And I didn’t change a thing in my configurarion in relation to that.