dcapslock
dcapslock
FYI thread. I just realised another workaround for `history-graph` which uses the experimental `eval_js` feature. `history-graph` will show 'No state found' if given a single bogus entity. So we can...
Please [format your code](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks). It is unreadable.
Looking at this I find that the below minimal config also exhibits the issue. Removing `sort` from yaml in edit mode then works. Note: when in this state no changes...
OK. It's a bug with how the edit form saves to config. I will be pushing a PR and will provide a test build from my fork.
Hi, I have submitted PR #575 to correct the issue. A build is available in my fork [HERE](https://github.com/dcapslock/lovelace-auto-entities/releases/tag/v1.16.1-dcapslock.6). Either add my form in HACS as a custom repository and select...
You can use the undocumented `evsl_js` option. See my [comment](https://github.com/thomasloven/lovelace-auto-entities/issues/578#issuecomment-3447862095) in another issue.
There is already an area option in [filters](https://github.com/thomasloven/lovelace-auto-entities#filters).
> _MORE GENERAL AND PROBABLY A BETTER FIX:_ Do not create/update the card until the EntityList has been populated. See #555 including a patched version available for cards that error...
@Mariusthvdb created #584 as your issue is different than this request. I will comment in #584
Hi @dobby5, you responded to my requests. Busy this week and I should be able to look at later in the week.