Projects using ESP-IDF don't build with the 2024.12 betas #42
Comments
|
To use the s3 boxes with ESPHome 2024.12 or above will require some reworking of the audio drivers due to the craziness of esp-adf and esp-idf. Work has begun on this to remove the esp-adf dependency but is not complete yet. There is no timeline available. Jesse |
|
I see the same behavior with the M5Stack Atom Echo clean build (not an ESP32-S3). Is that expected? My Onju devices fail the same way, but that's another ESP32-S3. Basically, all of my assist devices fail in the same way now with the beta. |
|
defining framework:
type: esp-idf
version: 4.4.8
platform_version: 5.4.0 |
That fixed it for me on the Atom echo. |
Where did you set this? |
|
In your .yaml config file. |
|
my Echo suffers this too I am afraid, and I am discussing this in Discord, but not been able to solve it yet (clean build files from Esphome dashboard ). my yaml is so where do I add the |
|
if using the adopted firmware from a project install and don't have the esp32:
board: m5stack-atom
framework:
type: esp-idf
version: 4.4.8
platform_version: 5.4.0also for reference the full device config can be found here (without edited framework) -> https://github.com/esphome/wake-word-voice-assistants/blob/main/m5stack-atom-echo/m5stack-atom-echo.yaml |
|
thanks BB, for now I have removed and reinstalled the Add-on, as I was instructed that should clean the build files (and probably downloads them again?) I had been relocated to https://github.com/esphome/firmware/tree/main/voice-assistant/ under the link to GitHub, so that seems to be not the same as your link above. all in all this seems way more involved, than simply hitting the update button, I hope this process will get some love. Not a tinkerer myself at all, not a complete noob either.. |
|
Pinning the idf version, as suggested in this comment, does work for me, but I then get a warning in the logs. |
|
@eamonnsullivan the warning can be ignored it is just pointing out that the version you have defined is not the same as the one used by default. |
|
fwiw, I didnt manage to update the Atom Echo and ignored the repair in Home Assistant for now. so, today, after updating Esphome (why on earth was that renamed to 'ESPHome device builder' .....) I tried it once more and at first got this again but somehow it didnt abort, and finished after all with 
device seems to be working alright, and can even command the assist got to say I am glad its working again, but all in all a mixed user experience (understatement) |
|
This: fatal: not a git repository (or any parent up to mount point /) This applies to both 2024.12.1 and 2024.12.2 updates |
I've just re-tried to install on my S3Box3 and got an error again, although a different one, it got a lot further into the compiling before it failed. The log is below.
|
|
@Clasper101 try doing a clean build files - from the 3 dot menu of the device card in the ESPHome dashboard and then try to recompile |
|
Nope, cleaning build files does not work. I'm also experiencing the problem on newest 2024.12.2 release, cleaned build files and restarted the add-on, host os, etc. Here are my logs: |
|
With the extra yaml code from above and a reboot I have managed to update my Atom Echoes and S3 Box 3. |
|
The proposed YAML in #42 (comment) did not fix it for me. I'm getting the same error as @Mis1ify in #42 (comment), and also have the latest esphome 2024.12.2. No workaround yet. I wanted to revert to an older version, but unfortunately there doesn't seem to be a way to install a previous version of esphome with brew: $ brew install [email protected]
Warning: No available formula with the name "[email protected]".
==> Searching for similarly named formulae and casks...
Error: No formulae or casks found for [email protected].$ brew search esphome@
==> Formulae
esphome ✔
==> Casks
epichrome |
|
Reverting back to 2024.11.3 fixed the issue for me. I figured out how to revert to a previous version on Homebrew. I had to create a tap and extract the old version: brew uninstall esphome
brew tap-new fortuna/esphome-versions
brew extract --version 2024.11.3 esphome fortuna/esphome-versions
brew install fortuna/esphome-versions/[email protected]Credit: https://stackoverflow.com/a/64125796/1234111 @jesserockz would it make sense to revert 2024.12? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
None of my Assist projects build with the ESPHome 2024.12 betas. They all fail with a build error in ESP-IDF related to the JSMN component.
Which version of ESPHome has the issue?
2024.12.0b0/b1/b2
What type of installation are you using?
Docker
Which version of Home Assistant has the issue?
2024.12.0b3
What platform are you using?
ESP32-IDF
Board
ESP32-S3-Box-3
Component causing the issue
jsnm
YAML Config
Anything in the logs that might be useful for us?
Additional information
If I install ESPHome 2024.11.3, the same projects build and install just fine. I get the same failure if I just try to build exactly the released config from https://github.com/esphome/wake-word-voice-assistants/blob/main/esp32-s3-box-3/esp32-s3-box-3.yaml as is.
The text was updated successfully, but these errors were encountered: