I’m not getting them either.
Core 2023.2.5 on Debian Bullseye.
I compile ESPHome configs on my Mac. Unsure of the version now, but it’s some months old. I don’t touch my ESPHome devices very often. But, I don’t think this matters, since I understand that this should show up server-side.
OK, I have moved to MariaDB in Docker using, tobi312/rpi-mariadb:10.6-debian
(RPi 4 armv7, HA Docker)
Everything is working now.
At the beginning I had some problem, HA migration to new 2023 version was failing.
I had minimized my DB by letting recorder purge keep days running from 30day to 7day before migration and new HA version, which minimized my DB from ~3GB to ~1GB.
(for copying DB from local to docker I used heidisql to copy directly without manual dump/import step)
I’ve a proposal to mitigate the concerns. Let’s split all firmware updates into two categories:
Important: to prevent breaking changes from happening and to fix security issues.
Optional: all other updates.
Any reason the code editor on mobile app (iOS) doesn’t show anymore for non custom cards?
That makes sense. That’s sort of how Microsoft does it with Windows updates. In that scenario, there are always some updates available, which is fine.
But it makes me question the best way to present them. Clearly the user with 200 ESPHome devices doesn’t need to see a yellow “bubble” with the number 200 in it. Nor do we want to totally hide updates so the beginner user never even knows they’re available.
Personally, I liked the way it was before. If there were an ESPHome update, or HA update, I’d see the number “1” or “2” in the bubble. When I went into ESPHome itself, I’d see which of my devices needed updating.
I made a feature request to add the ability to hide ESPHome entities because I have several ESPHome devices that are offline on purpose. Like my holiday lighting.
It’s bad enough to see “Update” on 50+ devices every few days, but worse on devices that I can’t update because they are in the attic in a box marked “XMAS Decorations”.
I do NOT want to see them in my Home Assistant Settings Page. This was not a well planned addition.
I disable my Xmas lighting ESPHome device when the lights are taken down.
Same here. Integrations → esphome entities. Sort by name, mass disable.
I tried every given advice but none of this advices worked. I tried top build a hole new Zigbee-Network but even this worked. Its frustrating.
I’ve read some time in here and asking myself if I should do the update to 2023.2.5 without problems after all? my version is the 2023.2.2 and everything is working as expected. What do you all mean?
wait, unobtrusive badge icon suggesting a pending update (which you probably should go out and do anyway) is an obvious mistake?
Relax, chill, this is just your esp board, not your core banking system. Just push that update button 
An obvious mistake is to think that everybody want and, therefore, would welcome the same.
As it has been said before, having lots of ESPHome devices turns these unobtrusive badge icons into a nagging nuisances, messing up your update schedule, not excluding general HA functionality.
“Just push the update button” - obviously, you never had to redo anything after an update went wrong. Good for you, but, again, it’s not something you should take for granted. Personally, I cannot afford playing with a complex smart home installation freely, thus, I do not welcome mostly experimental features being mass-deployed for live systems.
Naming the assistant in Home Assistant “Assistant” was not the smartest thing to do. Makes it impossible to do searches online, regarding finding help on the new assistant.
Sorry, didn’t mean to be that sarcastic…
Obviously you’re taking your smart home seriously, and thus you’re probably aware - delaying updates is an anti pattern. The more you delay the bigger chance that something may go wrong. Small update, less stress. Takes a lifetime to get use to it.
Why would you need to update the ESPs in the first place?
If the device works then why update it?
I’m delaying those, which I built or re-programmed myself, several of which - are heavily filled with external libs and includes. Blindly updating them evey time ESPHome updates is outright unsafe, carefully updating them every time - a headache. I know I shouldn’t delay updating too long, but smarthome system after it’s setup and tuneup should make things easier and not forcing user into doing things it’s way. Life is complicated enough as it is, we have too much forceful proprietary ecosystems already, please do not support turning HA into another one.
P.S. I know I complain here alot, but, seriously, there are literally no reason for such HA behaviour, none. ESPHome addon has “UPDATE ALL” button, it’s quite enough for those who actually need it.
Just disable the update entities. Your posts voicing displeasure take more time to create than it takes to disable update entities. Goto your integrations, click entities. Filter by esphome. Check all the update entities and then disable.
Yes, yes, I already did that, thank you 
I was merely explaining why do I think this feature should’nt have been enabled by default, that’s it.
The great thing about HA is that there are so many different ways to use it, and to integrate it into our lives. For some of us, it’s a lot of fun to play around with.
But some of us do take it very seriously. We monitor and control critical systems like sump pumps and heating systems. In my case, if these fail it can make my home uninhabitable.
In my career working on critical systems, delaying updates was the norm. Changes invariably created work for the support staff and customers alike. We never jumped on “.0” updates, and often skipped a version or two.
The more time you spend researching the full impact of a change, and the more you plan for both the implementation and any possible back-out, the smaller the chance something can go wrong. And the fewer times you have to do all that, the less chance of disruption.
those were all valid points before cloud native became a thing.
Let me try to make myself clear once more:
Those are notifications that an update is available.
Nobody is forcing actions here.
The disable update entities approach explained 2 posts above wraps the the topic.
The same well there is a notification bell to the right of this thread that I’ve just unclicked.