Good morning everybody.
The situation: I have a NSPanel (esp32) esphomeflashed directly connected with a Nuki Smart Lock with the great NukiLock component.
Working rock solid from some month now. and without any additional bridge in the middle.
With the latest update to 2022.12 and the changes to the ESP32 platform I’m not able to compile anymore, probably something related to the Nuki component itself.
Got a lot of scaring red lines during the compiling process…
Now the question.
Is it possible to force esphome to use the previous platform (the one used in 22022.11) so that I can update my NSPanel if needed?
Thank you in advance for your help.
Regards
zoogara
(Daryl)
December 15, 2022, 9:55am
2
Could possibly be this issue - there is supposedly a fix coming:
opened 07:37AM - 14 Dec 22 UTC
### The problem
Compile fails with "sh: 1: xtensa-esp32-elf-g++: not found"
…
### Which version of ESPHome has the issue?
2022.12.0
### What type of installation are you using?
Home Assistant Add-on
### Which version of Home Assistant has the issue?
2022.12.5
### What platform are you using?
ESP32
### Board
esp32dev
### Component causing the issue
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
Platform Manager: Installing platformio/espressif32 @ 5.2.0
INFO Installing platformio/espressif32 @ 5.2.0
Downloading [####################################] 100%
Unpacking [####################################] 100%
Platform Manager: [email protected] has been installed!
INFO [email protected] has been installed!
Tool Manager: Installing espressif/toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch3
INFO Installing espressif/toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch3
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: [email protected] +2021r2-patch3 has been installed!
INFO [email protected] +2021r2-patch3 has been installed!
Tool Manager: Installing platformio/framework-arduinoespressif32 @ ~3.20005.0
INFO Installing platformio/framework-arduinoespressif32 @ ~3.20005.0
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: [email protected] has been installed!
INFO [email protected] has been installed!
Tool Manager: Installing platformio/tool-esptoolpy @ ~1.40201.0
INFO Installing platformio/tool-esptoolpy @ ~1.40201.0
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: [email protected] has been installed!
INFO [email protected] has been installed!
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
- toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch3
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
Dependency Graph
|-- WiFi @ 2.0.0
|-- ESPmDNS @ 2.0.0
|-- Update @ 2.0.0
Compiling /data/luftkvalitet1/.pioenvs/luftkvalitet1/src/esphome/components/api/api_connection.cpp.o
sh: 1: xtensa-esp32-elf-g++: not found
*** [/data/luftkvalitet1/.pioenvs/luftkvalitet1/src/esphome/components/api/api_connection.cpp.o] Error 127
========================= [FAILED] Took 371.07 seconds =========================
```
### Additional information
_No response_
I don’t think is related to this, rather to the Nuki custom component…this is way I would prefer to instruct esphome to use the platforms used in the 2022.11 release…I don’t think I will ever need some more particular features in this device, but is just in case.
Any help is appreciated.