Template Condition last triggered doesn't work

Osorkon · June 9, 2022, 11:09am

I don’t know if is it a bug or feature?!
I have a script, that send me the names of open windows per telegram.
That script is not the issue, that works well.

I want to start the script when its beginning to rain.
Also this works fine.

But i wont to start the script maximun only one time per hour. If in the meantime the rain stops and start agian.

I would like to use a template condition to calculete when the script was last triggered.

{{ (as_timestamp(now()) - as_timestamp(state_attr('script.regen_benachrichtigung','last_triggered'))) | default(0)  | int > 3600}}

The Template Editor shows that the result ist false.

alias: Garten - Regen Benachrichtigung
description: ''
trigger:
  - platform: state
    entity_id: binary_sensor.regenmelder_regen
    from: 'off'
    to: 'on'
condition:
  - condition: template
    value_template: >-
      {{ (as_timestamp(now()) -
      as_timestamp(state_attr('script.regen_benachrichtigung','last_triggered')))
      | default(0)  | int > 3600}}
action:
  - service: script.regen_benachrichtigung
    data: {}
mode: single

But if I use the template in an Automation the condition doesn’t work anymore?!

It doesn’t matter if the condition is true or false. Always the Action will be executed.

It looks like that you can’t test a templete condition, beause the result is always this message?!

template value should be a string for dictionary value @ data[‘value_template’]. Got None

The trace looks also very strange?

Is my template not correct? Or it’s not possible to use such kind of template as a condition?

Thanks in advance.

tom_l · June 9, 2022, 11:49am

This is a known issue with the automation editor:

github.com/home-assistant/frontend

UI Testing of Automation Conditions Does Not Work with Template Conditions

opened 01:22PM - 08 Apr 22 UTC

closed 09:18AM - 16 Sep 22 UTC

marlemion

### The problem In order to implement a somewhat more complex template conditio…n, I came across the problem that (at least testing) templates conditions do not work (anymore). What I did: Create a simple automation having a template condition: ``` - condition: template value_template: "{{ 1 > 2 }}" ``` So, this is extremely simplifed. The expression should return False, but instead I get the following error when testing this expression in the condition frontend (under automatisations): `Error handling message: template value should be a string for dictionary value @ data['value_template']. Got None (invalid_format)` If I enter the same snippet of code in the templates section un der developer tools, it prints false. Either there is a problem in the code just adding the template condition in the automatisation frontend or something is completely borked. ### What version of Home Assistant Core has the issue? 2022.4.1 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Container ### Integration causing the issue Automation ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml - condition: template value_template: "{{ 1 > 2 }}" ``` ### Anything in the logs that might be useful for us? ```txt 2022-04-08 14:40:54 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140209354674720] Error handling message: template value should belue_template']. Got None (invalid_format) ``` ### Additional information _No response_

Osorkon · June 9, 2022, 11:52am

Ok, testing doesn’t work. It’s a cosmetic issue.
But what about the template condition itself.
Why is my automations not working?

tom_l · June 9, 2022, 11:54am

What does this give in the template editor:

 {{ (as_timestamp(now()) - as_timestamp(state_attr('script.regen_benachrichtigung','last_triggered'))) | int(0) }}

calisro · June 9, 2022, 11:54am

btw, you’re probably better with this imho so you don’t have a hard coded name in there.

{{ as_timestamp(now()) - as_timestamp(state_attr(this.entity_id,'last_triggered')) | int(0) > 3600 }}

tom_l · June 9, 2022, 11:55am

Except you should supply a default for the filter.

calisro · June 9, 2022, 11:56am

yep. Too quick to type. haha

Osorkon · June 9, 2022, 11:58am

As I wrote. Depends on the last triggered time the result is True or False.

Didgeridrew · June 9, 2022, 12:01pm

You could also cut out the timestamp conversion and use:


{{ now() - this.attributes.last_triggered | default(now(), true) > timedelta(hours=1) }}

tom_l · June 9, 2022, 12:02pm

Yeah but that’s not what I asked you to test.

Osorkon · June 9, 2022, 12:03pm

3385

Osorkon · June 9, 2022, 12:12pm

The same behavior by using you template.

