Constant updates, skip option

ESPHome
81

Maybe stupid question, but where and what is the update sensor? Where can I find it to unable the node updates three times in two weeks, but still can update esphome, and other updates from HASS still show?

82

It’s an entity that creates the notifications that felicitate the updates for a device. Disable the entity, remove the notification.

Update entities are the same as any other entity. You find them with the related device. If by chance you can’t find the device it’s coming from, you can always look for entities in Developer Tools → States page.

1 Like
83

everyone use this service call to skip all updates from esp home devices

service: update.skip
data: {}
target:
  entity_id: >
    {{ states.update | 
     selectattr('state', 'eq', 'on') | 
     map(attribute='entity_id') | 
     select('in', integration_entities('esphome')) | 
     list }}
3 Likes
84

This approach made the most sense. I can skip with one click but still see that updates are available until I do. Thanks!

85

Thanks!
However, update sensor remains enabled, so i guess that at next esphome update sensor will again show tthe need for an update (or will it?). Would be possible to use some kind of a script which would change all esphome update entities to disabled? (automatically, if possible, of course… :wink:)

86

I made the following automation to skip all ESPHome and MQTT Updates. Just edit integrations List. @Protoncek

  automation:
  - id: 13b62e56-d3f1-47a2-a558-cec4660119e4
    alias: skip selected Updates
    description: ""
    mode: restart
    variables:
      integrations:
        - esphome
        - mqtt
      entities: >
        {%- set ns = namespace(entities=[]) -%}

        {%- for x in integrations -%}
        {%- set entity = integration_entities(x)
        | select('match', 'update.')
        | list -%}

        {%- set ns.entities = (ns.entities + entity) -%}
        {%- endfor -%}

        {% set list = ns.entities %}

        {%- set ns = namespace(entities=[]) -%}

        {%- for x in list -%}
          {% if states(list[loop.index-1]) in 'on' %}
            {% set ns.entities = ns.entities + [x] %}
          {% endif %}
        {% endfor -%}

        {{ ns.entities }}
    trigger:
      # Trigger every Minute
    - platform: time_pattern
      minutes: "/1"
    condition:
    - alias: "update available?"
      condition: template
      value_template: "{{ entities|length > 0 }}"
    action:
      - service: update.skip
        target:
          entity_id: >
            {{ entities }}
1 Like
87

Wow, thanks a lot! So, if understand correct this should “delete” update warnings for esphome (and mqtt) when they popup… nice!

88

Finally, no more EspHome device update notifications. Soo annoying- what were the devs thinking !?

Automation Editor:

alias: ESPHome Update Skip All
description: ""
trigger:
  - platform: time_pattern
    minutes: /1
condition: []
action:
  - service: update.skip
    data: {}
    target:
      entity_id: |
        {{ states.update | 
         selectattr('state', 'eq', 'on') | 
         map(attribute='entity_id') | 
         select('in', integration_entities('esphome')) | 
         list }}
mode: single
2 Likes
89

They were thinking to notify you about an update :bulb:

It’s the same when a new HA core is released for example - you get notified about the update :speech_balloon: (that’s very common thing in the modern computer world - otherwise you just directly do auto-updates but that’s not really that good for HA related stuff as things might break if you don’t read change logs! :page_with_curl:)

You can also disable esphome updates notifications with a simple toggle switch instead creating an automation… but that might be to easy and not worth the rant :joy:

90

No. Embedded devices shouldn’t be updated 3 times a month. Updates should only be for security or required features.

Theyre not designed for constant updates. Flash wears out; not a problem on a hdd with wear protection, but on an Embedded device its a no-no.

How can all esphone device update notifications be disabled with a simple toggle whilst leaving esphome addon update notifications on? If thats possible the solution should be mentioned here.

91

Disable the update entity for the device. The update entity for the addon is handled by the supervisors integration.

image
image1701×796 66 KB

