dcapslock
dcapslock
> This one works correctly, but I want to shorten the names @BorisVolkovyski you an use the experimental `eval_js` option (not documented) to assist. ```yaml type: custom:auto-entities card: title: Running...
If you want to make a patch of `auto-entities.js` you can do so as per below. This will mean that `auto-entities` will not load the configured card on all errors,...
Experimental, may be removed, but may just get you around using a Jinja template until that can be fixed. I have a PR submitted with Frontend. Once that gets merged...
> [@dcapslock](https://github.com/dcapslock) your proposed edit only touches the error message does it? > 100% related. auto-entities cannot do its magic as the error is now generic AND the underlying error...
So can’t fix correctly without Frontend fix, which does has extra benefits beyond allowing a fix for auto-entities.
Yes. auto-entities existing method (hack) needs updating as the presentation of ‘No entities… ‘ error is now in the deep.
https://github.com/home-assistant/frontend/pull/26064
Same issue as card-mod when using templates. Thomas is aware.
> I have this problem with label filters even more, it it unusable in my config, check [this issue](https://github.com/thomasloven/lovelace-auto-entities/issues/438) Probably different, but all the same, there is an memory issue...
> That part of the issue seems frontend related Not sure what is going on there. Could be timing in when decluttering card creates the card and history data recieved....