If you use customizer try to use debug instead of local.
If you don’t - try to load https://raw.githubusercontent.com/andrey-git/home-assistant-custom-ui/master/state-card-custom-ui-dbg.html
I was going by the fact that the error specifically referenced the custom-ui. I’ve applied the cusom-ui to everything in config yaml using a customize_glob entry:
i’m not really sure how that affects things i haven’t specifically defined any elements for tho.
I’ve cleared the cache several times. It also displays that way on all my devices, all refreshed. the picture files still exist in the same location.
i do have one other customized entity_picture that still works (for a garage door display animated using a template).
all of the entities that won’t display are created using the broadlink component.
However, I still have some broadlink switches that are still displayed (but don’t use “entity_picture” just a straight mdi icon also defined in the customize section) so i don’t think the problem is there.
Apparently the issues I was seeing were caused by two things that happened coincidentally…
I had removed an android IP camera that I was using that used an extra_data_template for the battery state. I assume that since the camera didn’t exist the custom-ui couldn’t read the state and then threw the error. Getting rid of the camera in the config got rid of the error but I still didn’t have the entities displayed in the frontend.
AND!!!..
Somehow the update to 0.67.1 caused the broadlink component to stop using the friendly name as the entity id and instead use the name that was used to create the entity in the component. The ones that broke were so close (they ended in a number when created but not in the friendly name) that I didn’t notice they were different until I looked at them several times. Then I realized the differences.
There was a note about a breaking change in the release note for 0.67.1 but it was worded very vaguely and, when I read it, didn’t seem to apply to me. And following the link to the broadlink docs didn’t help clarify the breaking change either. Now knowing the issue and going back to re-read it I can kind of see the connection.
neither had anything to do with the other. they just happened at the same time and led me (and, hence, us…) on a wild goose chase.
Thanks for the help. At least it gave you the idea for an improvement!