if you don’t want the update notifications, disable the update sensors, and you won’t see them anymore, except on the esphome add-on page
So if I disabled the update sensor and decide to update the firmware on the device will it revert back to enabled by default?
no, it will not turn on again…
Google brought me here and I fully agree.
I have around 50 ESPHome nodes in my home and started to update all to ESPHome 2023.3.0 after an intrusive high orange number asked for it. This took me around 1,5 hours.
A couple of days later, the orange number reappeared, because there is an update to ESPHome 2023.3.1.
I took another 1,5 hours to update all my ESPHome devices.
Today the orange number reappeared because there is a new ESPHome update to 2023.3.2
I will skip this update because by now I’m worried about the flash memory in my sockets.
Please set up an option to hide updates for ESPHome components. I will continue to cheerfully update the firmware in my unifi components every month or so, but not updating all my ESPHome devices like 4 times a month.
see solution above…
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?
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.
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 }}
This approach made the most sense. I can skip with one click but still see that updates are available until I do. Thanks!
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… 
)
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 }}
Wow, thanks a lot! So, if understand correct this should “delete” update warnings for esphome (and mqtt) when they popup… nice!
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
They were thinking to notify you about an update 
It’s the same when a new HA core is released for example - you get notified about the update 
(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! 
)
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 
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.
Disable the update entity for the device. The update entity for the addon is handled by the supervisors integration.
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.
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.
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.
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 
You might have any link backing up your speculations with esp’s dying like flies? 
Like in the esphome forums or discord maybe? Any one wearing out their flash? 
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.
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 
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! 
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 
Still running HA 0.78 - right?
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…
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 
