Some integrations always tend to be a bit slow with setting up during startup leading to templates being evaluated before entities used in that templates provide all their attributes. In my case it’s mostly the knx integration that isn’t able to gather all states on startup before HA wants to evalu…

[image] Updating Templates with the new default values in 2021.10.x Configuration I keep seeing the same question about the new default argument for the templating. This post will cover all possible ways to define default. All the methods that were changed: …

We are thinking about not adding / setting the entities unavailable before the first run of the state updater. But don’t expect this any time soon, could be a quite big change. In the meantime you can try to just check if the attribute exists / is None in your template before comparing it with <, b…

[image] derandiunddasbo: any way to prevent these warnings? Add the availability option in your Template sensors. If the template within availability evaluates to false, the sensor’s state template is not evaluated. However that won’t prevent the issue with the Numeric State Trigger and cove…

Do you have any [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: messages in your logs?

Yes, I have one of these warnings in my log, but it’s always the same device and the same group address. That’s an issue with this specific device, which seemingly didn’t take a power outage about a year ago very well and is acting a bit weird since then. One of the issues is, that this device refus…

[image] 123: Which integration is used for that cover entity? This is a knx cover entity. But as said, I don’t think, there currently isn’t much that can be done from the integration’s side, apart from the long term goal to completely change the way, knx entites are set up during startup as @…

[image] 123: Add the availability option in your Template sensors. If the template within availability evaluates to false, the sensor’s state template is not evaluated. - platform: template sensors: eg_entertainment_kinomodus: friendly_name: EG Entertainment Kinomodus …

[image] derandiunddasbo: But I suspect, that this doesn’t affect setting up all other entities It doesn’t if it’s just one. If it were multiple GAs it would slow down initialization of others because only 2 parallel reads are sent - so others would have to wait 2 seconds.

Try this version: - platform: template sensors: eg_entertainment_kinomodus: friendly_name: EG Entertainment Kinomodus value_template: "{{ states('sensor.beamer_status') != 'standby' and state_attr('cover.eg_wohnen','current_position')|int(100) < 100 }}" availabilit…

[image] 123: Try this version: No, that’s raising the same error as before. It’s because of the way, the integration currently adds entities during startup. F.e. a cover entity is initialized without the current_position attribute at first. The attribute and it’s value is only added, after t…

Is there any way to prevent template warnings / errors on startup for yet non-existing state attributes?

Configuration

Mikefila (Mike Fila) November 16, 2021, 4:55pm 2