Any plan to Alerting Rule so there is built-in intelligence, less (or no) 1 by 1 config needed?

[Ltek]

Would love to see actual Automation and Intelligence (in additional to the nice visuals). It could be as simple as user defined Rules which determine what notifications are bubbled up... without need to tell the system on each and every action/activity/alerts.

• When 'mobile notification' contains string "Alert"
• When 'Area' = "Entry" and time is between 9pm and 6am
  ... etc

To go one step farther... you could then create a "Profile" which is a set with a Theme and Rules, in a single package that people could even share the JSON definition for. Rules can be system agnostic if defined using Labels, Areas, etc... the user simply imports the JSON and adjusts (if needed) the Lable/Area/etc

[djdevil]

Hi @Ltek 👋

This is a great direction — thanks for taking the time to sketch it out so concretely. The "Profiles as shareable JSON" angle in particular is something I hadn't fully thought through, and it clicks. Let me react honestly on where we are.

What already exists in that direction

The card ships with an Alert Templates Library (v1.3.9.9.7 onwards) — 11 pre-built bundles (batteries, doors/windows, water leaks, motion, updates, cameras, doorbell stack, presence, climate, offline detection, fire/CO). Each bundle uses HA's device_class metadata to automatically match every relevant entity on the user's setup, so you don't configure them one by one. Editor → + Add from template... dropdown.

This already covers a slice of the "less config needed" idea, but it's static: the bundles are curated, not user-authored rules.

What you're describing goes further

I read your proposal as three layers stacked on top of each other:

1. A rules engine — declarative "when X then bubble it up" instead of per-entity config
2. Contextual filters — Area, Label, time-of-day, day-of-week (this is the real "smart" part that HA's own automations already leverage)
3. Profiles — Rules + Theme + defaults packaged as JSON that anyone can import and re-adjust to their labels/areas

All three make sense, but they're very different amounts of work, and they can (should) ship independently.

Where I need your help

Before I commit to a roadmap I'd love to prioritize based on what YOU actually reach for in practice. Could you tell me:

1. Which 2-3 rules would you write on day one? — concrete examples like "any door in Area 'Downstairs' open between 22:00-06:00 → emergency theme". Real ones from your setup. This tells me which primitives to build first.

2. Do you already use HA Labels? (Settings → Devices & services → Labels — added in HA 2024.1) If yes, would you group by area, by label, or both?

3. When you say "mobile notification contains 'Alert'" — do you mean intercepting HA's persistent notifications? Or filtering already-configured alerts by title text? These are very different features (the first requires a whole new event listener paradigm).

4. On Profiles — would you actually share one publicly (e.g. a "family security profile" on the discussions board), or would it be a personal backup/restore thing only?

If we're honest, "Intelligence" is a strong word — the card wouldn't be doing anything AI-like, it'd be evaluating deterministic rules. But the practical outcome (less manual config, smarter matching) is the same, and that's what matters.

Would love your reactions to the 4 questions above — with those answers I can put a real proposal on the table.

[Ltek]

@djdevil
Looks like you are using AI (even to answer my post) so this is dead simple to add. You can see (and reuse) the rules engine I built into my custom cards. (screenshot below). You'd also want to add rule options specific to notification monitoring (which I dont have in there)

The 'Rules Engine' defines criteria ( 'intelligence' ) the card acts upon. One defined, you'd never need to modify the rules since rules are dynamic (evaluated real-time). Not tied to specific entities, automation notifications, scene, etc

#3 is a rule (really part of a rule) to monitor some/all (user selectable) of the HA notifications that go through the system (Persistent UI, mobile, 3rd part integration, etc). it simply intercepts the notification. Super easy