Also I’ve the same issue
My solution was to add the device in the 2nd device as well… don’t ask me why but I got this tip on discord and it worked.
It’s because you can’t have empty device actions in automations anymore. Making blueprints that have optional device actions fail. It’s no longer optional. The owner needs to make a new version, or you need to remove the optional device action from the blueprint, or you just select a second device.
+1 for this ![]()
Love this blueprint ! Thx so much for this.
Although it indeed needs update.
I do have 2 questions…
- Do you have ± the same for sensors ? like doors, smoke detectors etc etc
- Is it possible to auto delete the persistent notification if for ex an update has made…, so we dont have to “tick it away” on the home feed card?
- Why does some notifications dont have a title?
@CentralCommand any idea?
Is this blueprint still reasonable or is it obsolete?
I’m asking because I don’t know if the additional features are somehow available without the blueprint in the meantime.
Recently I discovered that I do not get update notifications anymore... Any idea if there was "another" breaking change in HA updates? And if not or so, is there another way to receive notifications for HA updates?
Look in your log for errors, nothing changed in regards to notifications this release.
Logger: homeassistant.components.mobile_app.notify
Source: components/mobile_app/notify.py:246
Integration: Mobile App (documentation, issues)
First occurred: June 6, 2026 at 21:08:29 (8 occurrences)
Last logged: 15:00:02
Error sending notification to SNAP
I did no change anything. I think it stopped working about somewhere between 2 months and now ago. I did update the blueprint to be sure, but that does not help either.
For others, there is a new blueprint!
![]()
