Heads up for Esphome 2024.6

ESPHome
1

In esphome 2024.6 the ota configuration has changed, and it you have ota: in your yaml file it won’t compile without fixing.

The old invocation was

ota:
  password: secretstuff

You now need to add platform, so it will look like this:

ota: 
  - password: secretstuff
    platform: esphome

this will get you there. There is now also a platform: http_request as well, hence the need for a change.

This is dealt with in the changelog ESPHome 2024.6.0 - 19th June 2024 — ESPHome , but I just wanted to post to help anyone who didn’t read it.

Brought to you by your team of regulars.

48 Likes
2

Thanks that worked for me .

4

That is not all. I use a dallas sensor and i need to replace that with one_wire.
However this is generating other errors. Still searching what changed.

5

See: https://esphome.io/changelog/2024.6.0.html#wire

2 Likes
6

Thanks, did not find it yet.

7

I am gonna wait a while until updating, like two or three weeks

8

What do I change this to?

ota:
  safe_mode: true
  password: !secret ota_password
  on_begin:
    then:
      - logger.log: "OTA start"
  on_progress:
    then:
      - logger.log:
          format: "OTA progress %0.1f%%"
          args: ["x"]
  on_end:
    then:
      - logger.log: "OTA end"
  on_error:
    then:
      - logger.log:
          format: "OTA update error %d"
          args: ["x"]

If I add “platform” in any position or format I get this at the top of the editor in Home Assistant, e.g.:

ota:
  platform: esphome
    safe_mode: true
  password: !secret ota_password
  on_begin:

image
image1175×225 10.4 KB

9

Edit: Deleted to avoid confusion. See below for correct config: Heads up for Esphome 2024.6 - #13 by Troon

10

image
image1101×178 6.29 KB

11

Edit: Deleted to avoid confusion. See below for correct config: Heads up for Esphome 2024.6 - #13 by Troon

12

How is update_interval:30 used now with 1-wire?

13

safe_mode is its own component (ref):

ota:
  - platform: esphome
    password: !secret ota_password

safe_mode:

dallas becomes one_wire like this (ref):

one_wire:
  - platform: gpio
    pin: D7

and the sensors change to dallas_temp (ref) (for temperature sensors like DS18B20) including the update_interval here rather than under one_wire:

sensor:
  - platform: dallas_temp
    update_interval: 30s
    address: ...
1 Like
14

Ah, so that is required in addition to this?

https://esphome.io/components/ota

Screenshot 2024-06-20 at 19-47-16 ESPHome OTA Updates — ESPHome

EDIT: that document is out of date. Do not use it.

15

What’s with dallas old option “index” ? It’s unknown feature now…?
i’ve had setup below, since i have three dallas sensors, but each on it’s own gpio, so i don’t use dallas addresses.

Also: has “update_interval” moved from “dallas” config to “platform: dallas_temp” ?

  - platform: dallas
    index: 0
    name: "Temperatura sanitarne vode"
    dallas_id : dallas_hub_1
    accuracy_decimals: 0
    filters:
      - offset: 1.0
16

Ahh… wondering what the problem with my update was. Thanks for the post.

17

Yes. Just changed all of mine:

sensor:
  - platform: dallas_temp
    address: 0x1a3c01e07605b228
    name: "Tank Temperature"
    update_interval: 3s
    filters:
      - sliding_window_moving_average:
          window_size: 10
          send_every: 10
          send_first_at: 1

  - platform: dallas_temp
    address:  0x58000000167d7228
    name: "HP Inlet Temperature"
    update_interval: 3s
    filters:
      - sliding_window_moving_average:
          window_size: 10
          send_every: 10
          send_first_at: 1
2 Likes
18

No, that doc is out of date.

image
image1083×143 13.1 KB

1 Like
20

Hm… when entering exactly above lines then line “safe_mode: true” is underlined with red, error is that safe mode has moved from ota to it’s own component…

21

Yes the docs are incorrect and need updating. See the post directly above yours by Troon.