You’re really blowing this out of proportion. In fact, this is the first time I’ve even tried it… by simply using the menus provided in home assistant. Sometimes it pays to click around to discover things.

3 Likes
92

Yeah, right… say that i have 50 or even 100 esphome modules. In this case i can only update these modules 24/7, no eating, sleeping, working….
Don’t fix if it’s not broken! The golden rule! I only update my esp’s if i need some changes, fixes or if it’s breaking change.

1 Like
93

It’s like any other device in HA that has a firmware update. You can disable the firmware (update entity), see my previous post. It’s very simple. It’s so simple, there’s no need for a debate.

94

And who is forcing you doing this updates? By default you get a notification - that’s all. Same with HA (core) for example, what you do with this information is your own beer :beer:

You might have any link backing up your speculations with esp’s dying like flies? :fly: Like in the esphome forums or discord maybe? Any one wearing out their flash? :hammer:

Last knowledge I had saved was the flash chips used in esp’s have minimum 100.000 (one hundred thousand) write cycles - Meaning you can flash a new firmware, every day for over 250 (two hundred fifty) years and it should still not be worn out. :bulb:

You might confuse the type of flash cells with the ones commonly used in SSD’s! For example some MLC NAND only allows a few thousand writes :brain:

I know it’s hard, but the solution includes the search engine and a little bit of commitment - unsubstantial ranting on the other is much easier! :face_with_symbols_over_mouth:

It’s only a notification (which can be easily turned off), you are not forced to update. Also you don’t need to stop eating, sleeping or even working. It’s your own decision what to do with this notifications (same for HA). If you don’t need them you can easily turn them off :point_down:

Still running HA 0.78 - right? :joy:

95

Yeah, it’s only a notification… or 100 of them. And then i will quite easily find an important update notification among those 100 useless ones, right?
I’m only saying that by default this notification should be disabled, not enabled. Yes, they can be turned off easily. But, as i already said: esp modules are not needed to be updated regularly, so it would be quite more productive and easier just to turn on a few ones which i do want a notification then turn off hundreds of them.

Hm…you’re comparing apples and hamburgers…

96

It’s no longer an issue, just add the above automation and the problem sorts itself out. No need to click around in Home Assistant every time a new device is added etc. Let the automation do that for you, whoop :smiley:

1 Like
97

I personally have around 40 ESPhome devices, so I know the situation described above.

My 2ct on this:

  • Don’t enable automatic updates of the add-on (don’t do that for any add-on, they can having breaking changes in the update, make sure to check what’s changed first), and if the update doesn’t bring you any relevant changes, skip the update of the ESPHome add-on. Next time it will have a new update, you will get an update notification again, and you can decide again if you want to update.
  • In case there are specific ESPHome devices you don’t want to update at all, just disable the update entity for that device like @petro has shown above, or move the yaml config for the device to another subfolder in your esphome folder. If you really don’t want to update it, you can’t make changes to the configuration anyway, because flashing the new configuration will also update it.
  • If you do want to keep the add-on up to date, and you want to skip all update entities of the ESPHome integration. I would suggest to trigger on a state change of the ESPHome Add-on update entity going from on to off (indicating it has been updated) or to create a binary sensor indicating there are ESPHome devices with an update and trigger on that binary sensor turing on. There is no need to trigger every minute and check if there might be any ESPHome devices with a pending update.

I personally have an indicator for pending updates on my dashboard. If I updated the ESPHome add-on, and don’t feel like updating all entities (for example if there was an update for the voice component only relevant for my Atom Echo) I have a template button which skips all ESPHome update entities.

1 Like
98

Yep, I do the same. Although I just have it as a service call to either update all or ignore all.

99

But aren’t these updates necessary for the devices as well? Or are most of these updates only applicable to the addon itself? How do you tell the difference?

100

Most of the updates are fixes for particular issues with specific boards or sensors. You can read the release notes to figure out what’s changed. They are as detailed as the HA releases.

1 Like