If I understand correctly, the latest updates of HA and/or ESPHome integrated the two more tightly. Part of that integration was adding a bunch of entities to HA. Some of these are update entities. You can see them in your entities list in Settings / Devices and Services / Entities. I had not noticed these before, but apparently this is how HA knows a version of something has changed, which triggers the notification “bubble” in the UI.
Maybe adding an update entity for every ESP device was helpful for someone. I have yet to see that explained. But at any rate, most active ESP users will probably find it problematic, for a number of reasons which have been well aired on this forum. Fortunately, there is a way to avoid (i.e.; “work around”) those problems. Just disable those update entities, right from that same Entities page.
It’s firmware tracking. It’s built the same way as all devices that have firmware updates. E.g. zwave, zigbee, UniFi, etc. It was an update to the esphome integration.
Hi, thanks and yes seen that. But disabling updates entities is not managing, is it? it’s just ignoring updates. Is there not any options to “forget” this update and wait for the next or other?
You can write an automation to skip specific updates with the skip update service. Works like any other service, just supply a list of update entities that you want to skip to it.
One gets more n more curious, what’s this " update annoyance " is all about , is their any specific reason that ESP-devices needs/is/gets so frequent updates ? , is it bug-fixes, feature updates or what/ why does it sounds like ESP-s has so frequent updates ?
I don’t have ESP-devices(what i know of), thou bunch of different brands in WIFI and Zigbee devices, but the “update” frequency , is very far from what current “Buzz” about ESP indicates
Updated to 2023.2.5 from 2023.2.0 Somehow all my Google Nest cast dashboards are “damaged”. Half of the entities are missing (consisting out of a lot of mushroomcards in a panel setup) I’ve restored a backup of last week when there was no trouble but that did not help. Few others see the same behaviour (thread). It looks like other dashboards that are not “hand build” do work. Anybody else experiencing this behaviour or maybe even have a solution. Needless to say that the family is not amused…
Hi, I’m have the same issue. Cards show fine within HA dashboards, no console errors - but when casting to Nest Hub, or Android TV - the same cards are missing. Up until reading @DBM’s post I thought I must have messed something up - but as I’m only just in the process of setting up a Cast dashboard - I didn’t have a ‘before’ to compare it to.
I’m seeing some Mushroom chips missing, but not all / Sensor card / Mushroom cards / Mushroom lights - so my initial thought was that it was custom cards, but the Mini graph cards work fine?!
If it helps, I tried the CATT method, which shows all cards, but I’m trying to stick to the inbuilt HA cast method. I’m happy to try anything, if anyone has any suggestions.
Combined image, as it’s my first post so still restricted:
I use a sensor group to sum up my energy meters for a total energy consumption.
Unfortunately, when setting up the sensor via the new Group feature in the UI, there is no state_class provided to the sensor and thus, it cannot be assigned for measuring the consumption in the energy dashboard. Brings me back to configuring the sensor via configuration.yaml.
Am I missing out something here or is the state_class missing from the UI configuration on purpose?
Yes, we all know that homeassistant is the center of the universe and all software distributions are rotating around homeassistant and the are not alllowed to stay on python 3.9 if homeassistant decides that 3.10 is necessary and they are also not allowed to upgrahe to 3.11 if home assistant only accepts 3.10. But some distibutions still dont want to be in sync with the glorious and god like home assistant team and then the user has a problem installing home assistant.
You need to install homeassistant and run it with a version of python that it says it is compatible with, it is that simple. Home assistant 2023.3 beta has had changes put it place to make it compatible with python 3.11
And by slow you mean if you have a monitor attached to your NUC ? , or are you as bachoo meaning when you access it over your WIFI, which most likely runs on WIFIg, in best case WIFIn , check your Router also might be high temperature there as well ( who knows ) … my point is lot’s of people saying my HA is slow, when in fact they have no idea of “what is slow” ? … bachoo name “on/from mobile apps” , so what about from a wired laptop/pc ? same “slowness” no ?, well then im sure you have a wifi-issue
PS: i assume you NUC/HA is wired
No, the nuc runs headless and is connected wired to ethernet. Using a Firewalla Purple, I have set up a firewall and traefik SSL offloading proxy to make it available from the outside world. Even If I us HA from inside the local network, it is quite slow. Slow in loading a dashboard, settings page and even in zwave response…
