-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to compile for M5Stack Atom Echo #286
Comments
The same issue here |
The same issue here ESP32-S3-Box 3 |
I am M5Stack Atom Echo too, stuck here:
|
I got this error:
|
My M5Stack Atom Echo also failed to update/install.
|
I think there are updates in the back end, as I now have a new error:
|
a workaround that seems to help me to unblock it is adding this inside the esp32 section
|
The workaround worked for me too.
|
Where should I add this? Placing it in the devices yaml file from the esphome gui I get "Component not found: framework." |
I added it at the end, it needs to go under the esp32 section as I didn't have one for my yaml:
|
That worked like a charm. Thank you! |
Got the same issue with my RaspiAudio Muse Luxe |
worked for me too, but had this : |
Adding it to my M5Stack Atom Echo worked, but it didn't work for my ESP32 S3 Box3, fatal: not a git repository (or any parent up to mount point /) Has anyone got the S3 Box 3 to update successfully? |
@Clasper101 work fine for my ESP32S3 box 3 |
Thanks, this worked for my M5Stack Atom Echo too! |
I have the same issue. |
I also have same issue. The lines were already in the YAML, so I added |
...same issue here |
running ESPHome version 2024.12.2 inside HA 2024.12.5 with the same error.
and luckily this helps, I can compile and flash now. |
Workaround fixed the issue for me as well, hoping this gets appropriately resolved soon. |
This workaround fixed the issue but is it normal that it takes a long time to compile around 25 minutes |
Same here. |
That seems excessive, I've just moved mine to a new HA instance and the compiling took 319 seconds. |
Do you have a lot of resources assigned to the vm? I set 10gb of ram and 4cpu |
I'm using HAOS on a mini pc (N100) with 16gb of ram. |
Then I don't understand my computer is more powerful than a mini PC. Could you post your yml? |
Here is my yml for an Atom Echo wifi: esp32: and for an ESP32 S3 Box 3 substitutions: wifi: esp32: Use address for when it doesn't automatically connect to wifi after compiling. |
So, if I wanted to change the wakeword to "hey jarvis", would I just edit the @Clasper101 .yaml as above to the following?
|
@adoucette, that's a good question. I haven't tried to change it yet. |
Even with you config it takes a lot to compile |
The change that @GitHubxtsnl suggested fixed it for me. Is it possible that the adf PR is not completely compatible with the esp-idf 5.1.5 version? @jesserockz might PR5230 need to be tweaked? Like around |
Adding this to the ESP32 section worked for me as well. version: 4.4.8 |
I'm experiencing the same issue, but I had to use the packages:
m5stack.atom-echo-voice-assistant: github://esphome/firmware/voice-assistant/m5stack-atom-echo.adopted.yaml@main
esp32:
framework:
type: esp-idf
version: 4.4.8
platform_version: 5.4.0 |
I can only assume, that whoever used to work on Echo is now working on the new Home Assistant Voice PE. And s3 box before that. I am waiting patiently for them to release the next ESPHome that should include the new ESP-IDF MediaPlayer that can use I2S Speaker as platform. This is what I see implemented in the code for Home Assistant Voice PE, but it is missing in current, beta and dev version of ESPHome (but it is mentioned as "planned to use psram with IDF" in Music Assistant docs and in some reference docs for mediaplayer in GitHub). Similarly, the incompatibility with ESP-IDF 5.1.5 is also fixed in Home Assistant Voice PE, but not in ESPHome. So someone should port those fixes. But I guess this can happen only when the commercial product is sold out and stable enough to start working on the next esphome... so I will wait and hope my echoes will work fine till then |
I'm having the same issue and trying to debug it. It seems that the package is referring to a library that has been deprecated and no longer exists. I'm trying to find an old version of the library to see what it was and why some are able get it from the by overriding by referring to the expressif libraries. |
Running esp32 s3 and today failed to install code as it could not connect to a git hub site with error 500. Added the entries above viz version 4.4.8 and platform version 5.4.0 seems to have fixed things. Interestingly the issue only presented itself today. |
I was having the same issue and by using:
I was able to prepare a download file to install on my Atom Echos |
this worked for me |
Upgraded my Home Assistant ESPHome to 2024.12.0 and I cannot compile the firmware for my M5Stack Atom Echo - I have other ESPHome devices that have all been successful so hopefully my environment is ok.
The messages during the compile are:
My yaml config for the device, working fine until now, is:
The text was updated successfully, but these errors were encountered: