[BUG] Notifications not sent

[dcapslock]

Before You Submit

• I have searched the existing issues and this is not a duplicate.
• I have provided logs or error evidence in the field below (debug logs, error messages, warnings, or any relevant output), or entered N/A with a reason if genuinely not applicable.
• I have filled in all applicable fields with real values and used N/A only where the field is genuinely irrelevant to my bug.

Describe the Bug

When I use a notification entity for notifications I do not get any notifications. Using a notification service works fine.

Device Type

Washing Machine

Device Brand & Model

N/A

WashData Integration Version

0.4.5.1

Home Assistant Version

2026.7.0

Reproduction Steps

Use a notification entity for finish notification. Notifications not sent.

Expected Behavior

Notifications sent

Logs / Error Evidence

N/A

Additional Context

Looking at the code, if a notification service starts with notify. it checks for a state, but also if the entity has attribute domain set to notify. None of my notification entities (iPhones) have a domain attribute so can only assume they were falling through to service which would have failed.

Contributing a Fix

• I plan to submit a PR fixing this and will wait for the accepted label before opening it

[github-actions]

👋 Hey @dcapslock, thanks for the report!

Looks like a few things are missing that we need before we can investigate:

• Outdated version (0.4.5.1): the current releases are v0.4.5.2 (stable) and v0.4.4-alpha (pre-release). Please upgrade and confirm the bug still exists on the latest version before we investigate — it may already be fixed. If it still reproduces, update this field with the version you tested.
• Logs / Error Evidence are missing or appear empty. This is the most important piece of information for diagnosing bugs. Please paste any relevant logs, error messages, or console output — debug logs if you have them, but even a single error line from the HA logbook is helpful. See the Logs / Error Evidence section of the issue form for instructions on enabling debug logging. If logs are genuinely not applicable to this report (for example: a documentation typo, a translation string fix, or a pure UI/config-flow layout issue where no runtime code path is exercised), replace the placeholder with N/A followed by a short one-line reason — for example: N/A - typo in README, no runtime behavior involved. Do not write N/A just because collecting logs is inconvenient; bug reports without logs and without a valid N/A reason cannot be investigated.

Please update the issue with the missing information. Without it, we won't be able to reproduce or debug the problem, and the issue may be closed.

How to edit this issue: click the three-dot menu (⋯) at the top-right of your post → Edit.

This check runs automatically. Once the issue is updated, it will be re-evaluated.

[dcapslock]

Version is actually 0.4.5.2. I filled i what the integration page was showing and note that the current code has 0.4.5.1 in manifest.json. I won't create an issue for this but you should note and update.

[3dg1luk43]

/fine

[github-actions]

✅ Cleared by @3dg1luk43 - issue marked as fine and queued for review.

[github-actions]

tag:v0.5.0

🎉 A fix or feature related to this issue shipped in 0.5.0 - Goodbye OptionsFlow, Hello Panel (Oh, and hi WashData Community Store).

Please update WashData and verify the behavior on your setup. If everything works for you, no action is needed — this issue will auto-close after 5 days of inactivity. If the problem still persists after updating, leave a comment here and @3dg1luk43 will take another look. 🙏