I just tested it here on a iPhone and Galaxy S8 and it is all working fine. Make sure you understand channels if you are using them.
Could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on “</>” and paste code in there.
Thanks for your help on this. This is a test automation I created to troubleshoot. Nothing fancy. I feel like it’s something simple. maybe even on the phone itself. I did test with “High Priority” “Sticky” and “Notification Channel” same result. they all work fine until I enable the Start action button. Thanks again for your help on this.
To add: I created a quick automation manually but this time I used the Call Service Notification: this does work and presents the button in the notification just fine. Not sure what is different between the two methods.
I can see the problem now. It is not really a bug, but I will need to address it. With Android if you don’t put a name in the cancel button it will not work . With iOS it will work . So others don’t have this problem into the future I will have to add a default in. Below is your YAML. Copy and paste it in as I also saw there were quotes that shouldn’t be there, I think it was when you pasted it into this forum
Thanks for reaching out and letting us know as this will help other in the future
Updated descriptions warnings on action buttons that may prevent the automation from functioning correctly and could result in not receiving the notification.
If you like this blueprint? Consider hitting the button in the top post
If you like my blueprints, and would like to show your support or just say thank you? Click Here
I am assuming this is for iOS devices. To my knowledge no I wish there was… and I also wish there was an option to keep it there when you tap on it and it just doesn’t disappear. Android allows this but iOS doesn’t.
I am getting the following error in the System Log:
Error initializing 'Notify: Family Room Presence Stuck' trigger: In 'numeric_state' condition: entity binary_sensor.family_room_presence_presence state 'on' cannot be processed as a number
I will be working on this error log but one thing I noticed in your YAML, your state is Detected. Not sure if that is working for you but have a look at the state in developer tools and match it. I may say on, note it is also cap sensitive.
I’ve checked the sensor in Dev Tools and it currently shows as ‘on’.
So I’ve changed the setting in the Automation to ‘on’.
I assume the clear state will be ‘off’ - so I set that in the End Trigger - Fixed State Option too.
Then I checked the System\Logs and saw this:
Logger: homeassistant.components.homeassistant.triggers.numeric_state
Source: components/homeassistant/triggers/numeric_state.py:153
integration: Home Assistant Core Integration (documentation, issues)
First occurred: August 30, 2024 at 2:45:00 PM (12 occurrences)
Last logged: 10:55:13 PM
Error initializing 'Notify: Family Room Presence Stuck' trigger: In 'numeric_state' condition: entity binary_sensor.family_room_presence_presence state 'off' cannot be processed as a number
Error initializing 'Notify: Family Room Presence Stuck' trigger: In 'numeric_state' condition: entity binary_sensor.family_room_presence_presence state 'on' cannot be processed as a number