clickAction / actionable notification buttons not navigating (iOS, HA Core 2026.7.1)
I tried with Claude so get actionable notifications to open a live stream of my ring cams when I get a notification but it doesnt works.
Claude gave me these information to post a topic here. I Hope you understand it and I hope you can help me!
Thank you
Summary
clickAction and actionable notification action buttons (action: URI) are
completely non-functional on my iOS device. Tapping a notification, or tapping
an action button inside an expanded notification, always opens the app to the
last-viewed screen instead of navigating to the URL specified in the payload.
No errors are logged on the HA side.
Environment
- Home Assistant Core: 2026.7.1
- Install type: Home Assistant OS / Supervised (add-on based setup)
- Notify target used:
notify.mobile_app_<device>(legacy per-device service,
not the new 2026.5 notify entity) - Relevant add-ons: Ring-MQTT with Video Streaming (uses embedded go2rtc),
HACS AlexxIT/WebRTC custom integration
Steps already taken (troubleshooting checklist)
- Confirmed app was fully force-quit (not just backgrounded) before testing
- Reset Push ID via Settings > Companion App > Notifications > Reset,
force-quit, reopened app, restarted Home Assistant per official docs - Checked HA error_log / system log around notification send time — no
errors logged for the affected test notifications - Verified
notify.mobile_app_<device>service call itself succeeds
(success: truein the service response every time)
Payload variants tested (all fail identically)
- Relative path to a custom (non-default) dashboard sub-view:
clickAction: /dashboard-versuch/kamera-haustur - Relative path to a standalone hidden dashboard
(show_in_sidebar: false):clickAction: /kamera-carport/live - Relative path to the built-in default dashboard
(a view that definitely exists):clickAction: /lovelace/energie - Same target, with
/lovelace/prefix removed for a non-default dashboard
(per docs,/lovelace/should only apply to the default dashboard;
tested per docs guidance) — no change - Full absolute URL instead of relative path:
clickAction: http://homeassistant.local:8123/kamera-carport/live - Legacy
category+push.actionsarray with aURIaction - Modern inline
actionsarray (2021.5+ syntax) with aURIaction,
testing the actual action button (not just notification tap)
Every single variant produces the same result: the notification is
delivered, but tapping it (or tapping the action button after
expanding/long-pressing) only opens the app to whatever screen was last
open — never the specified path. This includes the officially-documented
/lovelace/<default-dashboard-view> case, which should be the most basic,
guaranteed-to-work case per the docs.
Expected behavior
Per official docs (Introduction | Home Assistant Companion Docs
and .../actionable-notifications), tapping the notification or an action
button with action: URI and a relative /lovelace/... path should navigate
directly to that dashboard view.
Additional notes
- Found a similar unresolved community report from Jan 2025 with an
identical symptom description ("opens the app but doesn't navigate to
the dashboard") after a HA update:
Notification clickAction stopped working after latest update - Aware that HA 2026.5 introduced mobile app notify entities
(notify.send_message) alongside the legacynotify.mobile_app_*
service. I am still using the legacy service, but wondering if this
migration introduced a regression affecting the legacy path's
clickAction/actionshandling as well.
Question
Is this a known regression tied to a specific Companion app or HA Core
version? Is there a diagnostic (e.g. device-side logs, or a way to confirm
the app actually received and parsed the notification payload's URL/action
fields) I can pull to help narrow this down further?
Happy to provide additional diagnostics (HA logs, full automation YAML,
etc.) on request.