Markdown card templates using stricter rendering than developer-tools about frontend HOT 8 OPEN

Your template seems fine to me in a markdown card:

from frontend.

Your template seems fine to me in a markdown card:

Thanks for verifying, but it only fails for entities where the device class is missing.

from frontend.

Yes I see what you mean. It seems markdown card subscribes its template with an additional argument strict: true, and developer tools does not.

Related: #17824

from frontend.

So it seems that strict mode for devtools was replaced with an option report_errors, but report_errors seems to catch less things than strict mode.

Perhaps that should be reported as a core bug, that report_errors should be able to report everything that strict mode would catch. I assume that was its intention but I don't know.

from frontend.

@karwosts
Nice it seems your identifiers the source of this issue.
But one remark. Rejectattr and selectattr should not raise errors when those attributes don't exist (to my knowledge)?! They will simply not be selected or rejected (like dev tools and template sensors). That is why I raised the issue here.

from frontend.

Rejectattr and selectattr should not raise errors when those attributes don't exist (to my knowledge)?! They will simply not be selected or rejected (like dev tools and template sensors).

My first experiments with selectattr / rejectattr were on 2021 - and on that time I learned that I must check for an attribute existence before using selectattr/rejectattr.

from frontend.

My first experiments with selectattr / rejectattr were on 2021 - and on that time I learned that I must check for an attribute existence before using selectattr/rejectattr.

I agree it is not very robust, But How to do that in filter expressions?! When I lookup a value with state_attr(), I have to check, but in a filter I want to include/exclude entities that match.
I checked several places where I can execute templates (dev tools, template sensors, state switch card etc) and the same filtering works for all, except the markdown card.

Update: @ildar170975 thanks for your hint. This combo of filters works in the markdown as well:

selectattr('attributes.device_class', 'defined') |selectattr('attributes.device_class','eq','connectivity')

It complicates my full template, as I also want the entity's that don't have a device_class attribute (so need to merge two lists). But it's a workaround. Still hope the issue gets solved though.

from frontend.

Other simple example:

{% set entities = states | rejectattr('attributes.device_class','ne','connectivity')| map(attribute='entity_id') | list    -%}
{{ entities }}

auto entities card works fine:

Markdown card with the same template fails:

from frontend.