Not working automations with triggers and templates

Configuration
,
1

I’m using Hassio on RPi to make some automations. I’m new in domotics, and in Home Assistant, near 7 mounth of study on it. Well, i don’t known how to make any automation in automatic… I don’t known where is my fault. I read all documentation and all forums, I searched with google and tried all possible solutions… but there is some strange thing, that I do or I don’t do, that is wrong. I’ll explain now. I want to create a persistent notification when a sensor attribute is below 1 (numeric state). The sensor name is “rifiuti_organici” the attribute to check is “days”. The “days” is a number that go from any value to 0. I want to trigger my automation when this sensor attribute go to 1 and lower and show a persistent notification for this happening. I used 1 sensor but I want to use many others similar in one automation. Every sensor, even this one tested named “rifiuti_organici”, has setted friendly_name attribute. For this tested the friendly_name is “Rifiuti Organici”. This is the automation test (I’m using Automation Editor included in Hassio):

- id: '1574810504844'
  alias: TestingRDRSU
  description: ''
  trigger:
    - platform: template
      value_template: '{{ states.sensor.rifiuti_organici.attributes.days|int < 2 }}'
  condition: []
  action:
    - data:
        message: "Triggered by: {{state_attr(trigger.to_state.entity_id, 'friendly_name')}}
        {% if trigger.to_state.state == 'on' %} 
        ON
        {% elif trigger.to_state.state == 'off' %}    
        OFF 
        {% else %}
        Error for trigger status. 
        {% endif %}

        1: {{ trigger.from_state }}
        2: {{ trigger.to_state }}
        3: {{ trigger.from_state.attributes.friendly_name }}
        4: {{ trigger.to_state.attributes.friendly_name }}
        5: {{ trigger.from_state.entity_id }}"
      notification_id: RDRSU
      title: Raccolta Differenziata
      service: persistent_notification.create

When I activate manually this automation and the sensor has days=1 or days=0, the persistent notification appear with the same message that I wrote in Automation Editor, without any change on content…
Where is the wrong thing?
I tried changing " with ’ … nothing
I changed data: with data_template: with Configurator plugin… the automation didn’t run even manually…
I tried all…
What I can do?

There is a strange behaviour when in Automation Editor I press the space bar on keyboard… it don’t add a space, but try to jump at end of page.
There are some bugs to solve yet? Or my system don’t work?
Strange…

Thanks in advances for your kind replies.

2

data_template

Don’t use the gui editor.

1 Like
3

also, it’s best to use multi-line templates to make reading easier. And I don’t think you can do that with the editor. So another vote to not use the editor.

action:
    - data_template:
        message: >
          Triggered by: {{state_attr(trigger.to_state.entity_id, 'friendly_name')}}
            {% if trigger.to_state.state == 'on' %} 
              ON
            {% elif trigger.to_state.state == 'off' %}    
              OFF 
            {% else %}
              Error for trigger status. 
            {% endif %}

            1: {{ trigger.from_state }}
            2: {{ trigger.to_state }}
            3: {{ trigger.from_state.attributes.friendly_name }}
            4: {{ trigger.to_state.attributes.friendly_name }}
            5: {{ trigger.from_state.entity_id }}
1 Like
4

Ok. Thank you for yours replies. So, I want to use Configurator plugin… But how to exclude the editor and activate manually an automation for test?
I used device_template in my tests, with Configurator, but not worked when trigged manually (even automatically). Manually I mean that I reloaded the automation and activate it in the page of hassio config (I use the gui in the Italian translation, hoping you understand what I say), clicking on a i in a circle, near the pencil that get into the automation editor, and pressing Activate.

5

I don’t use the configurator plug-in either but from my understanding it’s just a text editor so you should just be able to ignore the automation editor and edit all of your automations in the configurator.

It can’t work like that because you are using the “trigger” state objects in your actions. And when you trigger it manually you bypass the programmed trigger completely so then there is no “trigger” to look at to retrieve that information.

To test it you will need to let the regular trigger happen a see if it works.

1 Like
6

Ahhh, finally an explanation!!! I mean for this strange behaviour… Thank you very much! So I have to wait …

7

And what about if I write the automation and then I modify the attribute state of the sensor in Developer Tools (I guess is called so in english)?

8

Yeah, I guess you could force the attribute change in the states page. I’ve never tried it so I don’t know how that works, tho.

1 Like
9

A word to the wise on top of what finity said.
This execution also bypasses the conditions :roll_eyes:

1 Like
10

Yes, but not condition at all in my tests… if the automations works, then I fine tune they with the accessories… :wink:
Here, my problem is basic. But I’ll work hard to solve…

11

Good,
You are in good hands here, so I’m sure they’ll get you through.
The only dumb question is one you haven’t asked :smiley:
Good Luck

1 Like