Frigate Proxy – Notification Media Paths After Migration

[yanivf38]

Hi team,

I recently moved Frigate from the Home Assistant add-on to its own LXC running under Proxmox, and replaced the original Frigate add-on with the frigate-proxy add-on. When sending notifications from Node-RED to my phone, the images and video clips are no longer delivered.

Previously (frigate add-on), the image and clip paths were relative and worked correctly:

const clip = `/api/frigate/notifications/${eventId}/${camera}/clip.mp4`;
const thumbnail = `/api/frigate/notifications/${eventId}/snapshot.jpg`;

With Frigate Proxy in place, it appears I now need to use the Events API directly on the Frigate instance:

const clip = `${frigateIp}:5000/api/events/${eventId}/clip.mp4`;
const thumbnail = `${frigateIp}:5000/api/events/${eventId}/snapshot.jpg`;

Is this the correct approach when using frigate-proxy, or should the add-on still support relative paths like before?

Thanks in advance.

[inkeep-ai-assistant[bot]]

When using the Frigate Proxy add-on, the /api/frigate/notifications path only supports a specific API endpoint format and does not proxy the entire Frigate API(1). The notifications proxy specifically supports the path /api/frigate/notifications/{event_id}/snapshot.jpg but not arbitrary paths like clip.mp4(1).

Your approach of using the Frigate instance directly is correct. When Frigate runs in a separate LXC (not as a Home Assistant add-on), you should point directly to the Frigate API endpoints(1):

${frigateIp}:5000/api/events/${eventId}/clip.mp4
${frigateIp}:5000/api/events/${eventId}/snapshot.jpg

The Frigate Proxy add-on is designed to integrate Frigate into Home Assistant's sidebar and provide basic proxying, but it does not replicate all the notification media paths that were available when Frigate ran as a full Home Assistant add-on(1).

If you need Home Assistant to access these media files externally (for notifications sent outside your local network), ensure Frigate is accessible at the URL you're using, and consider whether you need to use the authenticated port (8971) instead of the unauthenticated port (5000) depending on your security requirements(2)(3).

📚 Sources:

1. [Question]: 404 on API endpoint when using the proxied URL for Home Assistant notifications
2. Home Assistant Integration
3. Authentication

---

Have another question? Just tag @inkeep.

[NickM-27]

You're misunderstanding what pieces do what. It has nothing to do with if you are running Frigate via the addon or docker install. the /notifications/ API is for the Frigate integration in home assistant, which maps to the Frigate API. That will still work provided the integration is setup correctly

[yanivf38]

Thank you, @nickm‑27.
As always you are right :-) I added the add-on but didn't reconfigure the frigate integration. It works now.

Thank you very much for your help.