fix: remove notification title from Dreame Vacuum to avoid duplicated device name

The `notification_title` input defaulted to `{vacuum_name}`, which caused the
device name to appear twice (once in the title, once in the message body that
already starts with `{vacuum_name}`). Drop the title input and revert to
message-only notifications, matching the original behavior.

Common/Dreame Vacuum/README.md

@@ -1,6 +1,6 @@
 # Dreame Vacuum Notifications
 
-Sends customizable notifications for Dreame vacuum events. Requires the [Dreame Vacuum](https://github.com/Tasshack/dreame-vacuum) integration.
+Sends customizable notifications for Dreame vacuum events. Requires the [Dreame Vacuum](https://github.com/Tasshack/dreame-vacuum) integration and Home Assistant 2024.7+ (`notify.send_message` action).
 
 ## Features
 
@@ -9,7 +9,8 @@ Sends customizable notifications for Dreame vacuum events. Requires the [Dreame
 - Device warning and error notifications
 - Informational alerts (e.g., action blocked by Do Not Disturb)
 - Individual toggle for each event type
-- Customizable message templates with variable substitution
+- Per-code filter lists for silencing routine warnings, errors, or info messages
+- Customizable message templates
 - Multiple notification targets
 
 ## How It Works
@@ -24,7 +25,12 @@ The blueprint listens to events fired by the Dreame Vacuum integration:
 | `dreame_vacuum_error` | Device fault |
 | `dreame_vacuum_information` | Action blocked by user settings |
 
-Events are filtered by the configured vacuum entity, so only the selected vacuum triggers notifications.
+Events are filtered by the configured vacuum:
+
+1. If the event payload includes `device_id`, it must match the device of the configured vacuum entity. This is the most reliable match.
+2. Otherwise the entity_id in the event must equal the configured one, or equal it followed by a purely numeric suffix (e.g., `vacuum.dreame_x10_2`). The integration uses `generate_entity_id()`, so a numeric suffix can appear when the base entity_id is taken.
+
+This avoids false positives when two vacuums share an entity_id prefix (e.g., `vacuum.dreame_x10` vs. `vacuum.dreame_x10_pro`).
 
 ## Configuration
 
@@ -33,8 +39,13 @@ Events are filtered by the configured vacuum entity, so only the selected vacuum
 | **Vacuum Entity** | The Dreame vacuum entity to monitor |
 | **Notification Targets** | One or more `notify` entities |
 | **Event Toggles** | Enable/disable each event type independently |
+| **Filtering** | Lists of warning/error/information codes to silence |
 | **Message Templates** | Customizable message for each event type |
 
+### Filtering
+
+Each filter input is a list of codes (as strings) that should not produce a notification. The blueprint compares the event's `code` field (cast to string) against the list. Use this to suppress noisy routine events while keeping critical ones.
+
 ## Message Template Variables
 
 ### Cleaning Started
@@ -84,10 +95,16 @@ Events are filtered by the configured vacuum entity, so only the selected vacuum
 | --- | --- |
 | `{vacuum_name}` | Friendly name of the vacuum |
 | `{information}` | Information message (e.g., Dust Collection, Cleaning Paused) |
+| `{code}` | Information code |
+
+## Notes
+
+- The default messages contain emojis. Most modern notify integrations (Mobile App, Telegram, Discord) render them correctly; legacy SMS-based integrations may not.
+- `notify.send_message` requires Home Assistant 2024.7 or newer.
 
 ## Debug Mode
 
-Enable **Debug Notifications** in the Debug section to send persistent notifications with raw event data for troubleshooting.
+Enable **Debug Notifications** in the Debug section to send a persistent notification for every trigger. Each debug notification includes the blueprint version, dispatched event kind, and the enable decision — useful for confirming filters are doing what you expect. The notification is keyed per vacuum so debug entries from multiple vacuums do not overwrite each other.
 
 ## Author