### New Home Assistant Integration: Combined Notifications
I just released a brand new integration for Home Assistant called Combined Notifications — it helps you group multiple sensors (doors, locks, lights, etc.) into one simple status.
Instead of checking 5 cards or 10 helpers, you get one sensor that tells you if everything is good — or exactly what’s wrong.
Shows “All Clear” when everything is normal
Lists alerts like: Garage open, Front Door unlocked
Fully editable: change icons, text, colors, and conditions
No YAML required — everything is set up in the UI
Works with the optional Combined Notifications Card for a clean Lovelace display
No restart needed after editing sensors
This started because one night my son left the car trunk, garage door, and front door all open, and our alarm off. It was raining. I built this to help make sure that never happens again — and to sleep better knowing everything is locked down, put away and safe.
Hi, thanks for your work.
I have not yet figured out how to make it work.
But I have this question.
When editing a condition, a mandatory “Index” field appear. What is this field for ?
This is a problem with home assistant. We did not code any index into the integration and can not replicate, nor find out what this is or where its coming from. My recommendation is to delete the sensor and unfortunately try it again. Im sorry we are working on a solution, but as of now cannot find the problem, nor recreate it.
Hi,
Thanks for this integration.
Is there a way to create a condition for an unavailable sensor ?
Like when the device die before the battery becomes too low.
I have tried this way but without success.
Sorry, I just saw your question.
It makes sense. The expression == unavailable won’t work because Combined Notifications evaluates states as strings, not keywords. Combined Notifications automatically interprets on, off, open, closed, true, and false as boolean-like literals in Home Assistant context.
UNAVAILABLE is different: it’s not a valid boolean or device_class state — it’s a special internal HA state that isn’t auto-parsed as a literal. That’s why it must be explicitly wrapped in quotes ("unavailable") so the integration reads it as a string value rather than being undefined.
Rewrite it like this: sensor.yl_house_door_main_battery == “unavailable”
It should work. Please let me know either way and Ill work on it more if need be. [email protected]
Thanks for your detailled answer.
But it does not work. I have tried “unavailable”, “Unavailable” and even using this slightly different double-quote “unavailable”, “Unavailable”.
