Oh well. that aged like milk, since the 2024.6.0 was now rolled out - and somehow I missed this as well in the change notes, before updating my HA instance:
And actually it is a breaking change, because without a manual adaption of the configuration updates of ESPHome devices using OTA isn’t possible anymore.
Here’s the relevant summary, so other folks who stumble over that issue don’t have to stupidly dig into github pull-requests or discord chat protocols:
[…] if your original configuration looked like this:
ota:
password: "xxxxxxxxxxxxxxxx"
num_attempts: 3
safe_mode: no
…you now need to arrange it like this:
ota:
- platform: esphome
password: "xxxxxxxxxxxxxxxx"
num_attempts: 3
safe_mode: no
No other changes are required to continue using OTA and you will be able to update your devices in the same manner as before.
Although I don’t know if the documentation in the pull-request is outdated, because I updated my sensor config to, which works:
ota:
platform: esphome
password: ...
(for the untrained eye: it is not a list in my config, as mentioned in the pr-doc, see the missing “-” in front of the “platform” attribute, and I haven’t tried it as a list since I missed that myself when changing the configuration → but hey, it works on my HA instance)
Edit/Add: I am warming up this thread, because it was the only google search result when searching for the given error message “ota requires a platform key but it was not specified”, and I guess others will stumble over this as well.