homeassistant

11701 readers

94 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago

MODERATORS

[email protected]

Breaking change in ESPHome 2024.6.0 ota component (lemmy.world)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

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

top 9 comments

sorted by: hot top controversial new old

[–] [email protected] 5 points 2 months ago

The hero we need.

[–] [email protected] 4 points 2 months ago

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

[–] [email protected] 4 points 2 months ago* (last edited 2 months ago) (1 children)

~~You have a typo: platform: esphome.~~

Thanks for posting, good catch!

[–] [email protected] 5 points 2 months ago* (last edited 2 months ago) (1 children)

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

[–] [email protected] 3 points 2 months ago

Heh, typing YAML anywhere is squinty business. :⁠-⁠)

[–] [email protected] 2 points 2 months ago

Thanks for posting this!

[–] [email protected] 2 points 2 months ago (1 children)

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

[–] [email protected] 2 points 2 months ago* (last edited 2 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.

[–] [email protected] 2 points 2 months ago

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