[jinja] disable failOnUnknownTokens

[ccutrer]

Home Assistant doesn't enable strict mode, so we shouldn't either. Fixes Koenkk/zigbee2mqtt#17395

[antroids]

It was enabled to fix the issue: #10496

Could you please check what will Python Jinja return in the case from unit test?

[ccutrer]

>>> from jinja2 import Environment
>>> env = Environment()
>>> tmpl = env.from_string("Hello {{ missing }}!")
>>> tmpl.render()
'Hello !'

[ccutrer]

Note that with #16307, the situation from the issue you referenced will end up with the item updated to NULL, which makes perfect sense for the situations that I'm seeing the UnknownTokenException (zigbee2mqtt does not know the state of something yet, and for scenes in zwave-js-ui where it goes back to not having a state immediately after triggering the scene). If you think that's not the correct behavior for a climate component, we should look at the Home Assistant source and see how it handles this.

[antroids]

Note that with #16307, the situation from the issue you referenced will end up with the item updated to NULL, which makes perfect sense for the situations that I'm seeing the UnknownTokenException (zigbee2mqtt does not know the state of something yet, and for scenes in zwave-js-ui where it goes back to not having a state immediately after triggering the scene). If you think that's not the correct behavior for a climate component, we should look at the Home Assistant source and see how it handles this.

Yes, you are right. I'll double check the HASS sources, but looks like with #16307 this should be ok.

[antroids]

LGTM

It would be nice to support is_defined filter.

https://www.javadoc.io/doc/com.hubspot.jinjava/jinjava/latest/com/hubspot/jinjava/lib/filter/Filter.html

[lolodomo]

LGTM, thank you