WTH: Why with every ESPHome update, do I get prompted to update all my ESPHome devices right after

Month of "What the heck?!"
1

I don’t see the point of needing to update every single board every single time. It can be a time consuming task even with the update all button in espHome with 10+ boards.

Some updates are very minor or add something that has no impact or additional functionality to the sensors I am using on each board. Most of my stuff is set it and forget it. But I do like to keep the ESPHome app update to the most recent.

I would love a way to possibly tag individual boards as ignore all updates, accept all updates, or if it could know the specs, connected sensors, and/or config/yaml, update if there is anything that the specific board would benefit from.

2

You can already disable all updates by disabling the update entity for the esphome device.

1 Like
3

I setup a Automation that updates mine automatically. I rarely get breaking changes.

I have three Automation groups,
Infra (things like Power Monitor, temp sensors etc)
switches (all of my Shellys)
lights (all of the lights)

I do it like this because I have had in the pass, the Update All button break a few bulbs because a switch was updating at the same time as the same light was updating.

alias: Auto-update - ESPHome devices - Lights
description: ""
mode: single
triggers: []
conditions: []
actions:
  - variables:
      suffixes:
        - light
        - lamp
        - light_1
        - light_2
        - light_3
        - light_4
        - light_5
        - light_controller_1
        - light_controller_2
        - light_controller_3
        - light_controller_4
        - light_controller_5
  - repeat:
      for_each: "{{ suffixes }}"
      sequence:
        - variables:
            suffix: "{{ repeat.item }}"
        - repeat:
            for_each: >-
              {{ states.update | selectattr('state', 'eq', 'on') |
              selectattr('attributes.title', 'match', 'ESPHome') |
              selectattr('attributes.auto_update', 'eq', false) |
              selectattr('attributes.in_progress', 'eq', false) |
              selectattr('entity_id', 'match', 'update.*_' + suffix +
              '_firmware') | sort(attribute='attributes.installed_version') |
              map(attribute='entity_id') | list }}
            sequence:
              - target:
                  entity_id: "{{ repeat.item }}"
                continue_on_error: true
                action: update.install
1 Like
4

You don’t need to. Unless the release notes contain a breaking change for a component you use. In that case it is better dealt with now while the instructions to do so are easy to find (in the current release notes).

As Petro said, just disable the update entities for each of your devices and you won’t be nagged.

All you need to do is spend 30 seconds each month scanning the release notes for something that may affect you.

This is what I do. It is very easy and not at all time consuming.

3 Likes
5

That’s solved quite some time ago. Just disable this in esphome addon’s configuration page and update entities will be disabled by default:

image
image1049×91 7.05 KB

6

Yeah i do skip a lot of updates so that’s why i thought i could ignore majority of updates. Thanks for the feedback and i will be doing this going forward! I didn’t realize it was triggering based of the entity so i learned something new!

1 Like