Title: iOS Companion: can't launch an external app's URL scheme from a notification

[rtm]

Model Name: iPhone 17
Software Version: 26.5.1
App version: 2026.5.0 (2026.1984)

Home Assistant Core Version 2026.6.3

I want a notification tap (or button) to open another iOS app via its custom URL scheme—specifically UniFi Protect (unifi-protect://protect/devices/), so a person-detection alert can jump straight to that camera's live view with two-way talk.

The scheme itself is valid: typing unifi-protect:// into Safari opens the Protect app. But I can't get the Companion app to hand it off. On the latest iOS app I've tried:

1. Notification url: unifi-protect://protect/devices/<id> → opens HA, lands on the History panel.
2. Notification url: unifi-protect:// (bare) → same, History.
3. Action button action: URI, uri: unifi-protect://... → same, History.
4. A raw <a href="unifi-protect://..."> link in a Markdown card on a dashboard → tapping it immediately routes to History too.

In every case the app seems to intercept the custom scheme as internal navigation instead of handing it to iOS (UIApplication.open). Standard http(s) URLs and /lovelace/... paths work fine—it's specifically non-standard schemes that get swallowed.

Question: Is there a supported way to launch a custom URL scheme / external app from an iOS notification or dashboard? If not, could url/uri values carrying a non-HA scheme be handed off to iOS rather than routed internally? (For reference, Android handles this fine via an intent://… clickAction—this is iOS-only.)

[bgoncal]

action: notify.mobile_app_bruno_s_iphone
data:
  message: Hello
  data:
    url: unifi-protect://protect/devices

This works for me, if it doesn't for you, you can try the TestFlight version

[rtm]

Thanks. Is there some specific reason you mention TestFlgiht? I checked changelogs and saw nothing obvious.

[bgoncal]

Not really, just because that's the version I'm currently on, did you try the above?