Closed patrickwieth closed 10 months ago
same here just a bit different:
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash - framework-espidf @ 3.40405.230623 (4.4.5) - tool-cmake @ 3.16.4 - tool-ninja @ 1.7.1 - toolchain-esp32ulp @ 2.35.0-20220830 - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5 Reading CMake configuration... Dependency Graph |-- ArduinoJson @ 6.18.5 *** [.pioenvs/nspan/src/esphome/components/http_request/http_request.o] Source src/esphome/components/http_request/http_request.cpp' not found, needed by target
.pioenvs/nspan/src/esphome/components/http_request/http_request.o'. ========================== [FAILED] Took 6.00 seconds ==========================
xtensa-esp32-elf-g++: fatal error: Killed signal terminated program cc1plus compilation terminated. *** [.pioenvs/bueropanel/src/main.o] Error 1
Sounds like the compiler is crashing.
Please try adding this to your yaml:
# Limit the amount of resources used for compiling
esphome:
compile_process_limit: 1
Then try to compile again and let me know the results. If you are running ESPHome as an add-on to Home Assistant, try restarting the host system and stopping other add-ons temporarily, as this will free-up resources to ESPHome.
By the way, I believe this is more related to a ESPHome version that you might have changed than related to a version of our product, as we don't had that big change with the release earlier today, but if you wanna try an older version, just change in your remote_packages
area, from ref: main
to ref: v4.1.4
which was the version since earlier December until a few hours ago.
@edwardtfn just ran into the same issue but sadly limiting the compile process did not help
i'm running esphome as standalone docker container esphome version: 2023.12.5
my error
*** [.pioenvs/nspanel/src/esphome/components/http_request/http_request.o] Source `src/esphome/components/http_request/http_request.cpp' not found, needed by target `.pioenvs/nspanel/src/esphome/components/http_request/http_request.o'.
@edwardtfn with the ref set to the v4.1.4 tag its working
set to v4.2 is not working as expected
@tech2mar do you have also the esp-idf framework?
esp32:
framework:
type: esp-idf
@edwardtfn maybe its related to the framework used here?
Did you try to 'clean build files'?
@tech2mar do you have also the esp-idf framework?
esp32: framework: type: esp-idf
@edwardtfn maybe its related to the framework used here?
Yes.
Did you try to 'clean build files'?
No
Did you try to 'clean build files'?
awesome.. that did the trick
can this please be added to the "update instructions"?
Did you try to 'clean build files'?
That fixed the compiler crash.
Did you try to 'clean build files'?
Good point. That should be my first question next time. 😉
@patrickwieth, could you please confirm if that solved the issue in your case?
Did you try to 'clean build files'?
Good point. That should be my first question next time. 😉
@patrickwieth, could you please confirm if that solved the issue in your case?
Sadly it does not, I have also tried limiting the compile processes as well as restarting the HA instance. This is the log:
Library Manager: Installing bblanchon/ArduinoJson @ 6.18.5 INFO Installing bblanchon/ArduinoJson @ 6.18.5 Unpacking [####################################] 100% Library Manager: ArduinoJson@6.18.5 has been installed! INFO ArduinoJson@6.18.5 has been installed! HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
I also had this compilation error, resolved by disabling some of my add-ons temporarily (VSCode Server, OpenWakeWord) and freeing up resources. This is on Home Assistant VM running on Unraid with 4 cores and 2GB memory. It's interesting to see it took 525 seconds for compilation to fail, the entire process of updating took far less time to complete for me. Perhaps you're running Home Assistant on underpowered hardware?
I have a raspberry pi 4 with home assistant OS. With ref: v4.1.4 compiling works (would be strange if not, as this was working beforehand, when this was the main latest version).
I just wanted to try home assistant OS on raspberry pi 5, but it does not show up in the pi Imager, so installing might take some more time...
And have you tried cleaning the build files as suggested by @andythomas?
Hello I have also this error when updating to version 4.2 (HA running on RPI4)
Sorry for the noob's question as I am starting learning HA & ESPHome Where are located the build files you need to clean ?
Thx for your help ;-)
No worries, we are here to help you as good as we can. There is the three dots you have to press for a new menu. Please see the attached image. I marked two places with an arrow.
Thanx that does the trick to fix the error NSPanel running now with version 4.2.1
And have you tried cleaning the build files as suggested by @andythomas?
Of course and I was quite convinced this will help as others here with the same symptoms reported it helps :D
However, I have now tried with Raspberry Pi 5, same setup (restored backup...) and compiling works. It is the 8GB ram version of RPi5. My RPi4 has 2GB ram and I guess those with more ram might have succes with cleaning the build files, for me it failed in any case. Also surprising is that it did not fail with esp-idf on 4.1.4, so the switch to esp-idf is not the reason for the higher demand in ram after upgrade...
esp-idf
should be lighter for the compiler, as it removes one layer to be worked.
It's curious, as I don't see that big difference on the ESPHome side when compared to v4.1. I will have to try a bit more.
One thing that works pretty well is installing ESPHome in your laptop. It's much faster to compile and no chance to lack resources. I use that myself as part of the tests before each commit and it works like a charm.
Very likely this issue arises from insufficient ram on an underpowered device. I have the 4GB RPi4 and with a relatively normal install of HA this uses 3GB out of 4GB total memory (at its peak). For context, my base memory usage sits around 1.8GB.
Studio Code Server is a memory hog so it failed the first time I tried this without closing that addon. Compile completed in 582s after I did that.
I will investigate this more for a way to make it lighter, but I believe we cannot get too far without removing functionality, so that is not a direction I wanna go. One thing to try is removing the TFT transfer engine, as that is the biggest part of this project, but in this case you will have to flash an early version, like v4.1.4, use that to upload the latest TFT (v4.2.1), then flash your panel back without the TFT transfer by using this:
substitutions:
###### CHANGE ME START ######
device_name: "bueropanel"
wifi_ssid: "WLAN der Scham"
wifi_password: "..."
nextion_update_url: "http://homeassistant.local:8123/local/nspanel.tft" # URL to local tft File
# nextion_update_url: "http://homeassistant.local:8123/local/nspanel_blank.tft" # URL to local tft File
# nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_eu.tft" # URL to Github
# nextion_update_url: "https://github.com/Blackymas/NSPanel_HA_Blueprint/raw/main/nspanel_blank.tft" # URL to blank
# Add-on configuration (if needed)
# heater_relay: "1" # Possible values: "1" or "2"
# Customization area
##### My customization - Start #####
##### My customization - End #####
##### CHANGE ME END #####
##### DO NOT CHANGE ANYTHING! #####
packages:
##### download esphome code from Github
remote_package:
url: https://github.com/Blackymas/NSPanel_HA_Blueprint
ref: main
files:
# - nspanel_esphome.yaml # Base package removed as it includes TFT transfer
- advanced/esphome/nspanel_esphome_core.yaml # This is really the core without the TFT transfer
# Optional advanced and add-on configurations
# - advanced/esphome/nspanel_esphome_advanced.yaml
# - nspanel_esphome_addon_climate_cool.yaml
# - nspanel_esphome_addon_climate_heat.yaml
# - nspanel_esphome_addon_climate_dual.yaml
refresh: 300s
esp32:
framework:
type: esp-idf
##### DO NOT CHANGE ANYTHING! #####
I could try to split more thinks in this same way, so you could choose only what is important for you but, again, I don't think we can get that far this way. I'm more on the direction of a pre-built firmware, so we transfer the compiling to GitHub actions and take this from user's systems. But that requires more work and testing... Please take a look at this: https://github.com/Blackymas/NSPanel_HA_Blueprint/discussions/1602
TFT Version
No response
ESPHome Version
No response
Blueprint Version
No response
What is the bug?
Compiling when flashing the NSPanel fails, wirelessly as well as over uart
Steps to Reproduce
After trying with 1 NSPanel this worked and it looked nice, now I bought 8 and in the process of flashing all of those, it suddenly stopped working to flash the next one, it already failed during the compile step.
I then found out there is a new release, so maybe that is the reason. I looked for changes in the .yaml file and changed the files part to: files:
I tried the "validate" button on the ESPHome, it does not give green checkmark but red one.
And it does not work to update one of my already esphome flashed Panels (see log below) as well as creating a new blueprint (also see log below).
What am I doing wrong?
Your panel's YAML
ESPHome logs
Home Assistant logs
No response