ESP device won't update to 2024.6.0 about core

[velddriel]

@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:

[jesserockz]

Please read the release notes
https://esphome.io/changelog/2024.6.0#ota-platforms

[TheFes]

Well, technically ota: expects a list, so this would be better (without the - it will work until you want to add a 2nd OTA platform):

ota:
  - platform: esphome

[clucluclu]

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! :)

[clucluclu]

Me too 👍

[Mascot68]

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. :)

[velddriel]

Well, technically ota: expects a list, so this would be better (without the - it will work until you want to add a 2nd OTA platform):

ota:
  - platform: esphome

Thanks for the tip!

[velddriel]

Hi, I added this to the configuration yaml of my ESP32-S3-BOX-3.
ota:
platform: esphome
Validating this yaml succeeded. Try the OTA update ESPHome 2024.6.1. again, but now the log shows this. Anyone an idea?
<<INFO ESPHome 2024.6.1 INFO Reading configuration /config/esphome/esp32-s3-box-3-05a480.yaml... INFO Updating https://github.com/esphome/esphome.git@pull/5230/head WARNING GPIO0 is a strapping PIN and should only be used for I/O with care. Attaching external pullup/down resistors to strapping pins can cause unexpected failures. See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins INFO Starting log output from 192.168.178.45 using esphome API INFO Successfully connected to esp32-s3-box-3-05a480 @ 192.168.178.45 in 0.323s WARNING esp32-s3-box-3-05a480 @ 192.168.178.45: Connection error occurred: esp32-s3-box-3-05a480 @ 192.168.178.45: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (ESPHome Logs 2024.6.1). WARNING Can't connect to ESPHome API for esp32-s3-box-3-05a480 @ 192.168.178.45: esp32-s3-box-3-05a480 @ 192.168.178.45: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (ESPHome Logs 2024.6.1). (HandshakeAPIError) INFO Trying to connect to esp32-s3-box-3-05a480 @ 192.168.178.45 in the background>>

Copy:

ota: platform: esphome

Then save, validate and install

YES! It worked! Tnx. I didn't do the Install..... stupid!

[chunkysteveo]

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

[rlknappjr]

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

[chunkysteveo]

Remove safe_mode: true and update your GPIOXX to your GPIO pin that you are using.

[Nabys]

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

[scyto]

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.

[home-assistant]

Hey there @OttoWinter, @jesserockz, @kbx81, @bdraco, mind taking a look at this issue as it has been labeled with an integration (esphome) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of esphome can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign esphome Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

esphome documentation
esphome source
_{^{(message by IssueLinks)}}

[velddriel]

Hi,
I added this to the configuration yaml of my ESP32-S3-BOX-3.

ota:
platform: esphome

Validating this yaml succeeded.
Try the OTA update ESPHome 2024.6.1. again, but now the log shows this.
Anyone an idea?

<<INFO ESPHome 2024.6.1
INFO Reading configuration /config/esphome/esp32-s3-box-3-05a480.yaml...
INFO Updating https://github.com/esphome/esphome.git@pull/5230/head
WARNING GPIO0 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Starting log output from 192.168.178.45 using esphome API
INFO Successfully connected to esp32-s3-box-3-05a480 @ 192.168.178.45 in 0.323s
WARNING esp32-s3-box-3-05a480 @ 192.168.178.45: Connection error occurred: esp32-s3-box-3-05a480 @ 192.168.178.45: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (ESPHome Logs 2024.6.1).
WARNING Can't connect to ESPHome API for esp32-s3-box-3-05a480 @ 192.168.178.45: esp32-s3-box-3-05a480 @ 192.168.178.45: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (ESPHome Logs 2024.6.1). (HandshakeAPIError)
INFO Trying to connect to esp32-s3-box-3-05a480 @ 192.168.178.45 in the background>>

[Mascot68]

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.

[TheFes]

@Mascot68 the password is optional. Only the platform is required.
The ota: component must be defined somewhere in your configuration. Maybe included through an (online) package.

[andiukas]

Hi, I added this to the configuration yaml of my ESP32-S3-BOX-3.

ota:
platform: esphome

Validating this yaml succeeded. Try the OTA update ESPHome 2024.6.1. again, but now the log shows this. Anyone an idea?

<<INFO ESPHome 2024.6.1 INFO Reading configuration /config/esphome/esp32-s3-box-3-05a480.yaml... INFO Updating https://github.com/esphome/esphome.git@pull/5230/head WARNING GPIO0 is a strapping PIN and should only be used for I/O with care. Attaching external pullup/down resistors to strapping pins can cause unexpected failures. See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins INFO Starting log output from 192.168.178.45 using esphome API INFO Successfully connected to esp32-s3-box-3-05a480 @ 192.168.178.45 in 0.323s WARNING esp32-s3-box-3-05a480 @ 192.168.178.45: Connection error occurred: esp32-s3-box-3-05a480 @ 192.168.178.45: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (ESPHome Logs 2024.6.1). WARNING Can't connect to ESPHome API for esp32-s3-box-3-05a480 @ 192.168.178.45: esp32-s3-box-3-05a480 @ 192.168.178.45: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (ESPHome Logs 2024.6.1). (HandshakeAPIError) INFO Trying to connect to esp32-s3-box-3-05a480 @ 192.168.178.45 in the background>>

Copy:

ota:
platform: esphome

Then save, validate and install

[Mascot68]

@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". :)

[kdober]

Thanks for the tip. I was algo getting this error after today after updating. Adding this solved the issue

ota:
  - platform: esphome

[mabusdogma]

Me too, I get this:

INFO ESPHome 2024.6.1
INFO Reading configuration /config/esphome/led.yaml...
Failed config

ota.unknown: [source /config/esphome/led.yaml:8]
  
  'ota' requires a 'platform' key but it was not specified.
  password: xxxxx

The solution for me was to update the config of my esp home device like this:

ota:
 - platform: esphome
   password: "xxxxxxxxxxxxxxxx"

[rlknappjr]

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,

[chunkysteveo]

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.

[Nabys]

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.

[Dilbert66]

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

[ramdisk00]

after adding the ota to all of my devices I now do not get sensor updates, then all show as Unavailable in Developer tools