dcapslock

Name filters on entity friendly_name. It is not selecting a name for the label filter. To use a pattern for a label, enter in YAML.

@tbgoose what I mean is that the label filter also accepts wildcard, but not in visual eidtor. So you will need to use 'Show code editor' and fill in using...

Can you share a simple config you are finding is not working? I am finding it hard to decipher what your config is from images alone. Also, you may be...

I have tried a config similar to yours with domain and label and its working OK. This is with version 1.16.1. For the second option, what happens when you remove...

I wonder whether this is just a caching issue. I would have assumed you have refreshed the page while testing. Also, the performance issues I mention could be causing related...

Testing now and I believe the issue is with the caching that auto-entities does. I tested area "Küche" and find everything working fine. PR #593 adds cache updates when registries...

Best way I can think is to label your known entities for a Device and then you can use auto-entities to includes entities of a Device but exclude those matching...

PR #593 fixes this. This PR is included in [v1.16.1-dcapslock.10](https://github.com/dcapslock/lovelace-auto-entities/releases/tag/v1.16.1-dcapslock.10). Either grab `auto-entities.js` JS directly from the release files or add https://github.com/dcapslock/lovelace-auto-entities as a custom repository to HACS and look...

auto-entities.js should not be part of the PR as it is build output. That is the current conflict.

I can confirm that the issue is with using filter template for any card type where it would previously return an error which stated that entities were required. Specifically, when...