I missed it in the release notes, but there’s a breaking change in the ota component in ESPHome 2024.6.0. I figured I’d save folks some time and share the fix here.

If your OTA config looks like this;

...

ota:
  password: "*************"
  num_tries: 3
  safe_mode: on

...

Now you’ll need to add a platform key to start a list, and either comment out the other option or move them to a new component.

...

ota:
  - platform: esphome
    password: "*************"
  #num_tries: 3
  #safe_mode: on

...

edit: Here’s the PR introducing this change https://github.com/esphome/esphome/pull/6459

  • @ikiddEnglish
    5•5 months ago

    The hero we need.

  • AlchemyEnglish
    4•5 months ago

    Funnily enough I was just about to upgrade devices, thanks for this!

    • SolidGrueOPEnglish
      5•5 months ago

      Oops! Good eyes, and thanks! Typing yaml on mobile is squinty business. Fixed in the main post

  • @[email protected]English
    2•5 months ago

    Cheers mate - no doubt I would’ve scratched my head for a bit when I do my weekly container updates tomorrow.

  • @MNLFNUT8YGEnglish
    2•5 months ago

    Yeah this solve it. I didn’t got any release notes from the Home Assistant EPSHome update tho.

    • SolidGrueOPEnglish
      2•5 months ago

      Seems It was actually 2024.6.1 that introduced the change. Not sure where in this release notes it said it was a breaking change, but

      I’m all turned around. I updated the main post with the link to the PR and I had the right version from the get-go.