Sorry, I missed that. I hereby give you credit as the first to confirm. Thank you!
Can’t wait to try it myself. Not because having to work around a poorly implemented change is a good thing. Just because now I’m curious to see both the problem, and the workaround, in action. And, it’ll be a good reminder why I resist the temptation to jump on every new version as soon as it’s released.
Just to clarify, this works for all update entities in HA. Not just esphome.
strangely I have a bunch of ESPHome devices that I know for a fact that aren’t on the latest ESPHome version (they are all on 2022.9.x) and I haven’t seen any update notifications pop up on my system for them.
If your devices are not setup for api, then you will need see the pop up. At least for my case, I have one esp device that isn’t using the api and no pop up bubble for this one. Everyone else, yes.
They all use the API.
Till not so long ago I used a version of ESPHome which you had to install via an extra external third party add-on. That got updated nicely, regularly but not that often!
But with the API changes a month or so ago I found out that my version was very outdated it had been stuck since feb 2022. Friendly people here pointed out that I had to remove the previous ESPHome which was scary for I have a 50 nodes, so I thought I lose them all, but that did not happen.
And had to install the now inbuilt esphome add-on, which gets updated several times a week, lolz 
.
So now I update esphome ever so often, but let the bubble with the update nodes 50+ just be there and see if it get higher then I know there is another thing in HA that is in need for an update, the nodes… well maybe once a month or two months. For I dread the moment one gets flash fried, and I have to open walls.
I was not getting any update entities from ESPHOME and found a setting I had switched off, I posted here:
Where did you find that setting? I saw your other post, and I’m interested to see what else that integration does. I tried searching for it in integrations, and doing a regular Google search, but no luck.
In the configuration of the add-on, in settings
You are confusing the addon-update with the esphome module update, they are nit the same 
No, the setting I showed in the linked post will turn off the update entities, not sure what else it disables though
yup, i read it better this time, not a clue what is does though
I did find a skip option now, it was not there not so long ago, but it is in the settings, click a node, the little > and there you see this:
that did the trick for me, and the beauty of this is that under the ESPHome tab, all the nodes still show that there is an update if one would choose to update, I like it this way.
Ever notice how the most inaccessible device is the one that needs attention? Any devices “in the wall” should be accessible through a junction box or some other removable cover. You will have to access the device sooner or later.
After two or three ESPHome updates in just the last ten days, yet another one pops up today. What is driving the frequent releases? Is it bug fixes, new features, or an accelerated release schedule? For whatever reason, it’s too many, too frequently, IMHO.
I for one really like this feature. It finally handles all my updates in the same way: home Assistant components, add ins, HACS, router-firmware, Shelly firmware, and now finally esphome firmware.
This makes it very easy to automate on all the updates.
With one click/script you can install all updates.
I do understand though that frequent updates and many devices can get annoying.
Luckily there is the service “update.skip” which should also make it very easy to automate to skip all esphome updates.
It’s a no-go… do that 30+times for 30+ devices… And then do this again tomorrow… And day after tomorrow… And after 3-4 days… And…
For now best option is still to disable all “firmware” sensors from esp modules.
Well… Yes, but tell me why would anyone want to update 30 esp modules just because latest esphome has a bug correction for bl0939 chip, while NOone of my modules even use that library, so update won’t change absolutely nothing? And i really mean nothing! Doing constant updates will only end esp’s life prematurely, since (limited) number of flashes will come to an end. Would you change diesel pump in your car “just in case” , even if it’s working perfectly? I strongly doubt that.
And, updating from HA interface doesn’t work. It tries to update, but version on module remains the same and update notification is still there. One of reasons is that when compiling it’s often needed to “clean build” or compiling ends with an error.
No me neither, no idea when I switched it off, everything seems to work without it ?
it changes the version number 
but only that.
that is probably because the update failed, sometimes it succeeds, in the addon, you see the output with an error. the HA interface does not show the result. So you do not know what failed and why in the end except from the fact that the update appears again.
Noone is forcing you to update.
