Open nottledim opened 22 hours ago
Would be good to see the request details using browser debug tools so we can see what the response is
GET /api/frigate/notifications/1730396453.984189-ifwube/Porch/clip.mp4 HTTP/1.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Accept-Encoding: gzip, deflate
Accept-Language: en-GB,en-US;q=0.9,en;q=0.8
Cache-Control: max-age=0
Connection: keep-alive
DNT: 1
Host: hass.lingbrae:8123
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36
HTTP/1.1 400 Bad Request
Referrer-Policy: no-referrer
X-Content-Type-Options: nosniff
Server:
X-Frame-Options: SAMEORIGIN
Content-Length: 0
Date: Fri, 01 Nov 2024 13:36:58 GMT
When a notification is sent to android hass app using SgtBatten's notification blueprint it provides the clip url that looks like
https://<domain>/api/frigate/notifications/1730296666.946824-qaky68/drive/clip.mp4
Android reports attempting to open this as "this page isn't working" Error 400
Similarly locally or from the browser
http://hass:123/api/frigate/notifications/1730296666.946824-qaky68/drive/clip.mp4
returns an http 400 Request Error.This is using the integration v5.4.0 with frigate 0.14.1-f4f3cfa
Configuration
Frigate is on a separate server from hass
Notification automation:
Frigate config
frigate-proxy:
Incidentally SgtBatten beta version for frigate 0.14 has the same problem. The config is very similar but it has this extra attribute:
If I set a client_id in that url hass returns 404 error otherwise it returns 400 error.
To me it's like a proxy or remote access problem. My question is what is wrong that provokes the 400 error?