Help with ESP Home Addon - installation & update of esp device failes

ESPHome
1

Hello together,

I fresh installed ESP Home but it seems to not work with installing or updating my esp devices.
I installed a bluetooth proxy with the website and it worked, but with ESP Home it always fails.
Here a example of my output, when I’m trying to update that bluetooth proxy esp device.

Output 
Reading CMake configuration...
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- The ASM compiler identification is unknown
-- Found assembler: xtensa-esp32-elf-gcc
-- Warning: Did not find file Compiler/-ASM
-- Configuring incomplete, errors occurred!
See also "/data/build/atom-bluetooth-proxy-a05be4/.pioenvs/atom-bluetooth-proxy-a05be4/CMakeFiles/CMakeOutput.log".
See also "/data/build/atom-bluetooth-proxy-a05be4/.pioenvs/atom-bluetooth-proxy-a05be4/CMakeFiles/CMakeError.log".

fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:298 (__project):
  The CMAKE_C_COMPILER:

    xtensa-esp32-elf-gcc

  is not a full path and was not found in the PATH.

  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)


CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:298 (__project):
  The CMAKE_CXX_COMPILER:

    xtensa-esp32-elf-g++

  is not a full path and was not found in the PATH.

  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)


CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:298 (__project):
  The CMAKE_ASM_COMPILER:

    xtensa-esp32-elf-gcc

  is not a full path and was not found in the PATH.

  Tell CMake where to find the compiler by setting either the environment
  variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)



========================= [FAILED] Took 83.81 seconds =========================
= [ERROR] /config/esphome/atom-bluetooth-proxy-a05be4.yaml =



======================== [SUMMARY] ========================
  - /config/esphome/atom-bluetooth-proxy-a05be4.yaml: FAILED

maybe i overlooked something but I didn’t find anything that seems to fix this issue.

2

What sort of install? Python? Docker? ESPHome add-on on HAOS?

3

ESP Home add-on on HAOS on a RPI4

4

Hmm - ok - it’s hard to break that. Maybe the issue is with your yaml. Post that and maybe someone will spot something.

5

The ESP Device yml:

substitutions:
  name: atom-bluetooth-proxy-a05be4
  friendly_name: Büro Proxy
packages:
  esphome.bluetooth-proxy: github://esphome/firmware/bluetooth-proxy/m5stack-atom-lite.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: <secret key>


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

I’m not that familiar with bluetooth proxy, but why are you including this package? Also - as far as I can tell that file you are referencing does not exist.