xtensa-lx106-elf-g++: not found

[gitolicious]

Operating environment/Installation (Hass.io/Docker/pip/etc.):

Hass.io on Odroid N2

Hass.io Add-on: ESPHome (beta) Beta version of ESPHome Hass.io add-on.

Add-on version: 1.15.0b3 You are running the latest version of this add-on. System: Debian GNU/Linux 9 (stretch) (armv7 / odroid-xu) Home Assistant Core: 0.113.2 Home Assistant Supervisor: 229

ESP (ESP32/ESP8266, Board/Sonoff):

ESP8266, but irrelevant

ESPHome version (latest production, beta, dev branch)

1.15.0b3 - fails for ESP32 and ESP8266 latest dev - fails for ESP32 and ESP8266 1.14.5 - fails for ESP32, works fine for ESP8266

Affected component:

n/a

Description of problem: Compilation is giving me xtensa-lx106-elf-g++: not found

Problem-relevant YAML-configuration entries:

esphome:
  name: test
  platform: ESP8266
  board: esp01_1m

Logs (if applicable):

INFO Reading configuration /config/esphome/test.yaml...
INFO Generating C++ source...
INFO Core config or version changed, cleaning build files...
INFO Deleting /data/test/.pioenvs
INFO Deleting /data/test/.piolibdeps
INFO Compiling app...
INFO Running:  platformio run -d /config/esphome/test
Processing test (board: esp01_1m; framework: arduino; platform: espressif8266@2.6.0)
--------------------------------------------------------------------------------
PackageManager: Installing toolchain-xtensa @ ~2.40802.191122
Downloading  [####################################]  100%          
Unpacking  [####################################]  100%          
toolchain-xtensa @ 2.40802.200502 has been successfully installed!
HARDWARE: ESP8266 80MHz, 80KB RAM, 1MB Flash
PACKAGES: 
 - framework-arduinoespressif8266 3.20702.0 (2.7.2) 
 - tool-esptool 1.413.0 (4.13) 
 - tool-esptoolpy 1.20800.0 (2.8.0) 
 - toolchain-xtensa 2.40802.200502 (4.8.2)
Dependency Graph
|-- <ESP8266WiFi> 1.0
|-- <ESP8266mDNS> 1.2
|   |-- <ESP8266WiFi> 1.0
Compiling /data/test/.pioenvs/test/src/esphome/core/application.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/core/component.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/core/controller.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/core/esphal.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/core/helpers.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
*** [/data/test/.pioenvs/test/src/esphome/core/application.cpp.o] Error 127
Compiling /data/test/.pioenvs/test/src/esphome/core/log.cpp.o
*** [/data/test/.pioenvs/test/src/esphome/core/component.cpp.o] Error 127
*** [/data/test/.pioenvs/test/src/esphome/core/controller.cpp.o] Error 127
*** [/data/test/.pioenvs/test/src/esphome/core/esphal.cpp.o] Error 127
*** [/data/test/.pioenvs/test/src/esphome/core/helpers.cpp.o] Error 127
sh: 1: xtensa-lx106-elf-g++: not found
*** [/data/test/.pioenvs/test/src/esphome/core/log.cpp.o] Error 127
========================= [FAILED] Took 24.86 seconds =========================

Additional information and things you've tried:

• Tried dev branch with gitpod.io, works fine there
• Searched for the binary within the docker container, exists at

  root@15ef4d2f-esphome-beta:~/.platformio/packages/toolchain-xtensa/bin# ls -la ./xtensa-lx106-elf-g++ 
  -rwxr-xr-x 1 root root 819856 Jul 17  2019 ./xtensa-lx106-elf-g++

• Log for ESP32:

  sh: 1: xtensa-esp32-elf-g++: not found

[barryodonovan]

I upgraded ESPHome in my HomeAssistant (Raspberry Pi 4 core-21.10.6 ) earlier today and hit this issue. After a couple of hours of reading and trying to figure out how to access the underlying OS (I really like to low effort of the OOB image but hate how 'user friendly' it is!) I finally just uninstalled and then re-installed the add-on. This time I updated my devices (diy ESP8266 stuff) and walked away while it installed all the bits (instead of being impatient and presuming it was done when it stopped responding for 15 minutes!).

xtensa toolchain 2.40802.0 installed, all good, everything working again...

ymmv

[yannpub]

@barryodonovan I just tried the same uninstall/install the addon within HA. But unfortunately not with the same result :-( Still the infamous sh: 1: xtensa-lx106-elf-g++: not found

The strange thing is that the executable exists on my system:

find /usr -name xtensa-lx106-elf-g++

/usr/share/hassio/addons/data/a0d7b954_esphome/cache/platformio/packages/toolchain-xtensa/bin/xtensa-lx106-elf-g++

/usr/bin/xtensa-lx106-elf-g++

Any idea I could try?

[motwok]

... I finally just uninstalled and then re-installed the add-on.

What Addon did you exactly reinstall... something INSIDE the Docker-Image oder the ESP-Home HA Plugin?

Emmo

[barryodonovan]

I uninstalled the add-on in the Add-On Store, then re-installed it.

Barry

From: motwok @.> Sent: Wednesday 3 November 2021 15:36 To: esphome/issues @.> Cc: Barry O'Donovan @.>; Mention @.> Subject: Re: [esphome/issues] xtensa-lx106-elf-g++: not found (#1386)

... I finally just uninstalled and then re-installed the add-on.

What Addon did you exactly reinstall... something INSIDE the Docker-Image oder the ESP-Home HA Plugin?

Emmo

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/esphome/issues/issues/1386#issuecomment-959473101, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB5XWZSDO3IEYNEHU67NHLLUKFJHLANCNFSM4POLG6PA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[Riva34]

I have tried various methods but none worked for me. I have given up and used Linux esphome command to compile and flash.

[wijnandtop]

Had the same issue while compiling code for: ESP8266 / esp01_m1

Running version 2021.11.3 of HA and version 2021.10.3 of ESPHome.

Solved the issue by using arduino framework version 3.0.2 (which is latest according to: https://github.com/esp8266/Arduino/releases )

So changing code to:

esphome:
  name: device-name
  platform: ESP8266
  board: esp01_1m
  arduino_version: 3.0.2

[K-4U]

None of these have worked for me. Even tried installing everything myself on the docker container but that made things even worse. How is this issue running for so long!?

[mmakaay]

How is this issue running for so long!?

Because nobody came up with a solid fix so far? What might help is to provide some more information on your setup and what exact steps you tried, since you report that proposed solutions don't work for you. That indicates that there might be another variable at play in your case.

[gitolicious]

The original issue was opened by me and for my setup it was resolved somehow. I left the ticket open as others are still facing problems. +1 for the proposal from @mmakaay, everyone who has problems should share their setup and exact issues so we can identify similarities.

[K-4U]

Fair enough, i was venting after a few hours of sunday frustration. Apologies.

I reinstalled the latest version of the esphome manager in Home Assistant and created a brand new esp8266 nodemcuv2 project and wanted to check if it could install on the esp8266 i had.

That failed compilation with the same errors as above, even with different arduino_version. I even tried the same version that i had running for another project. But just the barebones project with

esphome:
  name: 3d-printer-ledstrip
  platform: esp8266
  board: nodemcuv2

doesn't work.

[mmakaay]

No problem, been there ;-) And what type of architecture are you running on? Also ARM64, on a Raspberry Pi or so?? (since that is the architecture that I see appear regularly up here).

[K-4U]

Here i was thinking i had all the information. Yes, I am running on a raspberry pi 4.. Looks like aarch64 on raspbian buster.

Edit: I just realised that i did get it working by installing the 2021.9.3 version of the docker container, so it broke sometime after that!

[mmakaay]

Probably because of various dependencies moving forward.

I only have a raspberry running with architecture armv7l, so the 32 bit version. I don't see the same issues with that one, so my guess is that an external dependency is not (yet) ready for the job. I don't have access to a 64 bit aarch64 install unfortunately, so I can't dig deeper into this myself, but I'm moving some things around in my network to free up the Raspberry that currently runs Home Assistant, with the idea to make that one HASSOS + aarch64, to be able to troubleshoot things like this.

A general lesson for now would be: armv7l is safer for compatibility, but I know that's of little use at this moment.

[fran6120]

Same issue here.

I am running esphome v2021.11.1 through pip install on a Nexus 5 android phone (armv7l) using Termux app.

For ESP32 platform i can compile and install firmwares but when i try to install a firmware for ESP8266 platform, i get a sh: 1: xtensa-lx106-elf-g++: not found error, and if i add arduino_version: X.X.X doesn't work for me either.

I don't have an aarch64 Android phone to test if the same issue occurs

[mmakaay]

So what we can learn from that, is that this is not 100% linked to amd64, since you use armv7l.

[gianklug]

Same issue here. Neither changing the Arduino Framework nor disable 64 Bits on my Pi 4 helped. Any Ideas?

[motwok]

Why i cant currently find other projects that have this problem... whatever i have no (more) desire to solve this, even i get the needed knowledge in the next weeks.

[Drun555]

Docker-container v2021.11.4, rpi 4, OSMC installed (Debian). Same issue.

[gianklug]

Disabling 64-Bit on the Host AND reinstalling ESPHome/redeploying the container worked for me

On Fri, 3 Dec 2021 at 07:56, Drun555 @.***> wrote:

Docker-container v2021.11.4, rpi 4, OSMC installed (Debian). Same issue.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/esphome/issues/issues/1386#issuecomment-985262490, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGSKD2AAQGY5I44OHCBG3DUPBSYBANCNFSM4POLG6PA .

[Squale76]

My config :

System Health

version	core-2021.11.5
installation_type	Home Assistant Supervised
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.9.7
os_name	Linux
os_version	5.10.1-v8+
arch	aarch64
timezone	Europe/Paris

Home Assistant Community Store

GitHub API | ok -- | -- Github API Calls Remaining | 4194 Installed Version | 1.18.0 Stage | running Available Repositories | 912 Installed Repositories | 12

Home Assistant Cloud

logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Debian GNU/Linux 10 (buster) -- | -- update_channel | stable supervisor_version | supervisor-2021.10.8 docker_version | 20.10.1 disk_total | 109.8 GB disk_used | 16.8 GB healthy | true supported | failed to load: Unsupported supervisor_api | ok version_api | ok installed_addons | File editor (5.3.3), MariaDB (2.4.0), Nginx Proxy Manager (0.11.0), Zigbee2mqtt (1.18.1-1), Mosquitto broker (6.0.1), Node-RED (10.2.0), InfluxDB (4.3.0), SSH & Web Terminal (9.1.1), Samba share (9.5.1), SQLite Web (3.2.0), Vaultwarden (Bitwarden) (0.14.0), ESPHome (dev) (dev), ESPHome (2021.11.4)

Lovelace

dashboards | 3 -- | -- resources | 17 views | 14 mode | storage

A module code with no error :

code with no compilation error

``` esphome: name: ble_gateway platform: ESP32 board: nodemcu-32s wifi: ssid: !secret wifi_ssid password: !secret wifi_pass # Optional manual IP manual_ip: static_ip: !secret ip_ble_gateway gateway: !secret ip_gateway subnet: !secret ip_subnet # Enable fallback hotspot (captive portal) in case wifi connection fails ap: ssid: "Ble Gateway Fallback Hotspot" password: !secret ap_ble_pass captive_portal: # Enable logging logger: baud_rate: 0 # Enable Home Assistant API api: password: !secret ota_ble_pass ota: password: !secret ota_ble_pass esp32_ble_tracker: sensor: - platform: xiaomi_hhccjcy01 mac_address: !secret mac_addr_miflora1 temperature: name: "Xiaomi MiFlora Temperature" moisture: name: "Xiaomi MiFlora Moisture" illuminance: name: "Xiaomi MiFlora Illuminance" conductivity: name: "Xiaomi MiFlora Soil Conductivity" ```

And code with xtensa-lx106-elf-g++: not found error :

Code with compilation errors

``` # ESPHome configuration file for teleinfokit module https://342apps.net/module-teleinfokit/ esphome: #arduino_version: 3.0.2 name: teleinfokit platform: ESP8266 board: esp01_1m wifi: ssid: !secret wifi_ssid password: !secret wifi_key # Optional manual IP manual_ip: static_ip: !secret ip_teleinfo gateway: !secret ip_gateway subnet: !secret ip_subnet # Enable fallback hotspot (captive portal) in case wifi connection fails ap: ssid: "TeleInfoKit" password: !secret ap_key captive_portal: # Enable logging logger: baud_rate: 0 # disable logging via UART, help to avoid numerous crash with ESP_LOGD level: INFO # INFO for less log, put DEBUG to view all the linky's "étiquettes" received in the logs esp8266_store_log_strings_in_flash: False # :doc:`recommanded for ESP8266 ` # Enable Home Assistant API api: password: !secret api_pass ota: password: !secret ota_pass id: my_ota # web_server: # port: !secret web_port uart: id: uart_bus rx_pin: GPIO3 baud_rate: 1200 parity: EVEN data_bits: 7 teleinfo: id: myteleinfo update_interval: 30s historical_mode: true sensor: - platform: teleinfo tag_name: "PAPP" id: papp name: "Puissance Actuelle" unit_of_measurement: "VA" icon: mdi:flash teleinfo_id: myteleinfo - platform: teleinfo tag_name: "IINST" id: iinst name: "Intensité Actuelle" unit_of_measurement: "A" icon: mdi:flash teleinfo_id: myteleinfo - platform: teleinfo tag_name: "BASE" id: basekwh name: "Index (kWh)" unit_of_measurement: "kWh" icon: mdi:flash teleinfo_id: myteleinfo state_class: total_increasing device_class: energy accuracy_decimals: 3 filters: - lambda: return (x * 0.001); - platform: teleinfo tag_name: "BASE" id: base name: "Index" unit_of_measurement: "Wh" icon: mdi:flash teleinfo_id: myteleinfo state_class: total_increasing device_class: energy i2c: sda: GPIO0 scl: GPIO2 font: - file: "arial.ttf" id: arial_font size: 16 display: - platform: ssd1306_i2c model: "SSD1306 128x32" id: oled rotation: 180° address: 0x3C pages: - id: page1 lambda: |- it.printf(0, 0, id(arial_font), "Conso: %.0f VA", id(papp).state); - id: page2 lambda: |- it.printf(0, 0, id(arial_font), "Intensite: %.0f A", id(iinst).state); - id: page3 lambda: |- it.printf(0, 0, id(arial_font), "Index: %.0f", id(base).state); interval: - interval: 5s then: - display.page.show_next: oled - component.update: oled binary_sensor: - platform: gpio pin: number: GPIO1 mode: INPUT_PULLUP inverted: True name: teleinfokit_switch on_click: min_length: 50ms max_length: 350ms then: - lambda: if (id(oled).is_on()) id(oled).turn_off(); else id(oled).turn_on(); ```

I tried to modify arduino_version with no success, tried to reinstall ESPHome, no success.

In docker container, i found xtensa-lx106-elf-g++ with find / -name xtensa-lx106-elf-g++ command in :

root@15ef4d2f-esphome:/# find / -name xtensa-lx106-elf-g++
/data/cache/platformio/packages/toolchain-xtensa@2.40802.200502/bin/xtensa-lx106-elf-g++
/data/cache/platformio/packages/toolchain-xtensa/bin/xtensa-lx106-elf-g++

I hope to find a solution

[motwok]

Disabling 64-Bit on the Host AND reinstalling ESPHome/redeploying the container worked for me … Is it possible that you did understand the impact of having 32bit instead of 64bit?

mo

[twocolors]

install ubuntu 64bit on raspberry catch this error , switch from linux/arm/v7 to linux/arm64 solved

[Morcatko]

I had the same issue once I upgraded my LibreELEC 9.x to 10x on RPi4.

I was able to make it work by adding a platform property to my docker-compose.yaml file.

version: "3.9"
services:
   esphome:
    image: esphome/esphome
    platform: linux/arm64

You should be able to use platform even with docker pull or use pull by digest.

make it work = it compiles. I have not tested anything else yet.

---

https://docs.docker.com/compose/compose-file/compose-file-v2/#platform https://docs.docker.com/engine/reference/commandline/pull/#pull-an-image-by-digest-immutable-identifier

[saipavanc]

Did anybody try to install it in a Python env? I am facing this same error

HARDWARE: ESP8266 80MHz, 80KB RAM, 1MB Flash
Dependency Graph
|-- <ESPAsyncTCP-esphome> 1.2.3
|-- <ESPAsyncWebServer-esphome> 2.1.0
|   |-- <ESPAsyncTCP-esphome> 1.2.3
|   |-- <Hash> 1.0
|   |-- <ESP8266WiFi> 1.0
|-- <DNSServer> 1.1.1
|-- <ESP8266WiFi> 1.0
|-- <ESP8266mDNS> 1.2
Compiling .pioenvs/bedroom/src/esphome/components/api/api_connection.cpp.o
Compiling .pioenvs/bedroom/src/esphome/components/api/api_frame_helper.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
sh: 1: xtensa-lx106-elf-g++: not found
Compiling .pioenvs/bedroom/src/esphome/components/api/api_pb2.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling .pioenvs/bedroom/src/esphome/components/api/api_pb2_service.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling .pioenvs/bedroom/src/esphome/components/api/api_server.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling .pioenvs/bedroom/src/esphome/components/api/list_entities.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling .pioenvs/bedroom/src/esphome/components/api/proto.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
*** [.pioenvs/bedroom/src/esphome/components/api/api_connection.cpp.o] Error 127
Compiling .pioenvs/bedroom/src/esphome/components/api/subscribe_state.cpp.o
*** [.pioenvs/bedroom/src/esphome/components/api/api_frame_helper.cpp.o] Error 127
*** [.pioenvs/bedroom/src/esphome/components/api/api_pb2.cpp.o] Error 127
*** [.pioenvs/bedroom/src/esphome/components/api/api_pb2_service.cpp.o] Error 127
*** [.pioenvs/bedroom/src/esphome/components/api/api_server.cpp.o] Error 127
*** [.pioenvs/bedroom/src/esphome/components/api/list_entities.cpp.o] Error 127
*** [.pioenvs/bedroom/src/esphome/components/api/proto.cpp.o] Error 127
sh: 1: xtensa-lx106-elf-g++: not found
*** [.pioenvs/bedroom/src/esphome/components/api/subscribe_state.cpp.o] Error 127
===================================================================== [FAILED] Took 4.69 seconds =====================================================================

This is my platform:

$ uname -a
Linux localhost 4.4.285-perf+ #1 SMP PREEMPT Tue Dec 21 07:54:44 UTC 2021 aarch64 Android

When I try to run the executable from ~/.platformio/packages/toolchain-xtensa/bin, I get an error saying the file doesn't exist which is weird because I can see it in ls. Somehow, shell sh is not recognizing the file either. Any help in this regard will be highly appreciated.

[heintjeput]

I am currently running into the same issue. I tried the first work around adding: arduino_version: 2.5.1 --> doesn't work 2nd work around: arduino_version: 3.0.2 --> does work

Is there a 3rd work around for compiling the code yourself? In that case where to find the code?

What can we do to push this issue forward, it has been running for almost 1.5 year now, but no real root cause or solution yet.

I am running hassOs 7.0 / Hass 2021.12.6 on a RPi 3

[motwok]

PLEASE PROVE ME WRONG: THIS BUG WILL NEVER EVER BE FIXED.

Look into your installation and you one reason... Meanwhile there is a big message stating your operating system is not supported (because you dont use a hass image or not the "original" hass image).

What can we do to push this issue forward, it has been running for almost 1.5 year now, but no real root cause or solution yet. And even when we push this hourly in a reasonable fashion, its more meaningfull to piss on a tree... Why? This feeling to be discharged is so relaxing! :)

Ignorance and delay are the deadliest forms of denial.

if you realy want a solution:

• Learn Docker basics
• Learn how platformio works (has to be installed)
• Learn how esspressiv supports plattformio
• Learn how to create a working Esphome installation
• Do all the above again in "expert mode" (become an expert)
• Create your own working esphome docker image
• Feel proud that you found the solution.
• Create a PR for the devs
• Maintain the PR and wait for a year or two
• Find out that you fouled yourself by hoping somone review / tests / merges the PR
• publish it elsewhere

last 4 points sound pesimistic... nope... that is pure "experienced optimism"!

mo

[mmakaay]

Another way to help things forward would be: create a clean write up of a step by step process to reproduce the issue. I've looked over this issue a couple of times now, but I have no inspiration on how to get this build error on a local system, allowing to poke at it and see if there's a way to fix it.

When there's a PR, I don't think the last four steps need to reach this level of optimism :-)

[jesserockz]

My HA is on a Blue (Odroid N2+) with HA OS which works as expected and I personally have never seen this error. I am not sure how I could even attempt to reproduce this myself sorry.

[saipavanc]

To put the process to reproduce this error, it is pretty straightforward. These are the steps and I got to the same error following this procedure twice after I installed a different custom ROM, so I think it is reproducible.

• Install Termux using FDroid store on an android phone. Hopefully on some latest android 11 or 12.
• follow the following commands

  pkg update
  pkg upgrade
  pkg install python
  pip install esphome

• Then follow the Getting started with ESPHome guide.

  esphome wizard livingroom.yaml
  esphome run livingroom.yaml

• I encountered the above error with the last command when it started compiling. The same is pasted here

  HARDWARE: ESP8266 80MHz, 80KB RAM, 1MB Flash
  Dependency Graph
  |-- <ESPAsyncTCP-esphome> 1.2.3
  |-- <ESPAsyncWebServer-esphome> 2.1.0
  |   |-- <ESPAsyncTCP-esphome> 1.2.3
  |   |-- <Hash> 1.0
  |   |-- <ESP8266WiFi> 1.0
  |-- <DNSServer> 1.1.1
  |-- <ESP8266WiFi> 1.0
  |-- <ESP8266mDNS> 1.2
  Compiling .pioenvs/bedroom/src/esphome/components/api/api_connection.cpp.o
  Compiling .pioenvs/bedroom/src/esphome/components/api/api_frame_helper.cpp.o
  sh: 1: xtensa-lx106-elf-g++: not found
  sh: 1: xtensa-lx106-elf-g++: not found
  Compiling .pioenvs/bedroom/src/esphome/components/api/api_pb2.cpp.o
  sh: 1: xtensa-lx106-elf-g++: not found
  Compiling .pioenvs/bedroom/src/esphome/components/api/api_pb2_service.cpp.o
  sh: 1: xtensa-lx106-elf-g++: not found
  Compiling .pioenvs/bedroom/src/esphome/components/api/api_server.cpp.o
  sh: 1: xtensa-lx106-elf-g++: not found
  Compiling .pioenvs/bedroom/src/esphome/components/api/list_entities.cpp.o
  sh: 1: xtensa-lx106-elf-g++: not found
  Compiling .pioenvs/bedroom/src/esphome/components/api/proto.cpp.o
  sh: 1: xtensa-lx106-elf-g++: not found
  *** [.pioenvs/bedroom/src/esphome/components/api/api_connection.cpp.o] Error 127
  Compiling .pioenvs/bedroom/src/esphome/components/api/subscribe_state.cpp.o
  *** [.pioenvs/bedroom/src/esphome/components/api/api_frame_helper.cpp.o] Error 127
  *** [.pioenvs/bedroom/src/esphome/components/api/api_pb2.cpp.o] Error 127
  *** [.pioenvs/bedroom/src/esphome/components/api/api_pb2_service.cpp.o] Error 127
  *** [.pioenvs/bedroom/src/esphome/components/api/api_server.cpp.o] Error 127
  *** [.pioenvs/bedroom/src/esphome/components/api/list_entities.cpp.o] Error 127
  *** [.pioenvs/bedroom/src/esphome/components/api/proto.cpp.o] Error 127
  sh: 1: xtensa-lx106-elf-g++: not found
  *** [.pioenvs/bedroom/src/esphome/components/api/subscribe_state.cpp.o] Error 127
  ===================================================================== [FAILED] Took 4.69 seconds =====================================================================

  I understand that Android OS is not supported in the first place, but installing it along with Home Assistant on an old phone which is lying around seems to be very appealing, because the chipsets are more than capable to handle ESPHome. I have just also installed Home Assistant along with octa4a and everything seems to be smooth and responsive. I'm no expert at making or developing packages but if someone can figure that out it would be amazing, can help give life to an old phone and also save you from all the cost to buy and setup a Raspberry Pi 3 or 4.

For a workaround, I was able to install ESPHome in my laptop and use it to compile a small test code to an ESP-01. This was picked up as an extra available device on my Home Assistant. So, ESPHome should be installed on the android as well, but any thing that requires compilation like adding a new ESP to the network or updating them on wifi that can hopefully done from the laptop itself. One small advantage here is that compilation of ESP code can be much quicker on the laptop compared to an android phone.

[fran6120]

I think what this issue is not caused by esphome. Trying to test on platformio with other envariomens i get similar errors that make me think what the problem it is in platformio.

(esphome) ~/.../unit-testing/calculator $ platformio test
Verbose mode can be enabled via -v, --verbose option
Collected 3 items

Processing test_common in uno environment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Building...
sh: 1: avr-g++: not found
*** [.pio/build/uno/test/test_common/test_calculator.cpp.o] Error 127
sh: 1: avr-g++: not found
*** [.pio/build/uno/test/tmp_pio_test_transport.cpp.o] Error 127
========================================================================================= [FAILED] Took 3.18 seconds =========================================================================================

Processing test_common in nodemcu environment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Building...
sh: 1: xtensa-lx106-elf-g++: not found
*** [.pio/build/nodemcu/test/test_common/test_calculator.cpp.o] Error 127
sh: 1: xtensa-lx106-elf-g++: not found
*** [.pio/build/nodemcu/test/tmp_pio_test_transport.cpp.o] Error 127
========================================================================================= [FAILED] Took 4.27 seconds =========================================================================================

Processing test_common in esp32 environment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Building...
/data/data/com.termux/files/home/.platformio/packages/framework-arduinoespressif32/cores/esp32/esp32-hal-spi.c: In function 'spiTransferBytesNL':
/data/data/com.termux/files/home/.platformio/packages/framework-arduinoespressif32/cores/esp32/esp32-hal-spi.c:922:39: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
                 uint8_t * last_out8 = &result[c_longs-1];
                                       ^
/data/data/com.termux/files/home/.platformio/packages/framework-arduinoespressif32/cores/esp32/esp32-hal-spi.c:923:40: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
                 uint8_t * last_data8 = &last_data;
                                        ^
Uploading...
Tool Manager: Installing platformio/tool-mkspiffs @ ~2.230.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Tool Manager: tool-mkspiffs @ 2.230.0 has been installed!

Warning! Please install `99-platformio-udev.rules`.
More details: https://docs.platformio.org/page/faq.html#platformio-udev-rules

Error: Please specify `upload_port` for environment or use global `--upload-port` option.
For some development platforms it can be a USB flash drive (i.e. /media/<user>/<device name>)
*** [upload] Explicit exit, status 1
========================================================================================= [FAILED] Took 59.14 seconds =========================================================================================

Processing test_common in native environment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Building...
sh: 1: ar: not found
*** [.pio/build/native/lib86c/libcalculator.a] Error 127
========================================================================================= [FAILED] Took 3.52 seconds =========================================================================================

Processing test_desktop in native environment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Building...
sh: 1: ar: not found
*** [.pio/build/native/lib86c/libcalculator.a] Error 127
========================================================================================= [FAILED] Took 3.58 seconds =========================================================================================

Processing test_embedded in uno environment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Building...
sh: 1: avr-g++: not found
*** [.pio/build/uno/test/test_embedded/test_calculator.cpp.o] Error 127
sh: 1: avr-g++: not found
*** [.pio/build/uno/test/tmp_pio_test_transport.cpp.o] Error 127
========================================================================================= [FAILED] Took 3.00 seconds =========================================================================================

Processing test_embedded in nodemcu environment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Building...
sh: 1: xtensa-lx106-elf-g++: not found
*** [.pio/build/nodemcu/test/test_embedded/test_calculator.cpp.o] Error 127
sh: 1: xtensa-lx106-elf-g++: not found
*** [.pio/build/nodemcu/test/tmp_pio_test_transport.cpp.o] Error 127
========================================================================================= [FAILED] Took 4.11 seconds =========================================================================================

Processing test_embedded in esp32 environment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Building...
Uploading...

Warning! Please install `99-platformio-udev.rules`.
More details: https://docs.platformio.org/page/faq.html#platformio-udev-rules

Error: Please specify `upload_port` for environment or use global `--upload-port` option.
For some development platforms it can be a USB flash drive (i.e. /media/<user>/<device name>)
*** [upload] Explicit exit, status 1
========================================================================================= [FAILED] Took 24.70 seconds =========================================================================================

Test           Environment    Status    Duration
-------------  -------------  --------  ------------
test_common    uno            FAILED    00:00:03.182
test_common    nodemcu        FAILED    00:00:04.272
test_common    esp32          FAILED    00:00:59.143
test_common    native         FAILED    00:00:03.515
test_desktop   native         FAILED    00:00:03.576
test_embedded  uno            FAILED    00:00:03.002
test_embedded  nodemcu        FAILED    00:00:04.113
test_embedded  esp32          FAILED    00:00:24.701
==================================================================================== 8 failed, 0 succeeded in 00:01:45.505 ====================================================================================

Curiously enough building only works on esp32 platform, it can see in some lines below and on esphome i have chek it with a esp32cam.

INFO Reading configuration config/esp32cam.yaml...
WARNING GPIO0 is a Strapping PIN and should be avoided.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Generating C++ source...
INFO Compiling app...
Processing esp32cam (board: esp32cam; framework: arduino; platform: platformio/espressif32 @ 3.3.2)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
Dependency Graph
|-- <AsyncTCP-esphome> 1.2.2
|-- <WiFi> 1.0
|-- <FS> 1.0
|-- <Update> 1.0
|-- <ESPAsyncWebServer-esphome> 2.1.0
|   |-- <AsyncTCP-esphome> 1.2.2
|-- <DNSServer> 1.1.0
|-- <ESPmDNS> 1.0
Compiling .pioenvs/esp32cam/src/esphome/components/api/api_connection.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/api_frame_helper.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/api_pb2.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/api_pb2_service.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/api_server.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/list_entities.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/proto.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/subscribe_state.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/user_services.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/api/util.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/captive_portal/captive_portal.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/esp32/core.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/esp32/gpio_arduino.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/esp32/gpio_idf.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/esp32/preferences.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/esp32_camera/esp32_camera.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/esp32_camera_web_server/camera_web_server.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/logger/logger.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/md5/md5.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/mdns/mdns_component.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/mdns/mdns_esp32_arduino.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/mdns/mdns_esp8266.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/mdns/mdns_esp_idf.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/network/util.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/ota/ota_backend_arduino_esp32.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/ota/ota_backend_arduino_esp8266.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/ota/ota_backend_esp_idf.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/ota/ota_component.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/socket/bsd_sockets_impl.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/socket/lwip_raw_tcp_impl.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/web_server_base/web_server_base.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/wifi/wifi_component.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/wifi/wifi_component_esp32_arduino.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/wifi/wifi_component_esp8266.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/components/wifi/wifi_component_esp_idf.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/application.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/color.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/component.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/controller.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/entity_base.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/helpers.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/log.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/scheduler.cpp.o
Compiling .pioenvs/esp32cam/src/esphome/core/util.cpp.o
Compiling .pioenvs/esp32cam/src/main.cpp.o
Generating partitions .pioenvs/esp32cam/partitions.bin
Compiling .pioenvs/esp32cam/libf4a/AsyncTCP-esphome/AsyncTCP.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/ETH.cpp.o
Archiving .pioenvs/esp32cam/libf4a/libAsyncTCP-esphome.a
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFi.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFiAP.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFiClient.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFiGeneric.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFiMulti.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFiSTA.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFiScan.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFiServer.cpp.o
Compiling .pioenvs/esp32cam/lib8e3/WiFi/WiFiUdp.cpp.o
Compiling .pioenvs/esp32cam/libe22/FS/FS.cpp.o
Compiling .pioenvs/esp32cam/libe22/FS/vfs_api.cpp.o
Archiving .pioenvs/esp32cam/lib8e3/libWiFi.a
Compiling .pioenvs/esp32cam/libec0/Update/HttpsOTAUpdate.cpp.o
Compiling .pioenvs/esp32cam/libec0/Update/Updater.cpp.o
Archiving .pioenvs/esp32cam/libe22/libFS.a
Compiling .pioenvs/esp32cam/lib388/ESPAsyncWebServer-esphome/AsyncEventSource.cpp.o
Compiling .pioenvs/esp32cam/lib388/ESPAsyncWebServer-esphome/AsyncWebSocket.cpp.o
Archiving .pioenvs/esp32cam/libec0/libUpdate.a
Compiling .pioenvs/esp32cam/lib388/ESPAsyncWebServer-esphome/WebAuthentication.cpp.o
Compiling .pioenvs/esp32cam/lib388/ESPAsyncWebServer-esphome/WebHandlers.cpp.o
Compiling .pioenvs/esp32cam/lib388/ESPAsyncWebServer-esphome/WebRequest.cpp.o
Compiling .pioenvs/esp32cam/lib388/ESPAsyncWebServer-esphome/WebResponses.cpp.o
Compiling .pioenvs/esp32cam/lib388/ESPAsyncWebServer-esphome/WebServer.cpp.o
Compiling .pioenvs/esp32cam/lib19f/DNSServer/DNSServer.cpp.o
Compiling .pioenvs/esp32cam/lib99e/ESPmDNS/ESPmDNS.cpp.o
Archiving .pioenvs/esp32cam/lib388/libESPAsyncWebServer-esphome.a
Archiving .pioenvs/esp32cam/libFrameworkArduinoVariant.a
Compiling .pioenvs/esp32cam/FrameworkArduino/Esp.cpp.o
Archiving .pioenvs/esp32cam/lib19f/libDNSServer.a
Compiling .pioenvs/esp32cam/FrameworkArduino/FunctionalInterrupt.cpp.o
Archiving .pioenvs/esp32cam/lib99e/libESPmDNS.a
Compiling .pioenvs/esp32cam/FrameworkArduino/HardwareSerial.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/IPAddress.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/IPv6Address.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/MD5Builder.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/Print.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/Stream.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/StreamString.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/WMath.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/WString.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/base64.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/cbuf.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-adc.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-bt.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-cpu.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-dac.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-gpio.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-i2c.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-ledc.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-log.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-matrix.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-misc.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-psram.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-rmt.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-sigmadelta.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-spi.c.o
/data/data/com.termux/files/home/.platformio/packages/framework-arduinoespressif32/cores/esp32/esp32-hal-spi.c: In function 'spiTransferBytesNL':
/data/data/com.termux/files/home/.platformio/packages/framework-arduinoespressif32/cores/esp32/esp32-hal-spi.c:922:39: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
                 uint8_t * last_out8 = &result[c_longs-1];
                                       ^
/data/data/com.termux/files/home/.platformio/packages/framework-arduinoespressif32/cores/esp32/esp32-hal-spi.c:923:40: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
                 uint8_t * last_data8 = &last_data;
                                        ^
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-time.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-timer.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-touch.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/esp32-hal-uart.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/libb64/cdecode.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/libb64/cencode.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/main.cpp.o
Compiling .pioenvs/esp32cam/FrameworkArduino/stdlib_noniso.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/wiring_pulse.c.o
Compiling .pioenvs/esp32cam/FrameworkArduino/wiring_shift.c.o
Archiving .pioenvs/esp32cam/libFrameworkArduino.a
Linking .pioenvs/esp32cam/firmware.elf
RAM:   [=         ]  14.1% (used 46088 bytes from 327680 bytes)
Flash: [======    ]  58.5% (used 1072994 bytes from 1835008 bytes)
Building .pioenvs/esp32cam/firmware.bin
======================== [SUCCESS] Took 247.76 seconds ========================
INFO Successfully compiled program.

[netfarma]

Hi,

I have RP3 B+ and have the same problem. (HA 64bit) I was trying all configuration methods above. nothing worked..

Today i have downloaded last stable version https://github.com/home-assistant/operating-system/releases/download/7.1/haos_rpi3-64-7.1.img.xz

Installed again on my microsd card with BalenaEther. next thing was install ESPHome and add (UI) new esp32 device. The autogenerated code looks like:

esphome:
  name: test

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: "xxx"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Test Fallback Hotspot"
    password: "xxx"

captive_portal:

Than I clicked INSTALL, choose connected USB device and miracle happend :D My esp32 device is ONLINE!

Don't known the problem was my device configuration or old HA installation, but now it works. Didn't have any sensors connected, now i am happy it is compiled at all.

Br

[Fraddles]

I recently encountered this when going to do a build on a Raspberry for the first time in a while, previously I was building on an i7 laptop (Debian) that worked fine.

I have two Pi4s... both running Raspbian GNU/Linux 10 (buster) One with original 32-bit O/S install upgraded with 64-bit kernel. This fails to compile with the above not found error. One with clean install from 64-bit Beta OS. This compiles just fine.

Both fully updated and using Docker installed with the 'convenience script'. One difference I noticed was that the first Pi is using the Arm build of Docker, whereas the second is using the Arm64 build, despite both having been installed with the 64-bit kernel...

Otherwise same Kernel version, Same O/S version, same Docker version, almost the same hardware (one is a 4GB, the other is 8GB). Docker-Compose version is different, but I cannot see that making a difference here...

Cheers.

[motwok]

Both fully updated and using Docker installed with the 'convenience script'. One difference I noticed was that the first Pi is using the Arm build of Docker, whereas the second is using the Arm64 build, despite both having been installed with the 64-bit kernel...

How did you install docker 64 bit version?

Emmo

[jpcornil-git]

I have the same issue, i.e. config not building on RPI/aarch64 using esphome dashboard, but I was able to build using esphome CLI on the same platform/esphome venv. => issue seems specific to dashboard (rather than toolchain)

[jpcornil-git]

Found/fixed my issue in the mean time ...

I had the following systemctl service

[Unit]
Description=ESPHome Dashboard
After=network-online.target

[Service] 
Type=simple 
User=homeassistant 
Environment="PATH=/srv/esphome/bin" 
ExecStart=/srv/esphome/bin/esphome dashboard /home/homeassistant/.homeassistant/esphome/ 
[Install]
WantedBy=multi-user.target

but Environment variable should have been (I installed esphome in /srv just as homeassistant and esphome configuration files under /home/homeassistant/.homeassistant/esphome/):

[Unit]
Description=ESPHome Dashboard
After=network-online.target

[Service] 
Type=simple 
User=homeassistant 
Environment="PATH=/srv/esphome/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games" 
ExecStart=/srv/esphome/bin/esphome dashboard /home/homeassistant/.homeassistant/esphome/ 
[Install]
WantedBy=multi-user.target

with the above I can build from the dashboard interface on my RPi/aarch64 as well

[gianklug]

Getting this issue again after updating to Hass OS Supervised 2022.1

[motwok]

Getting this issue again after updating to Hass OS Supervised 2022.1

And round and round it goes 🗡️

You think that was solved and solved forever?

There is some problem in the intallation of the xtensa package... looks for me the 32/64bit check is faulty... or lets say there are 2 different... one is used for the installation and one for the execution... and on such a mixed system they come to a different conclusion.

Emmo

[deathsfaction]

Getting this issue again after updating to Hass OS Supervised 2022.1

Same - this is frustrating as it's the first time I've come across it and I can't find a way to fix it. Got a pile of sensors to add and can't :(

Ive read this entire post but can't identify a proper 'fix' for this.

[gianklug]

Disabling 64-Bit on my Pi 4 and reinstalling the addon fixed it for me

deathsfaction @.***> schrieb am Fr., 11. Feb. 2022, 09:44:

Getting this issue again after updating to Hass OS Supervised 2022.1

Same - this is frustrating as it's the first time I've come across it and I can't find a way to fix it. Got a pile of sensors to add and can't :(

Ive read this entire post but can't identify a proper 'fix' for this.

— Reply to this email directly, view it on GitHub https://github.com/esphome/issues/issues/1386#issuecomment-1035985936, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGSKD3ULCDIEN2YVBMHE4TU2TD7VANCNFSM4POLG6PA . You are receiving this because you commented.Message ID: @.***>

[deathsfaction]

Disabling 64-Bit on my Pi 4 and reinstalling the addon fixed it for me deathsfaction @.> schrieb am Fr., 11. Feb. 2022, 09:44: … Getting this issue again after updating to Hass OS Supervised 2022.1 Same - this is frustrating as it's the first time I've come across it and I can't find a way to fix it. Got a pile of sensors to add and can't :( Ive read this entire post but can't identify a proper 'fix' for this. — Reply to this email directly, view it on GitHub <#1386 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGSKD3ULCDIEN2YVBMHE4TU2TD7VANCNFSM4POLG6PA . You are receiving this because you commented.Message ID: @.>

I've got it installed from the HASS image - not sure what the knock-on effects of that would be and would hate to lose everything I have already set up as it's quite a large setup I have.

What's the best way to 'reinstall'?

[pechenkin655]

I have the same issue, i.e. config not building on RPI/aarch64 using esphome dashboard, but I was able to build using esphome CLI on the same platform/esphome venv. => issue seems specific to dashboard (rather than toolchain)

Raspberry pi 4, Ubuntu 20.04.3, 64 bit os. Esphome installed using docker. Can confirm, running

esphome compile config.yml

or

esphome run config.yml

within esphome's container is working. Trying to run install from dashboard resulting in same error:

sh: 1: xtensa-lx106-elf-g++: Permission denied
Compiling .pioenvs/tvoc-node-1/src/esphome/components/api/api_frame_helper.cpp.o
sh: 1: xtensa-lx106-elf-g++: Permission denied
Compiling .pioenvs/tvoc-node-1/src/esphome/components/api/api_pb2.cpp.o
sh: 1: xtensa-lx106-elf-g++: Permission denied
*** [.pioenvs/tvoc-node-1/src/esphome/components/api/api_connection.cpp.o] Error 126
Compiling .pioenvs/tvoc-node-1/src/esphome/components/api/api_pb2_service.cpp.o
*** [.pioenvs/tvoc-node-1/src/esphome/components/api/api_frame_helper.cpp.o] Error 126
*** [.pioenvs/tvoc-node-1/src/esphome/components/api/api_pb2.cpp.o] Error 126
sh: 1: xtensa-lx106-elf-g++: Permission denied
*** [.pioenvs/tvoc-node-1/src/esphome/components/api/api_pb2_service.cpp.o] Error 126```

[jpcornil-git]

Your issue looks related to incorrect access rights (compiler not able to write object files)

Do you know what user is running dashboard and in which configuration directory, e.g. my (custom) install uses systemd to run dashboard service (content of my /etc/systemd/system/esphome@homeassistant.service dumped above) and run it as homeassistant:

User=homeassistant

using /home/homeassistant/.homeassistant/esphome as configuration directory (homeassistant has full access rights here):

ExecStart=/srv/esphome/bin/esphome dashboard /home/homeassistant/.homeassistant/esphome/

[thoompje]

Found/fixed my issue in the mean time ...

I had the following systemctl service

[Unit]
Description=ESPHome Dashboard
After=network-online.target

[Service] 
Type=simple 
User=homeassistant 
Environment="PATH=/srv/esphome/bin" 
ExecStart=/srv/esphome/bin/esphome dashboard /home/homeassistant/.homeassistant/esphome/ 
[Install]
WantedBy=multi-user.target

but Environment variable should have been (I installed esphome in /srv just as homeassistant and esphome configuration files under /home/homeassistant/.homeassistant/esphome/):

[Unit]
Description=ESPHome Dashboard
After=network-online.target

[Service] 
Type=simple 
User=homeassistant 
Environment="PATH=/srv/esphome/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games" 
ExecStart=/srv/esphome/bin/esphome dashboard /home/homeassistant/.homeassistant/esphome/ 
[Install]
WantedBy=multi-user.target

with the above I can build from the dashboard interface on my RPi/aarch64 as well

Where did you build this service? Inside the ESPHome container or the home assistant container or op de pi itself?

[jpcornil-git]

Hi @thoompje, I'm using a core install for HA and run therefore everything on the pi itself/no containers but venv. I've a spare RPi and could therefore run a test with e.g. HAOS running HA+ESPHome containers Cheers, jpc

[thoompje]

Hi @thoompje, I'm using a core install for HA and run therefore everything on the pi itself/no containers but venv. I've a spare RPi and could therefore run a test with e.g. HAOS running HA+ESPHome containers Cheers, jpc

Ahh thanks a lot, that would be great! Hopefully we can fix this with a workaround🙏

[jpcornil-git]

Do I need specific versions or latest HAOS/ESPHome versions are exposing the issue ?

[thoompje]

Just latest version

[thoompje]

Do I need specific versions or latest HAOS/ESPHome versions are exposing the issue ?

Any news from the lab?😁

[jpcornil-git]

Hi @thoompje,

I just created a test setup and had no issues to build/install (from HA/ESPHome UI and docker CLI) with:

• aarch64 (RPi)
• Home Assistant OS 2022.2.9
• ESPHome 2022.2.6
• https://github.com/jpcornil-git/HA-M5StickC (platformio/espressif32 @ 3.5.0)

Do you have a failing configuration yaml calling for xtensa-lx106-elf toolchain that I could try to build as well?

Cheers, jpc

[thoompje]

Hi @thoompje,

I just created a test setup and had no issues to build/install (from HA/ESPHome UI and docker CLI) with:

• aarch64 (RPi)
• Home Assistant OS 2022.2.9
• ESPHome 2022.2.6
• https://github.com/jpcornil-git/HA-M5StickC (platformio/espressif32 @ 3.5.0)

Do you have a failing configuration yaml calling for xtensa-lx106-elf toolchain that I could try to build as well?

Cheers, jpc

Hi, this is my config, i removed the SSID, IP and passwords of course :)

esphome:
  name: shutters
  platform: ESP8266
  board: nodemcuv2
  esp8266_restore_from_flash: true

# Enable logging
logger:

# Enable Home Assistant API
api:
  password: ""

ota:
  password: ""

wifi:
  ssid: ""
  password: ""

  manual_ip:
    static_ip: 
    gateway: 
    subnet: 255.255.255.0

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Shutters Fallback Hotspot"
    password: ""

captive_portal:

switch:
  - platform: gpio
    pin: D1
    name: "Shutter 1 plus"
    id: shutter1plus
  - platform: gpio
    pin: D2
    name: "Shutter 1 min"
    id: shutter1min
  - platform: restart
    name: "Shutter restart"

cover:
  - platform: time_based
    name: "Shutters"

    open_action:
      - switch.turn_on: shutter1plus
      - switch.turn_off: shutter1min
    open_duration: 12s

    close_action:
      - switch.turn_on: shutter1min
      - switch.turn_off: shutter1plus
    close_duration: 12s

    stop_action:
      - switch.turn_off: shutter1plus
      - switch.turn_off: shutter1min