Home Assistant service targets return 404, while persistent notifications work

[LukaHummel]

Summary

The Home Assistant (hassio://) notification target works when no service target is specified, creating a persistent Home Assistant notification. However, adding a valid mobile-app notification service target causes the Unraid Apprise Notification Agent test to fail with Not Found.

The same mobile notification action works when triggered directly in Home Assistant Developer Tools.

Environment

• Unraid host: Rack
• Apprise-Go version: v0.2.8
• Home Assistant host: 192.168.178.58
• Home Assistant notification service: notify.mobile_app_pixel_8
• Notification Agent: Apprise Notification Agent

Working URL

This successfully creates a persistent notification in Home Assistant:

hassio://192.168.178.58/<REDACTED_LONG_LIVED_TOKEN>

Failing URL

This fails when attempting to call the mobile-app notification service:

hassio://192.168.178.58/<REDACTED_LONG_LIVED_TOKEN>/mobile_app_pixel_8?batch=no&emojis=yes

I also tried the explicit equivalent form:

hassio://192.168.178.58/<REDACTED_LONG_LIVED_TOKEN>/notify.mobile_app_pixel_8?batch=no&emojis=yes

Steps to reproduce

1. Configure an Apprise Notification Agent with a valid Home Assistant long-lived access token.
2. Verify that a target-less URL works:

   hassio://<home-assistant-host>/<token>
   

   This creates a persistent notification in Home Assistant.
3. Add a valid Home Assistant mobile-app target:

   hassio://<home-assistant-host>/<token>/mobile_app_pixel_8
   

4. In Unraid, run Test for the notification agent.

Actual result

The test fails with:

Aug  1 10:58:47 Rack ool www: /usr/local/emhttp/plugins/dynamix/scripts/agent 'test' 'Apprise_Notification_Agent.sh'
Aug  1 10:58:47 Rack Apprise_Notification_Agent.sh: Failed sending notification (hassio notify error: unexpected status: Not Found)

The agent script contains:

APPRISE_URLS="hassio://192.168.178.58/<REDACTED_LONG_LIVED_TOKEN>/mobile_app_pixel_8?batch=no&emojis=yes"

The locally installed binary reports:

Apprise v0.2.8

Expected result

The notification agent should call Home Assistant's valid service:

notify.mobile_app_pixel_8

and the Pixel should receive a push notification.

Additional verification

The notification service itself is functional. This succeeds in Home Assistant Developer Tools:

action: notify.mobile_app_pixel_8
data:
  title: Unraid test
  message: Direct Home Assistant test

This suggests that:

• Network connectivity from Unraid to Home Assistant works
• The long-lived access token works
• Persistent notification mode works
• The target service exists and works in Home Assistant
• Only hassio:// service-target mode fails, returning HTTP 404

The current Apprise Home Assistant documentation states that these target forms should be supported:

hassio://host/token/mobile_app_phone
hassio://host/token/notify.mobile_app_phone

Could this be an incorrect API route generated by the Apprise-Go Home Assistant provider, or missing support for direct Home Assistant service targets?