Automation based on log

Configuration
,
1

I have tried a couple approaches to scrape log as an automation trigger. Neither seem to fire any pointers would be appreciated.
`

id: '1631227541159'

  alias: Zwave  Issue Notify (Duplicate)

  description: ''

  trigger:

  - platform: event

    event_type: system_log_event

  condition:

  - condition: template

    value_template: '''{{ "zwave_js_server.exceptions.Failed" in trigger.event.data.message[0]

      }}'''

  action:

  - service: notify.notifier_telegram

    data:

      message: Zwave Error 2

  mode: single'

`

- id: '1631313071772'

  alias: 'Zwave  Issue Notify2 '

  description: ''

  trigger:

  - platform: event

    event_type: system_log_event

    event_data:

      name: 'homeassistant.components.zwave_js:'

      level: ERROR

  condition: []

  action:

  - service: notify.notifier_telegram

    data:

      message: 'Zwave  Issue Notify2 '

  mode: single
2

Try this:

alias: example 555
trigger:
- platform: event
  event_type: system_log_event
condition: '{{ "zwave_js_server.exceptions.Failed" in trigger.event.data.exception }}'
action:
- service: notify.notifier_telegram
  data:
    message: 'Zwave Error 2'
3

Thanks that is not triggered either - I simplified to “Error” to get more hits fro CLI

grep -c “Error” /root/config/home-assistant.log

returns but nothing triggered

4

Did you configure the System Log integration to fire events?

fire_event string (Optional, default: false)

Whether events are fired (required when used for triggers).

5

I’m missing something here

system_log:
  fire_event: true
logger:
  default: info
  logs:
    zwave_js_server: error
    homeassistant.components.zwave_js: error

but the automation is still not firing.



- id: "1631466803658"

  alias: error  Notify (Duplicate) (Duplicate)

  description: ""

  trigger:

    - platform: event

      event_type: system_log_event

  condition:

    - condition: template

      value_template: '''{{ "Error" in trigger.event.data.exception }}'''

  action:

    - service: notify.notifier_telegram

      data:

        message: HA Error msg data

  mode: single
6

If you just added fire_event: true to configuration.yaml don’t forget that you have to restart Home Assistant to register the change you made.

Here’s an experiment I performed and you might want to try in order to confirm that the events are being generated.

Open two browser tabs, each one connected to your Home Assistant instance.

In one tab, go to Developer Tools > Events, enter system_log_event in “Event to subscribe to” then click “Listen to events”.

In the other tab, go to Developer Tools > Services, select “System Log: Write”, enter some text in “Message”, enable “Level”, select “error”, then click “Call Service”.

Screenshot from 2021-09-12 19-27-19
Screenshot from 2021-09-12 19-27-19676Ă—758 34.4 KB

Switch back to the other tab and confirm that it displayed the details of the event like shown below:

Screenshot from 2021-09-12 19-17-36
Screenshot from 2021-09-12 19-17-36653Ă—821 54.8 KB

In this example, you’ll notice the message I created is not in exception but in message. So if I wanted an automation’s action to check the event’s details, it would need to inspect trigger.event.data.message[0].

condition: "{{ 'testing' in trigger.event.data.message[0] }}"

In your case, it’s unclear to me where your zwave error message will be (in exception or in message) but if exception didn’t work then try message[0].

2 Likes
7

Thank you. This was super helpful - creating and recieving events via log is working fine.

8

Glad to hear it’s resolved.

Please consider marking my post above with the Solution tag. It will automatically place a check-mark next to the topic’s title which signals to other users that this topic has been solved. It helps users find answers to similar questions. For more information refer to guideline 21 in the FAQ.

9

Thanks for the help - final step for me was call with the quotes in the trigger condition - hard to test as manual operation skips the trigger + condition

10

Hi,

Just a question:
How to show debug logs after setting fire_event to true.

11

My response here might be useful: Trigger automation based on defined error in system log file - #7 by dajomas