I’ve seen this quite a lot in my old (core in Docker) install, where a card in the Lovelace UI would only show this error. Force refresh would often solve (though typically not until second, third or even fourth reload).
Now I have moved to HassOS in a VM, so it’s a pretty clean install. But trying to use custom cards (installed w. HACS) throws the same error. Example here:
Doing a force-refresh in the browser fixes it (temporarily), and shows the card. But that’s not really sustainable.
I’ve seen other posts about this, but typically those posts couldn’t temporarily fix it by “force-refresh”.
And the solutions were typically that (1) some code should be in configuration.yaml instead of ui-lovalace.yaml (in this new install, I have not used yaml mode yet for lovelace), (2) a typo in manually written yaml code (again, haven’t done any of that for this install), (3) to ensure that the folders for the cards were in the correct locations (they are all in /config/www/community/, all automatically installed there by HACS), (4) or that resources are loaded in “Configuration” → “Dashboards” in Hass UI (they are, third line in screenshot below for the example above):
So everything is the same as it was in my old “Core in Docker” install, where I also saw this.
Does anyone know why, and more importantly, what to do about it?
Note: The auto-entities is just an example, I’ve seen this for different custom cards as well, so it’s not (specifically) an auto-entities issue. Also, it is problem regardless of where I’m trying to view (browser or mobile app, local IP or remote access).