hi all - first time poster so if I should be doing this elsewhere please let me know - have been using M5 Atom Lites as bluetooth proxies in Home Assistant. I’ve updated the Home Assistant core to the latest version 2023.1.0 this is now generating a warning saying I need to update the proxies to ESPHome 2022.12.0 or later, but when I attempt to do this via the ESPHome add on’s Web UI, the update fails. Any tips on how to get the updates to succeed? Thanks in advance. cheers, cal
What version of esphome are you running?
‘Failed’ is not an error message. Logs?
Hi there - thanks for the reply - ESPHome add on 2022.12.3 - have uninstalled and reinstalled today. This pic is from my last attempt to update via the HA ESPHome add-on Web UI
Thanks for your help - I’ll try to give you whatever you need - cheers
Please stop making screenshots. Cut, paste, win.
It may be helpful too to see your yaml file.
no more screenshots - happy to oblige 
yaml of the one of my proxies obtained from the ESPHome add-on’s web ui:
substitutions:
name: atom-bluetooth-proxy-06d720
packages:
esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/m5stack-atom-lite.yaml@main
esphome:
name: ${name}
name_add_mac_suffix: false
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
let me know if I can provide anything else too - thank you
Try cleaning the build files (It is in the overflow menu)
Thanks Nick - done this, plus connected the Atom Lite directly to my HA RPi3 serial USB port and it still comes up with the above error message when I attempted to update it (with the entire house’s WiFi disabled, so it wasn’t choosing WiFI to do OTA, but had to try directly). The ESPHHome add-on Web UI terminal window goes through the same process as previously, with the same errors have occurred as in this image from earlier https://cdn.discordapp.com/attachments/1060695866358374471/1060699661863751710/image.png - as I said I am a novice, but it keeps referring to a failure of the C Compiler. Any ideas on how I can get it to have a working C Compiler, or how I can get the correct update file, as it seems that whatever ‘file’ it is sourcing from the internet to update my Atom Lite is itself the problem and corrupted? Thanks for any and all help 
or am i totally on the wrong line of thought?
Did you also update the ESPHome “Dashboard” Add-On to 2022.12.x before trying/running the update on the esphome node itself via the Web-UI/Dashboard?
As a work’a’round you might wanna install the ESPHome “Dashboard” via docker or pip on your workstation and have a try 
Yes he answered that above.
Thanks for the ideas (+ @nickrout) - appreciated.
I’ve def done the following - all of which have failed:
- uninstalled and reinstalled the HA ESPHome add-on and attempted to update the Atom Lite bluetooth proxies via the Web UI. ESPHome version is currently 2022.12.3
- plugged in one of the Atom Lite bluetooth proxies into my Raspberry Pi 3 that is running my HA installation, thereby connecting to the Atom Lite via serial (USB), and after disabling the house’s WiFi (to ensure any communication with the Atom Lite was via the serial connection), attempted to update the Atom Lite
- restarted the Atom Lite with the button depressed during the update process to try to see if that helped the ‘flashing’
- reinstalled the whole BT proxy via ESPHome Bluetooth Proxy
- just now loaded ESPHome onto my desktop via pip - fairly fresh at doing any of this! Can’t seem to type the correct command at my terminal window to activate the ESPHome Dashboard via pip. Anyone aware of what command to type at terminal window once ESPHome has been installed to get the ESPHome Dashboard working locally?
Everytime the same errors end up causing failure - as far as I can see - which is cut and pasted below at the bottom of this post, but seems to be a Compiler problem. Does this mean it’s a problem with my hardware? With ESPHome? With something else?
Now that @bdraco has made some amazing updates to the Bluetooth Proxy setup in HA (see ESPHome 2022.12.0 - 14th December 2022 — ESPHome), and with the hope that minimal programming novices like myself can use these awesome features, I wonder if the best way to solve this for me (and others in the future?) would be for the bluetooth-proxies web-installer site (ESPHome Bluetooth Proxy) to actually facilitate having the latest update loaded at the time of setting up the Atom Lite (and other units). Could this web-installer site be updated to have the latest firmware to mean the proxies are ready-to-go and updated and can then be further updated in the future via WiFi? Or can anyone see what else I can do - being a novice! - to update my Atom Lites to the latest version to ensure their longevity and optimal function?
Reading CMake configuration...
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- The ASM compiler identification is GNU
-- Found assembler: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc -- broken
-- Configuring incomplete, errors occurred!
See also "/data/atom-bluetooth-proxy-06d720/.pioenvs/atom-bluetooth-proxy-06d720/CMakeFiles/CMakeOutput.log".
See also "/data/atom-bluetooth-proxy-06d720/.pioenvs/atom-bluetooth-proxy-06d720/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/tool-cmake/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message):
The C compiler
"/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: /data/atom-bluetooth-proxy-06d720/.pioenvs/atom-bluetooth-proxy-06d720/CMakeFiles/CMakeTmp
Run Build Command(s):/data/cache/platformio/packages/tool-ninja/ninja cmTC_d2942 && [1/2] Building C object CMakeFiles/cmTC_d2942.dir/testCCompiler.c.obj
[2/2] Linking C executable cmTC_d2942
FAILED: cmTC_d2942
: && /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc -mlongcalls -Wno-frame-address CMakeFiles/cmTC_d2942.dir/testCCompiler.c.obj -o cmTC_d2942 && :
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: error loading plugin: /data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
/data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:296 (__project)
CMakeLists.txt:3 (project)
========================= [FAILED] Took 160.92 seconds =========================
anyone out there having these issues or know of a solution?
I’m having the exact same issue, and do not yet have any solution, sorry.
1 Like
It compiles fine here. Esphome-dev via the addon on x86-64. I downloaded the yaml from github. This is the output from compiling the binary for modern format INFO Reading configuration /config/esphome/m5stack-atom-lite.yaml...INFO Gener - Pastebin.com and for legacy format INFO Reading configuration /config/esphome/m5stack-atom-lite.yaml...INFO Gener - Pastebin.com
EDIT: I did make clean between the two compiles. Thinking the only difference in our setups is likely to be the processor we are compiling on?
Hi @nickrout
Thanks for looking into it - appreciated.
For your modern format post, line 126 is where it all fails for me.
Could you please post the downloaded yaml file that you used from github - being a novice I am wondering how I can fix it, and with this, I’ll use the ESPHome Web interface and install it and see how I go?
It seems that with my setup it’s just not finding what it needs to find from the internet to update successfully, so I am happy to use the yaml file you successfully used
Does that sound OK?
Thanks for any and all help.
Cheers
I used the file that is on GitHub. The repo is on the ESPHome Bluetooth Proxy site and the yaml file is here bluetooth-proxies/m5stack-atom-lite.yaml at 28d6e65141bda9b69bf3eb91f625250b4619154f · esphome/bluetooth-proxies · GitHub
I could build a binary for you if you like. Let me know. I’ll leave the WiFi details blank.
nickrout, I’m having the same problem compiling Bluetooth proxy. I could use a bin file. I could email you my simple yaml file if you would be willing to help. Had this working awhile back but now it won’t build. Thanks in advance. [email protected]
Thanks so much @nickrout for the kind offer - yep I’ve no idea how to build the binary file (which I presume is the file i’d use in the ESPHome Web interface to update the Atom Lite BT proxy after creating it on ESPHome Bluetooth Proxy), so if you could create the update file that’d be greatly appreciated - cheers!
I have bookmarked this with a reminder for the weekend, a bit busy right now sorry.
No worries - all help appreciated, and totally understand any assistance is a bonus - take your time thanks again, cheers