Why is this notification dismissal happening in the background?

@Mariusthvdb wrote:

building on this: Please check correct trigger and id in this automation

I have test automation for finding the correct trigger templates for my persistent_notifications. To see which service_data is used:

  - alias: 'Global persistent notification dismissal notification'
    trigger:
      platform: event
      event_type: call_service
      event_data:
        domain: persistent_notification
        service: dismiss
    action:
      service: notify.mobile_app_calltheboss
      data_template:
        title: 'dismissed'
        message: >
          persistent notification with notification_id {{trigger.event.data.service_data.notification_id}}
          was dismissed

without any frontend persistent_notification being created (or at least so I can see) this is firing about very 5 minutes…??

message text is:

persistent notification with notification_id config_entry_discovery was dismissed

Apparently the config discovery going on in the background, creating a persistent notification, which is then auto dismissed somehow. The dismissal is being sensed by the automation, and reported…

Is this a bug in the system, or a unexpected side-effect of an ‘ignore’ for the discovery I set? these kept bugging me:

Schermafbeelding 2020-04-14 om 22.55.051498×490 19.6 KB

and now still do, in the background apparently? I would think, setting the ignore fall would truly ignore the discovery, as in prevent. Now it seems to hide it, which is really unwanted, and taking system resources at that.

or would something else be going on

thanks for having a look

Posts: 1

Participants: 1

Read full topic