Closed jaburges closed 5 years ago
We already show error cards for missing entities so we can close this request I guess.
This should be re opened. This error is when an entity is configured in a Lovelace card but is not in HA at all. It is reproduced 100% of the time.
I'm away from my machine but I can provide additional details in a while.
And we handle that
Let me get more info in a bit. There is a use case that isn't handled. I'm mobile so it will be a bit but an example I had recently was a cast device that went unavailable and then a restart was performed and upon HA coming up, the cast device was still not online. Therefore, Lovelace threw the uncaught error.
EDIT: I will have to test further. Seems my use case maybe has been resolved? IDK. I just went through the same steps that would log an uncaught in the past. If I can reproduce, I'll open a new issue with more data.
log shows:
http://HA/lovelace/XXXX:0:0 Uncaught
this error seems to occur when an entity in
ui-lovelace.yaml
doesnt exist. Often can happen if re-naming something in the UI, or zwave renames the entity etc.REQUEST: can we include the entity that is missing in the error message please?