{{ now() - state_attr('script.regen_benachrichtigung','last_triggered') > timedelta(hours=1) }}

The condition is not fulfill → result = false.

But the actions are executed anyway?!

tom_l · June 9, 2022, 12:13pm

Can you post the full automation trace?

calisro · June 9, 2022, 12:14pm

Won’t this will fail if there is no last_triggered. timedelta is nice but need to ensure defaults and checks are in there.

Osorkon · June 9, 2022, 12:15pm

What exactly? The step details?

tom_l · June 9, 2022, 12:17pm

There’s a “Download Trace” (arrow icon), top right of the trace page.

Osorkon · June 9, 2022, 12:18pm

{
  "trace": {
    "last_step": "action/0",
    "run_id": "9443f561d772691058dfe101f9920344",
    "state": "stopped",
    "script_execution": "finished",
    "timestamp": {
      "start": "2022-06-09T12:09:30.216274+00:00",
      "finish": "2022-06-09T12:09:30.276153+00:00"
    },
    "domain": "automation",
    "item_id": "1621165589883",
    "trigger": null,
    "trace": {
      "trigger": [
        {
          "path": "trigger",
          "timestamp": "2022-06-09T12:09:30.216718+00:00",
          "changed_variables": {
            "this": {
              "entity_id": "automation.garten_regen_benachrichtigung",
              "state": "on",
              "attributes": {
                "last_triggered": "2022-06-09T12:08:41.734737+00:00",
                "mode": "single",
                "current": 0,
                "id": "1621165589883",
                "friendly_name": "Garten - Regen Benachrichtigung"
              },
              "last_changed": "2022-06-09T12:08:29.100922+00:00",
              "last_updated": "2022-06-09T12:08:41.779885+00:00",
              "context": {
                "id": "01G545VS05HWG0EY3DJJTKQ7TW",
                "parent_id": "01G545VS006J809MQ378T08WVC",
                "user_id": null
              }
            },
            "trigger": {
              "platform": null
            }
          }
        }
      ],
      "action/0": [
        {
          "path": "action/0",
          "timestamp": "2022-06-09T12:09:30.223985+00:00",
          "child_id": {
            "domain": "script",
            "item_id": "regen_benachrichtigung",
            "run_id": "28960080bbe5043475c67c4b863bd646"
          },
          "changed_variables": {
            "context": {
              "id": "01G545X8B8RG8NNCJ9XYZWXN8E",
              "parent_id": "01G545X8B2142G9NHGBQHPFQ2W",
              "user_id": null
            }
          },
          "result": {
            "params": {
              "domain": "script",
              "service": "regen_benachrichtigung",
              "service_data": {},
              "target": {}
            },
            "running_script": true,
            "limit": null
          }
        }
      ]
    },
    "config": {
      "id": "1621165589883",
      "alias": "Garten - Regen Benachrichtigung",
      "description": "",
      "trigger": [
        {
          "platform": "state",
          "entity_id": "binary_sensor.regenmelder_regen",
          "from": "off",
          "to": "on"
        }
      ],
      "condition": [
        {
          "condition": "template",
          "value_template": "{{ now() - state_attr('script.regen_benachrichtigung','last_triggered') > timedelta(hours=1) }}"
        }
      ],
      "action": [
        {
          "service": "script.regen_benachrichtigung",
          "data": {}
        }
      ],
      "mode": "single"
    },
    "blueprint_inputs": null,
    "context": {
      "id": "01G545X8B8RG8NNCJ9XYZWXN8E",
      "parent_id": "01G545X8B2142G9NHGBQHPFQ2W",
      "user_id": null
    }
  },
  "logbookEntries": []
}

tom_l · June 9, 2022, 12:19pm

If you run the automation manually it skips the triggers and conditions and just performs the actions.

If you use the trigger automation service in Developer Tools > Services you can choose not to skip the conditions,

Didgeridrew · June 9, 2022, 12:34pm

You’re absolutely right, I’ve updated the template in my original post

Osorkon · June 9, 2022, 7:34pm

But by default now() means.
When the script was never triggered before. There is no value for last triggered.
now() - now() = 0
now() - now() > timedelta(hours=1) → FALSE
That means that the automation will never be executed?!