Why does a contact alarm card offer me smoke alarm tags?

Does anybody know why this contact alarm card offers me smoke alarm tags?

When I add a card like this:

Then this:

If I click on the tag, I get this:

which means when I try to test my flow, the test condition seems to be only for smoke alarm as a trigger.

What am I missing?

Since the card supports multiple alarm types, but only one example text per token for the entire card, Athom has apparently chosen “Smoke Alarm” (etc). It’s just poorly named.

"alarm_true": {
  "title": "Any device's alarm turned on",
  "titleFormatted": "Any device's [[capability]] turned on",
  "token": {
    "capabilityName": {
      "title": "Alarm",
      "example": "Smoke Alarm"
    },
    "deviceName": {
      "title": "Device",
      "example": "Smoke Sensor"
    },
    "deviceZone": {
      "title": "Zone",
      "example": "Hallway"
    }
  },
  "args": {
    "capability": {
      "title": "Alarm",
      "__any": "Any Alarm"
    }
  }
}
1 Like

Thanks Robert, does that have any effect on how I can test the flow?

I think you can select which alarm it should test with?

Sadly not:

Test fail

That looks like the last “Then” card (“Resume Smart Schedule”) is just failing, regardless of whether you’re running a test or not.

You’re supposed to use the tags provided by the trigger card in the notification card. It will dynamically report the actual contact alarm name + zone.
When you test a flow, the timeline card shows your entered test data

Select these tags:

Flow:

Thanks for your replies.

I’ve added tags as I think you suggested @Peter_Kawa , but it still seems to just throw up Smoke alarm and the wrong zone

30333

It doesn’t work when testing. Because you “impersonate” the trigger card.
Just test it by operating the real contact sensors in the kitchen!