Apparently not Frigate
Response from developer
Thanks for the feedback.The description clearly says this is a third-party app, not the official Frigate app.
Unable to get FCM notifications working
Error: Update FCM token failed: 405”. Perhaps I’m missing something server side? I really like this app so far but notifications are a requirement for me.
Response from developer
Thank you for your feedback. FCM notifications require the Securex Nvr Push Relay setup on your Frigate server. Please follow the setup guide here: https://tynvr.147lab.com/#firebase After setup, restart Frigate and use the test button to verify notifications.
Amazing
Response from developer
Thank you for your support! Glad you’re enjoying the app 😊
Best iOS client I’ve tried!
Response from developer
Thank you so much for the kind review and support! Glad you’re enjoying the app 😊
Clean app - can’t believe it’s free
Response from developer
Thank you so much for your support! Glad you’re enjoying the app 😊
Bare bones, but solid
Response from developer
Thanks for the feedback! We’ll keep improving usability while staying powerful 💪
Thank you
Not sure why other reviews show failure to connect. It worked perfectly first try.
I'm hosting mine in docker with dock tail to provide https certs through tailscale.
Great app, thanks for making it.
Response from developer
Thanks a lot! Glad it worked smoothly for you 🙌
cannot connect to frigate over tailscale
edit: the issue may be the app doesn't let you change the port; when i remove it or use 80 the app tries port 50053, 50054, etc
Response from developer
I tested this by changing the default port, and both local IP and Tailscale worked fine on my side. 5000 works for HTTP, and 8971 works for HTTPS. If you're connecting over HTTPS — for example on port 8971 — you must turn on both Prefer HTTPS and Ignore Certificate Error (self-signed), otherwise the connection will fail.
Cannot connect
Response from developer
Thank you for your feedback. Sorry about that — I tested using the IP address and it works fine. If you are using HTTPS, you need to either disable “Prefer HTTPS”, or enable both “Prefer HTTPS” and “Ignore Certificate Errors.” Please note that using a domain name is currently not supported.
New update broke connection
Response from developer
Thank you for your feedback, and we're really sorry to hear you're experiencing connection issues after the update. This is not the experience we want for our users. The latest version included some changes that may affect certain connection setups, and we are actively working on improving compatibility.
Timezone seems to be hardcoded to EST
Response from developer
Can you please verify whether your Docker container itself is using the Asia/Shanghai timezone? Even if the host system is already set to China time, the container doesn’t always inherit the host timezone unless it is explicitly configured. If the output is not showing China time, then the container is still running in a different timezone (often UTC or U.S. Eastern), which would cause the recording timestamps to appear incorrect.
