-
-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
ESP device won't update to 2024.6.0 #120005
Comments
Hey there @OttoWinter, @jesserockz, @kbx81, @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) esphome documentation |
Me too 👍 |
Please read the release notes |
Thankyou @jesserockz! That’ll teach me! - Worked perfectly, super simple. This kind of end-user laziness is your punishment for rolling so many seamless updates that I stopped bothering to read the notes on ‘em! :) |
Hi, ota: Validating this yaml succeeded. <<INFO ESPHome 2024.6.1 |
I cannot find an ota: section in my current configuration.yaml (but I do have devices that I have been updating OTA for ages now). It's also unclear to me whether the password is mandatory, and what purpose it serves. For now, I reverted to the backup and will wait to see how this thread pans out. |
@Mascot68 the password is optional. Only the |
Copy: ota: Then save, validate and install |
YES! It worked! Tnx. I didn't do the Install..... stupid! |
@TheFes Wherever it is, I cannot find the file that contains it. I've only found a single configuration.yaml anywhere in the folder structure so far, and it's not in there. There are two other yaml files in the esphome folder, but there's no ota in any of those either. I don't know how to check for inclusion of an online package. If that's a thing, it's not something I knowingly did. I can't remember having done anything in HA more "advanced" than modifying a card's yaml using the built-in editor. When I have some more time I'll update again and try to add the ota section as suggested above to the configuration.yaml and see what happens. I didn't want to do that before, because of the password, but with that confirmed as optional it'll hopefully "just work". :) |
Go to your ESPHome: |
Well, technically ota:
- platform: esphome |
Thanks for the tip! |
I somehow missed that we're talking about the configuration file for the device, not esphome or HA as a whole. Thanks to @velddriel's image, I'm all sorted now. :) |
Thanks for the tip. I was algo getting this error after today after updating. Adding this solved the issue
|
Me too, I get this:
The solution for me was to update the config of my esp home device like this:
|
Ditto here too - blindly updating without checking release notes! Thanks for the pointers to the notes to know you have to add the platform. If you/I viewed the device YAML, it showed the error there too. Thanks - Steve |
I am having the same problem, but I am not able to find the file that I need to modify. I am using home assistant yellow. I am using studio Code Server. I have tried searching for some of the words and am not able to find it. I believe ESPHOME is at 2024.6.1. Bluetooth Proxy.... are at 2024.5.5 to upgrade to 2024.6.1. Is the solution documented here able to fix the problem if I can find where the files I need to update. Thank you, Ray, |
It's on every device YAML file. You need to update each device with the new ota platform. |
I found the yaml files and updated them and the components updated. Thank you very much |
I'm sorry but I'm also having this issue and I can't seem to resolve it. I've added the rota platform to both the devices I have, and updated the yaml to the new dallas_temp thing, but I still can't update them. Any help would be greatly appreciated. I've tried restarting HA in case of that made a difference but it did not. |
Remove safe_mode: true and update your GPIOXX to your GPIO pin that you are using. |
Thank you! They've now updated without issue. I appreciate the straightforward answer |
Seems like a classic case where home assistant should apply an autofix given this was a breaking change. I didn't catch it as the release notes said the config would fail to validate, yet the error message didn't say i had a validation problem. As such i had read the release notes and never linked the two issue in my head. |
Well, maybe it compiles but ota updates when in safe mode no longer works. I always get a can't connect on two different devices.. I havent had a chance to look at the code but I suspect someone didnt do some testing here.... I have "safe_mode:" by itself in the config and have platform: espome for ota. The device does indicate it's in safe mode. I can ping it but no ota. Edit, this issue happens when using an "on_begin:" action under ota. I've posted a separate issue here: esphome/issues#5976 |
after adding the ota to all of my devices I now do not get sensor updates, then all show as Unavailable in Developer tools |
The problem
I updated the general ESP Home earlier, but now I have 3 ESP devices that show as needing to be updated (as usually happens). When I ckick on UPDATE, I get the error:
If I try to go through the ESPHOME console, I get:
What version of Home Assistant Core has the issue?
2024.6.3
What was the last working version of Home Assistant Core?
2024.6.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
ESPHome
Link to integration documentation on our website
https://www.home-assistant.io/integrations/esphome
Diagnostics information
5c53de3b_esphome_2024-06-20T03-12-33.017Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: