-
-
Notifications
You must be signed in to change notification settings - Fork 253
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
Bug
Can't build with ESPHome 2024.3.0 because remote_package doesn't update
#1975
Comments
Please notice that I have @main on the remote package definition (so it should download the latest version), but I still get this in the ESPHome build dialog:
Notice the Reverting changes line that seems to reset the head to a much older version, so I can't fetch the version v4.3.1 that should have fixed this issue. I don't understand where this revert comes from. |
Please see here. It seems the I've cleaned the project but it didn't work. Changing the |
Bug
Can't build with ESPHome 2024.3.0Bug
Can't build with ESPHome 2024.3.0 because remote_package doesn't update
Same issue here. Home Assistant Core 2024.3.3 I have multiple panels and they now require TTL flashing 😅 so I want to stay at the latest arduino version until I have time to flash each one to idf but I want to keep updated with ESPHome in the meantime. Release v4.3.1 mentions a fix that I believe could be related to this issue, and if true I think that all previous versions of NSPanel_HA_Blueprint are broken: https://github.com/Blackymas/NSPanel_HA_Blueprint/releases/tag/v4.3.1
|
See #1821 for how to build a ESP-IDF version that's compatible with your Arduino's partition layout. That's what I'm using and it's working fine. The issue in ESPHome has been identified. It's mainly due to ESPHome silently reverting the package's git repository to the previous version when it encounter a YAML error on the new version. But since it doesn't tell you the error, you can't fix it and you're struck to a non functional system. On my case, it was the line
That caused the breakage. The file was moved between version v4.2.6 and v4.3.1 so the generated YAML with the old path failed to build. Update the path to the new version and it should work. As long as you get a log from your build that says:
Your YAML is failing, this line shouldn't be there. |
I just removed the first panel from the wall and setup my tools 😅 I'm going to flash them because I'll have to eventually, but thanks for the tip! |
What's the issue? Why am I getting this error, and how can it be resolved?
|
Personally I ended up upgrading all my panels (with TTL) to the latest version |
@ali96adil Check the release notes: https://github.com/Blackymas/NSPanel_HA_Blueprint/releases/tag/v4.3.0 |
You probably are using advanced mode in YAML. The files have changed position so you need to update the file location. In case of doubt, just replace the |
I'm also getting this "Reverting changes" behaviour in a completely different compile (https://github.com/jaymunro/esphome_firmware/blob/continued-conversation/wake-word-voice-assistant/esp32-s3-box-3.yaml). It's making testing very troublesome as no errors are reported anymore while developing. It strikes me this new behaviour is desirable for end users in a production environment, but there must be some new flag to turn this off, surely. |
We have discussed this issue on Discord. There's no message (and no way to have one) in current code, except by going into the docker and deleting the Git repository for the package. If a repository exists, its current HEAD is remembered and restored upon error. If it doesn't exist, this doesn't happen and you get the error reported. |
I found another work around was to create another branch and update the reference in ESPHome, but it's not practical for the long term. |
Same problem here. I don't knowhow i can fix it. There is solution for this issue? ESPHome 2024.3.1 /data/packages/566b10a3/advanced/esphome/nspanel_esphome_core.yaml: In lambda function: |
Change your ref in your YAML from |
Are you still having these issues with v4.3.2? For my own reference, this is the related Discord discussion around this: https://discord.com/channels/429907082951524364/524177279270780928/1221336605093269535 |
Could you please share the logs before this error message. |
same here after changing ref, commenting out nspanel_advanced, cleaning build files and trying to build again:
|
Here is log before cleaning build files: And full log after cleaning buld files for the nspanel: If i can replace some file or if you want me to check some solution feel free. I'm ready. I want to update because i'm after big chcange in my home and i try to prepare new configuration on the newest version. |
@gednet, by looking at your logs I just realized you are using Arduino, so this is different than the original case which was ESP-IDF. Do you mind sharing your panel's yaml? Please remove any sensitive info before sharing. |
The same problem after several attempts did not solve the problem logs_nsali_run.txt |
@ali96adil, could you please share your panel's yaml? Please remove any sensitive information before sharing. |
|
Your logs shows a mix of frameworks and tags used, so I believe you have tried different things, right? |
Ok. But i don't understand why still is arduino framework, when in nspanel_esphome_core.yaml from lin no 103 is right definition esp-idf framework type. Here is my original yaml
After i have read your suggestion i put in my yaml all framework definition from nspanel_esphome_core.yaml. But compilation still gave me the same error. |
Could you please try changing from |
Nothing changed :( If i may check or change something i'm ready. |
That doesn't work on ESPHome. He has to change the ref to refresh, the refresh time is ignored upon error. |
I have the same problem and cannot build |
Please try changing from |
TFT Version
latest
ESPHome Version
latest
Blueprint Version
latest
Panel Model
EU
What is the bug?
When trying to build with latest ESPHome version, it fails with this log:
Steps to Reproduce
No response
Your Panel's YAML
ESPHome Logs
No response
Home Assistant Logs
No response
The text was updated successfully, but these errors were encountered: