When referencing a node red message for a URL or URI, it doesn’t work for the ios notification to direct the app to a path. My path is /lovelace-control/cards. A message “notify_url” is set to a string of /lovelace-control/cards
You don’t say how exactly it doesn’t work.
You don’t show where notify_url is set. What you have posted - suggests that you have previously set msg.notify_url to the value you want, but you haven’t clarified that anywhere so we cannot know for sure.
ALWAYS use a debug node when things aren’t working properly and make sure you set it to dump all of msg, and not just msg.payload.
When using the “url”: “{{notify_url}}”, when clicking the notification, it opens the app, but not to the path. When using “url”: “/lovelace-control/firetablet”, when clicking the notification, it opens the app, and navigates to the the path “firetablet” on the dashboard “control”.
Here is my node red:
From the NodeRed manual - By default, Mustache will replace certain characters with their HTML escape codes. To stop that happening, you can use triple braces: {{{payload}}}. so by only using the 2 braces, your / in your URL will be becoming %2 when sent to the service call. So the full URL your app is receiving is %2Flovelace-control%2Ffiretablet
Took me a while to get to the bottom of it too, because I have some flows using double braces and some using triple. I knew there was a reason, but I had to go and Google to find out what the differences were.
Please consider marking my post as the solution, to help others.
There is a grey bit of text that says “Solution” with a tick next to it, next to the part of the post where you like it, on the one that has the solution (ie use triple braces) - just click on the bit of text that says Solution.
No… by some reason it’s not possible to accept in some forums.
The reason there is an accept in the other forums is to make it easier to find answers, I find it odd that is not the case here.