IOS📱 - Notifications ( Actions, Attachments, Customizable ) - Blueprint

IOS Notification Blueprint

This blueprint aims to be a full implementation of all options available for notifications on IOS.

No more thinkering with the settings until it works somehow and then redo everything for the next automation.
Just use this blueprint, attach some scripts to some actions and be happy.
Functions include:

  • All configuration options for notifications
  • Static attachments
  • Dynamic Attachments (Map and Camera) with full configuration options
  • Attaching Scripts to actions
  • Provide a text field upon clicking on an action (the reply is given as input for the script)
  • And many more!

Import

I will not post the blueprint here directly, since it has over 1500 lines. But you can see it (and modify it) here

If anything does not work, just write something here and I will look into it. There seem to be some options that simply wont work.

8 Likes

Quick note for everyone that wants to put pins on the map and template the input for that. I did not now that but if a template outputs something comma-seperated it will allways be treated as a list, not matter if you cast it to a string inside the jinja template. So if you now generate the lat and lon as comma seperated values as required, you will get an error because the blueprint assumes the output is a string, but it is a list. To circumentvent this you can add ~",," to your plueprint like so

{{(state_attr("device_tracker.<whatever>","latitude") ~","~state_attr("device_tracker.<whatever>","longitude")) ~ ",,"}}

This will output a string, because it is not a valid list… and still works with the blueprint!

Thank you for this. I have a question about the Trigger. I see that it is not possible to use a normal trigger. Understood. I have created a helper input_button but when I press that helper button the iOS notification is not triggered. Is the input_button meant to be just a dummy that does nothing?

I can push “RUN ACTIONS” within the automation and the iOS notification goes out. How should I be triggering the notification blueprint?

Thanks!

image

Sorry for the late response!

Seems that you are right. Incredible that so many people did not have that issue because this should not work for anybody…

it is fixed now in the git…since that is linked to the button deleting the blueprint and reimporting it should fix this issue.

Thanks again for bringing this to my attention.

1 Like

Hey, thanks for this.
I ran into a problem when using internal links - i am using this on iOS devices.
I enter URLs like “/lovelace/card-name” as values.
Every time i click them the companion app goes in the background and then opens the link correctly.
But i have to put the app to the foreground manually again - which renders this quite “uncomfortable”.
The action is marked as “foreground” and i tried several combinations with always the same outcome.
Any hint?

Thanks in advance!