Outgouing Alerts, matching ID field, and scary "FALSE" message ....

[FabienD74]

Hi,
I have setup a Pulse->Home assistant API in order to receive pulse alerts directly as "persistants notifications" in HA.
Works fine.
I ASSUMED the ID in alerts to be the same for Alerts with

• event = "alert" => I create a persistant notification with the "ID provided by Pulse"
• event = "resolved" => I deletthe persistant notification with the "ID provided by Pulse"

In therory !!!!!!!!, if systems are in sync, i should see persistant messages created then removed when they are "somehow solved" in Pulse.

It is +/- right and working.... So at least logic and pipes are UP and working.

But after some time ( 1 or 2 hours) , i suddently saw a lot movement in HA in the left menu.
The Only messages pending were :

• one regarding a proxmox being down ... I shuted down => OK.
• Another one A BIT MORE scary:

In the history of "messages" received on HA side, i also saw a lot of network issues created then resolved.
That point me in 2 things:

1. I will have to create a tool to insure PULSE NEVER HAVE a single network glitch... ( something like 10 pings per second with TTL 10ms, dump date >>/network_outage.txt; ip -a >>/network_outage.txt it it fails. Just to have a trace. I'm blind on this ATM.
2. I still don't know the best approach to see/debug/fix the matching (or not) of the ID send by pulse. Trace history in HA VS history in Pulse ???

Thx.

[FabienD74]

In Pulse, Everything is back to normal without doing anything...

[rcourtman]

For a single alert occurrence, the firing and resolved deliveries use the same alert identity. If you use a custom payload template, expose that as {{ .ID }} and use it as the Home Assistant persistent-notification ID. The transport idempotency header is deliberately different: X-Pulse-Event-ID is <alert-id>:alert for the firing delivery and <alert-id>:resolved for recovery, so retries can be deduplicated without treating recovery as a duplicate of the original alert.

To determine whether the mismatch is in Pulse or the Home Assistant mapping, please paste one matched firing/resolved pair from the webhook delivery history with only these fields: event, the alert ID field your template emits, resource name, alert type, start time, resolved time, and X-Pulse-Event-ID. Also paste the exact text/value behind the FALSE screenshot; the image alone does not reveal which payload field produced it.

The rapid network create/resolve activity is a separate signal. A short interruption can legitimately fire and recover, but the matched payload pair will show whether those were one incident lifecycle or different alert identities.