Fregata Mobile for iOS - Beta Access

[nulledy]

Join the Beta and install Fregata Mobile now: https://testflight.apple.com/join/VP8qbJNw

Beta's are installed via Apple's TestFlight. You'll need to first install the TestFlight app which will then act as the "App Store" where you will install and get updates for Fregata Mobile Betas.

Any and all feedback requested and highly appreciated! Be sure to include your application version (initial release is 0.1.0 (474))

Beta updates will come often as we get and incorporate feedback.

Tell us below in the comments if:

• You find a bug, or something just feels "off"
• You have an idea for a new feature
• You think something could be improved, such as layout, page design, button placement, etc etc
• ANY and ALL feedback and suggestions are encouraged!

---

• Works with Frigate & Fregata v0.17+
• End-to-end encrypted notifications between your server and your phone. We can't read them, Apple can't read them
• Rich notifications with Photo & Video clips
• Notification text templating so notifications say exactly what you want them to say
• Notification filtering based on cameras and/or object type, allow certain notifications to break through iOS Focus
• Live, Review Clips, and Event Snapshot viewers (of course)
• Timeline scrubbing
• Intelligent switching between external and internal server URLs so walking out of your house and dropping off Wifi doesn't force a reconnect or app restart
• Full support of Fregata's Adaptive Transcoding so you can still see your 4K high-bitrate streams in lower quality when on a weak cellular connection (requires Fregata server)
• Support for custom headers to seamlessly access servers behind a proxy or Cloudflare Access
• Automated server-side config changes to setup encrypted notifications if logged in as admin, if logged in as a viewer user you are told the YAML config changes to make
• iOS shortcuts integration - likely needs more work, feedback requested
• Semantic search integration
• Multiple server support
• Share clips and snapshots directly from your phone to iMessage, WhatsApp, Facebook, etc
• Private by design: No analytics. The only traffic is between the app and your server + the notifications service (which is E2E Encrypted)
• Tons more I'm surely forgetting off the top of my head

Known Issues:

• No iPad specific layout, yet
• Website and docs do not yet exist

[Perry-The-Cynic]

Since I'm feeling perverse, I'm choosing the "set up with viewer account" fork.

“frigate.cynic.org does not look like an address on your own network” Why not? My (iOS) domain configuration says I'm in the cynic.org domain. What does not look like my own network here?

On the manual configure-my-Frigate path, I saw red phrases indicating something needs to be done in Frigate, but nothing looked like a link to detailed instructions. I figured it out (based on the Frigate docs), but that part isn't intuitively obvious. :-)

It's not clear (in this flow) when exactly the Frigate reboot(s) need to happen. I eventually figured out that I needed another reboot at the "now test it" point before it would, well, notify. And it works, yay!

More later.

[nulledy]

“frigate.cynic.org does not look like an address on your own network” Why not? My (iOS) domain configuration says I'm in the cynic.org domain. What does not look like my own network here?

We assumed most users would use a LAN local IP range here, which is what we are checking for. Note that this warning does not affect any actual functionality, but we can probably clean this up.

On the manual configure-my-Frigate path, I saw red phrases indicating something needs to be done in Frigate, but nothing looked like a link to detailed instructions. I figured it out (based on the Frigate docs), but that part isn't intuitively obvious. :-)

We plan to eventually have docs for each item and links to those docs for each in the app, we just aren't there yet. Do you know which these were? And were they red or yellow?

It's not clear (in this flow) when exactly the Frigate reboot(s) need to happen. I eventually figured out that I needed another reboot at the "now test it" point before it would, well, notify. And it works, yay!

Yeah, we've already done a lot of work here, but it sounds like we need to do more! We focused on the admin user path to start with assuming most users would use that, but the viewer path is supported and needs to be first class as well.

[Perry-The-Cynic]

Reddish. I didn't take screenshots, they were imperative ("do this or that"). I can re-run the setup if you need details.
It sounds like Frigate needs two restarts - one after enabling notifications, and another after registration. That seems... odd?

[nulledy]

I didn't write that part of the code, but I believe only 1 restart is required after both notifications are enabled AND the registration is done. This is likely an issue on our end with regards to the setup wizard.

Either way, we'll re-work the wizard and make it crystal clear for the user exactly what is required.

One other thing, the wizard should have told you the exact YAML changes that were required. Was that not adequate in your case? You mentioned needing to check the Frigate docs.

[nulledy]

We've now totally re-written the setup wizard:
Admins can have all of this applied in one click and 1 server restart.

For Viewers, 2 restarts are required:

• Gives step by step instructions each with 3 things: Where to set the setting in the v0.18 UI if you are running v0.18+, the exact YAML to set in plain english, a link to the relevant Frigate documentation. You must explicitly tell the wizard you completed the step, and it will verify on the next restart
• Tells you exactly when to restart, as a separate step, and watches your server to make sure you do it and it succeeds

[Perry-The-Cynic]

I remember no proposed yaml at all, nor any obvious link. I just went to the docs-dev site and looked at "notifications" to figure it out. Honestly, a link to that would have sufficed in my case.
I got all the way to "test; but you can't if you're a viewer", scratched my head, rebooted Frigate a second time, and it started working.

[mumbargo]

Looking good though it doesn’t seem to like my Tailscale ip for the away ip.
Settings>Connections give an alert that states “ 100.x.x.x looks like an address on you own network…”
…
And doesn’t connect on cellular.
iOS 27 public beta
0.1.1 (474)

[nulledy]

http:// should work fine, you may just need to remove the s manually as I believe https:// is auto-populated since both Frigate and Fregata set up HTTPS by default unless you disable it.

Let us know if you get this working or if there is a bug we need to fix somewhere.

[mumbargo]

I do have the away address set to http://
Still no remote connection, "could not reach"
The tail IP works fine on safari and chrome iOS browsers, although with a secure alerts.
From the browser, .../api/version returns a 404 until I log in. After log in it then returns 0.18.0-beta3+fregata.5e06d200f
It goes with out saying, I do not have TLS turned on as I'm local only with this server. Local and Tailscale that is.

[nulledy]

We block http:// for away addresses today, we had not taken into account a user using tailscale, or other VPN, without https://

This will be fixed in the next version, and will just show a warning.

[nulledy]

Is this working for you now @mumbargo?

[mumbargo]

It does indeed! On Tailscale WiFi and cellular Camera feeds stream just fine.

[Perry-The-Cynic]

In the full-screen replay view (only), a tap in the main view can mean either "bring up the hover bar" or "start/stop playing" depending on whether the hover bar is currently up. Since the bar auto-hides after a few seconds, this turns into a game of whack-a-tap: I want to stop playing, so I tap but the hover bar just hid so the tap brings it back and doesn't stop playing.
It might be better to make showing/hiding the hover bar an explicit discoverable action. Dismiss can obviously be done by flicking it, but how to show it? Tap-on-the-screen should be a reliable start/stop regardless of context. (Or else there should always be a play/pause button on screen.)

[nulledy]

This is a real UX problem. My first thought is to make the controls show up on tap in landscape and not have it pause/play, as once the controls are up you can use the controls to pause/play. Thoughts on that solution as a user?

[Perry-The-Cynic]

There seem to be two modes here, "watch" and "fiddle". In watch mode, I want the hover stuff to go away so I can watch. In fiddle mode, I want to quickly manipulate the timeline (scrub, back, forward, next tick) and I'm less concerned with seeing every last pixel. So yes, making this an explicit switch sounds good, and "tap in the hover bar" (not just in the play/pause micro-widget) works for me.
(HIG 101: Minimize mode switches, but make them explicit and discoverable where you need them.)

[nulledy]

Tapping the screen in landscape/fullscreen mode mode will now only bring up the controls, not pause or play.

Tapping on the video to pause/play still works in portrait mode

[Perry-The-Cynic]

Excellent. Thanks.

[Perry-The-Cynic]

In full-screen review, the stream details pane from the "speed dial" icon hides along with the hover bar. This means I get barely two seconds to read it before it hides itself. There is way more than two seconds' worth of stuff in that pane. :)

[nulledy]

In full-screen review

I'm unable to reproduce this in the full-screen review, however I can reproduce it exactly in full-screen live. Is that what you meant, perhaps?

[Perry-The-Cynic]

Looks like it.

[nulledy]

When turned on, stats in live view now stay visible until they are explicitly turned off

[Perry-The-Cynic]

The history view packs a lot of data into a small space. The snaps are well done. I wish there was a second-granularity timestamp visible. Or else show some animation that indicates that video is moving forward - the start/pause icon is formally serving this but something moving works better (and surveillance video is often "nothing happening until suddenly it does").

The tactile feedback when the history view snaps to event markers is sublime. Good call.

[nulledy]

Do you just mean some sort of timestamp/clock with second-granularity in the app interface itself? All of our test cameras (and my personal ones) have their own timestamps so we overlooked that if that's what you're asking for. I just want to make sure I understand you ask properly.

I'm not sure if Frigate/go2rtc provide the exact current stream time, but we can certainly look into what can be done here.

[Perry-The-Cynic]

Yes, I simply mean a running timestamp (with second granularity). The Frigate web ui shows that in the scrub bar handle.
I'm removing all text super-impositions from my cameras (they destroy pixels). Didn't realize people rely on those.
I think what's happening is that the play/pause widget is so tiny that my eyes don't lock on it. That and the 1/2 second latency responding to start/stop actions.
I think that I also have a learned expectation of the web ui being a bit flakey (sometimes it just freezes even though it's "playing"), and my mind is transferring that to your app's behavior and wants an animated indicator of progress.

[nulledy]

• Pause/play latency was improved
• A timestamp of the video playback with second granularity is now directly under the timeline marker, the timeline still skips back 1.5-2.5s when you release your finger

[jm1175]

Really liking this so far. Here is my current feedback:



1. Live view for cameras with HEVC codec don't play, it's just a black screen with audio. Playback clips in the review and explore tab play fine for these cameras.

2. The camera stream layout on the cameras tab is a bit of a mess for me. The streams on the right column are overlapping the streams on the left, and the streams are also partially cut off from the edges of the screen. It would be great if there was a single column view option that showed the full stream of each camera just like in the Frigate iOS web app.

3. Tapping the audio button to disable audio on a playback clip causes the video to pause. I also think it would be nice if it remembered the last state of the audio setting. So if I disable the audio while viewing a video, all other videos I view after that will also have the audio disabled until I tap the audio button again to enable it.

4. When viewing playback clips, I noticed you can quickly close the video with a pinch gesture or by swiping either from the left side or top of the video. The problem with this is that it conflicts with zooming out of the video and panning. For example if I zoom into the video, I can't pan/drag upward or to the left without accidentally closing the video, and I also can't zoom back out without closing the video.

5. It would be nice if there was a seperate control for finer scrubbing through the actual alert/detection segments on the timeline. The 1 hour timeline is too large for accurately scrubbing through a 20 second segment.

6. One other feature I'd like to suggest is deep links. I currently use home assistant for camera notifications and would love to be able to tap a notification and have it open up the matching review clip or live stream in the Fregata iOS app.

[nulledy]

Live view for cameras with HEVC codec don't play, it's just a black screen with audio. Playback clips in the review and explore tab play fine for these cameras.

Silly oversight on our part, will be fixed in the next version. I assume these HEVC live streams play fine in iOS Safari via the Frigate WebUI? Are you using any "Smart Codec"/"H.265+" etc on your cameras?

The camera stream layout on the cameras tab is a bit of a mess for me. The streams on the right column are overlapping the streams on the left, and the streams are also partially cut off from the edges of the screen. It would be great if there was a single column view option that showed the full stream of each camera just like in the Frigate iOS web app.

I bet this is an aspect ratio issue that we should handle better. All of our cameras are 16:9. Would you be able to send us a screenshot of this? Feel free to email it if you prefer for privacy (reply to your Fregata license email, assuming you are a Fregata user).

Tapping the audio button to disable audio on a playback clip causes the video to pause.

Bug, will be fixed in the next release

I also think it would be nice if it remembered the last state of the audio setting. So if I disable the audio while viewing a video, all other videos I view after that will also have the audio disabled until I tap the audio button again to enable it.

I like this idea, app-wide mute that follows from live view, review view, and between cameras, we'll add this

When viewing playback clips, I noticed you can quickly close the video with a pinch gesture or by swiping either from the left side or top of the video. The problem with this is that it conflicts with zooming out of the video and panning. For example if I zoom into the video, I can't pan/drag upward or to the left without accidentally closing the video, and I also can't zoom back out without closing the video.

We fought with this a lot already, and just giving it another test it looks like we have more work to do!

It would be nice if there was a seperate control for finer scrubbing through the actual alert/detection segments on the timeline. The 1 hour timeline is too large for accurately scrubbing through a 20 second segment.

Adding a shorter timeline of say 10 minutes is easy, the problem is that I'm not sure if Frigate produces preview frames at a fine enough granularity to actually see a preview while scrubbing with such granularity. We'll get this as good as we can based on what Frigate produces with regards to preview frames.

One other feature I'd like to suggest is deep links. I currently use home assistant for camera notifications and would love to be able to tap a notification and have it open up the matching review clip or live stream in the Fregata iOS app.

I suspect this can be done, however, I'd most like to know what would keep you using HA notifications instead of Fregata Mobile's, once it's stable. On my personal server I still use both, but that's really just for testing purposes. If there is something HA can do for notifications that Fregata Mobile cannot, we'd love to add it, if possible.

[Perry-The-Cynic]

The app seems to assume that full-screen is always best seen in landscape. There are cameras installed sideways (and 90 degree rotated in software) to catch hallways and corridors. For those, full-screen should remain in portrait mode. (There are also older 3:2 aspect cameras, and cameras that stitch two images together for "sideways panorama" views. And fisheyes - those are always great fun.)

[nulledy]

• HEVC camera live views should be fixed, but this could be camera dependent, please verify on the next build
• The 2 column view is fixed for cameras with unusual aspect ratios, but it may no always be ideal so a 1 column view was also added. We don't really have any unusual aspect ratios to test with, so please verify this and share feedback
• Muting or unmuting no longer pauses the video and mute is saved as an app setting and applies to all streams without having to be re-set
• I think we fixed all the issues with swiping, pinching, etc while zooming and panning the video, we found several
• a 5m timeline view was added that allows 1 pixel = 1s scrubbing, But we can still only show the preview frames Frigate has. Whatever those are, we show the closest one, whether that is every 1s or not
• Fullscreen mode is now camera aspect-ratio aware. Needs testing, very open to feedback

[nulledy]

A new build that hopefully incorporates all feedback will be live on TestFlight soon. You should receive a notification when it is ready.

Thanks to all for the testing and the feedback, keep it coming!

[jm1175]

I've just tested the new build (512) and here's what I've found:

The live streams for my HEVC cameras still don't play, only audio. The stream is visible in the main column or grid view and I can see the timestamp moving, but when I tap on the stream to open it, it only shows a black screen. I can confirm that these live streams do play in Frigate on iOS safari. For reference the cameras are Reolink Duo 2, Duo 3 and 1212a. I don't think they use smart codec just standard h265.

The camera stream layout looks much better now. No overlapping or cut-off streams on either the grid view or column view. I have a mix of dual lens cameras and single lens cameras so the aspect ratios vary a lot. One thing I will say about the column view specifically, it looks like each stream is scaled to fit inside a fixed aspect ratio which appears to be based on the widest stream (in my case the duo 3 - 32:9). This means all other camera streams with less-wide aspect ratios (4:3 and 16:9) are scaled down and have large black bars on either side of the stream. Not a huge deal but it would probably look better if each stream filled the full width of the column regardless of their aspect ratio.

The audio button works great now.

Zooming and panning is much better, though I noticed a slight inconvenience with zooming where it doesn't keep the frame anchored on the area that you're zooming into and instead seems to veer off to the center. If you compare this with the zooming in the Frigate web app, you will notice that it mostly remains anchored on the area where your fingers touch the screen.

The 5 minute timeline works great for scrubbing, though on some videos it didn't work for me. Also, on very short segments (like 5 seconds) I find scrubbing can be difficult because of the playhead snapping to the alert marker. Maybe the playhead snapping could be disabled on the 5 minute timeline?

The main reason I'd be reluctant to switch from Home Assistant to the Fregata app for notifications is because I currently use the Frigate notification blueprint with some conditional logic that wouldn't work in the Fregata app right now. For example, in the notification blueprint I'm able to use a condition for critical alerts that changes the notification to critical if the time is at night and the object is a person. I also have some switches in the home assistant dashboard that allow me to control the notifications further, such as a temporary notification pause switch for pausing notifications for a chosen amount of time (5 minutes, 30 minutes, 1 hour, etc.). I use the master condition filter in the notification blueprint to check if this switch is active before sending a notification. If the Fregata notifications functioned similarly to the notification blueprint and there was an option to add a few custom switches in the app somewhere, I'd definitely consider using it!

[nulledy]

We request some more info below, you can send it to us via email by replying directly to your Fregata license email.

The live streams for my HEVC cameras still don't play, only audio. The stream is visible in the main column or grid view and I can see the timestamp moving, but when I tap on the stream to open it, it only shows a black screen. I can confirm that these live streams do play in Frigate on iOS safari. For reference the cameras are Reolink Duo 2, Duo 3 and 1212a. I don't think they use smart codec just standard h265.

Looking into this some more, on our Dahua test cams HEVC works fine for General Codec, Smart Codec, and AI Codec. So this is likely camera dependent, Reolink is infamous for funky codecs. We need to make sure that anything that plays in Safari plays in our player, but we're coding in the dark here since we don't have a camera that fails.

• Are these cameras being restreamed in Frigate through go2rtc or is Frigate connecting to them directly?
• Open the Frigate Web UI to one of these cameras in Safari on iOS -> Gear Icon -> Show Stream Stats. Is the stream type MSE, WebRTC, or jsmpeg?, and is it definitely playing your main, full-res stream?
• In the app, can you open one of the black cameras, open the stats panel, leave it for ~10 seconds then screen shot it and email it to us?
• Right after the above, go to Settings > Diagnostics > Copy icon in the top right corner and send us this log via email? (no credentials are logged)

The camera stream layout looks much better now. No overlapping or cut-off streams on either the grid view or column view. I have a mix of dual lens cameras and single lens cameras so the aspect ratios vary a lot. One thing I will say about the column view specifically, it looks like each stream is scaled to fit inside a fixed aspect ratio which appears to be based on the widest stream (in my case the duo 3 - 32:9). This means all other camera streams with less-wide aspect ratios (4:3 and 16:9) are scaled down and have large black bars on either side of the stream. Not a huge deal but it would probably look better if each stream filled the full width of the column regardless of their aspect ratio.

We played around with this a lot yesterday. When trying to get odd aspect ratio streams to fit in a box you have 3 options:

• Full width, crop the height
• Full height, crop the width
• Fit the full frame, add black bars on top or bottom as necessary

We picked the third, as it looked best in our mockups, but these were just mockups. Very open to feedback here, screenshots would be super helpful (feel free to send via email for privacy)

Zooming and panning is much better, though I noticed a slight inconvenience with zooming where it doesn't keep the frame anchored on the area that you're zooming into and instead seems to veer off to the center. If you compare this with the zooming in the Frigate web app, you will notice that it mostly remains anchored on the area where your fingers touch the screen.

Reproduced, should be easy to fix.

The 5 minute timeline works great for scrubbing, though on some videos it didn't work for me. Also, on very short segments (like 5 seconds) I find scrubbing can be difficult because of the playhead snapping to the alert marker. Maybe the playhead snapping could be disabled on the 5 minute timeline?

Can you elaborate a bit on "some videos it didn't work for me"? I do think removing the snapping on the zoomed in timeline is probably best, we'll make that change.

The main reason I'd be reluctant to switch from Home Assistant to the Fregata app for notifications is because I currently use the Frigate notification blueprint with some conditional logic that wouldn't work in the Fregata app right now. For example, in the notification blueprint I'm able to use a condition for critical alerts that changes the notification to critical if the time is at night and the object is a person. I also have some switches in the home assistant dashboard that allow me to control the notifications further, such as a temporary notification pause switch for pausing notifications for a chosen amount of time (5 minutes, 30 minutes, 1 hour, etc.). I use the master condition filter in the notification blueprint to check if this switch is active before sending a notification. If the Fregata notifications functioned similarly to the notification blueprint and there was an option to add a few custom switches in the app somewhere, I'd definitely consider using it!

• Critical notifications are something we want to support, but they require a special iOS entitlement that App Store reviewers scrutinize heavily (so that Critical Notifications don't get over used for spammy notifications). It's not recommended to request this entitlement on your initial App Store publish. Coming soon, dependent on Apple's approval.
• Notification snooze is currently supported per-camera in the camera settings under live view. We should add a global toggle and we could make this toggle-able via Control Center, a Widget, or iOS Shortcuts. Added to the roadmap.
• We definitely want to build out more notification control for power users and it's coming. If you have any more ideas, let us know!

[Perry-The-Cynic]

Default-cropping and zooming are the same problem space: whatever you do, make cropping act like a zoom - so I can pan around, and I can zoom out and get letterbox bars.
It would be quite helpful if "more this way" was visually indicated in images, whether it's due to default cropping or explicit zooming. A single-pixel colored line sufficies, or you can use blending/blurring if you want to be fruity about it.
I think if those two apply, then the initial cropping behavior is much less important, and you can always make it a preference.

[jm1175]

No problem I've just emailed the screenshot and log. Yes the cameras are being re-streamed through go2rtc. I'm using the http-flv stream as it seemed to be much more stable than rtsp. The stream type in Frigate safari iOS is jsmpeg and also says "Live view is in low-bandwidth mode due to buffering or stream errors". It also appears to be exactly the same in safari on Mac. I didn't notice this before because I usually view the live streams in Frigate using Brave browser on Mac, where the streams are smooth (stream type MSE), or in the Reolink iOS app.

I'll send a screenshot through TestFlight feedback regarding the column view layout.

As for the scrubbing on the 5 minute timeline not working on some videos, it just shows a still frame while scrubbing. As if there are no preview frames available for the video or it's having trouble loading them. Actually now that I look at it again, I think I see what's going on. Only new playback videos created since the top of the hour are working for scrubbing, anything older cannot be scrubbed (the video itself still plays). This is probably just an issue on my end and I think it might be related to the RAM disk dump error that I'm getting in the logs.

[Perry-The-Cynic]

In the alert layout, skip the "GenAI Summary:" header (and the empty line preceding it!). On a watch, that's literally all that comes through: "GenAI Summary: A p..."
I'd say that if there is a GenAI summary, then skip the entire object list ("Person") and just show as much of the GenAI summary as you can.

[nulledy]

I'm not sure we want to skip the object list entirely when a Gen AI summary comes in (maybe we can make it configurable?), because if the first 2 lines of the Gen AI summary do not contain enough details, relevant data is lost from the notification.

I made the change to delete the extra line break and removed the GenAI Summary: prefix. Let me know what you think of that when that lands in the next build.

[nulledy]

Rethinking this, we'll add genai to the templating engine so you can place it wherever you want.

The default template will be updated to what I mentioned above. If you want the GenAI summary to replace the body of the notification entirely, but still have the current body until the GenAI summary arrives, you'd use:
{{^genai}}{{subjects}}{{#zones}} in {{zones}} Zone{{/zones}}{{/genai}}{{#genai}}{{genai}}{{/genai}}

Will be available in the next build.

[nulledy]

v0.1.0 (534) is going out now with the following fixes:

• Remove the GenAI Summary: and blank line before it in notifications by default
• Allow the Gen AI summary to be configured by the notification templating engine for customization. And update the default template to be in line with the above
• Try to fall back to a lower stream if HEVC decode fails and log more diagnostics as to why the decode failed
• When clicking on an event, the event title no longer quickly switches from "Event" to "Camera Name"
• Prevent pinch to zoom from trying to pull towards the center of the video frame
• The zoomed in 5m timeline no longer snaps to the edges of reviews to allow for precise scrubbing
• Fix revoked push notification registration entries that could linger forever on the diagnostics page

[nulledy]

v0.1.0 (541) is going out now with the following fixes:

• Improve single-column camera layout (feedback requested)
• Fix a bug that could cause a review clip to be paused or black when switching to another app and switching back
• Fix a bug that could cause the app to rarely continue trying the internal URL when watching a review and moving from your home WiFi network to cellular

[derekboreman]

Here are some things I've found so far. Looks very promising.

Timeline/recording playback stuck in a rebuild loop behind a reverse proxy (live + Safari both work)

App: Fregata 0.1.0 (534), iOS 26.6.2. Frigate 0.18.0. Over VPN (app says offnet).

SETUP
Frigate is behind a reverse proxy that does auth (Frigate's own auth disabled:
auth.enabled false + proxy header_map). The app uses Advanced > custom header
Authorization: Bearer , which the proxy maps to an admin user. The proxy
also sets a matching frigate_auth cookie so iOS AVPlayer (which can't send the
Authorization header on its HLS requests) can authenticate playback.
Unauthenticated requests get a 302 to a login page.

WHAT WORKS
Live (MSE), events, notifications, snapshots, the scrub filmstrip, and all API
calls (Bearer header) work perfectly. The same recordings play flawlessly in
mobile Safari (Frigate PWA) over the identical proxy/path using a session cookie.

WHAT FAILS
Recordings/timeline never advance. One frame then black. Diagnostic overlay:
Ladder=Single rung, Resolution=2560x1920, Bandwidth=—, Buffered=0s, Stalls=0,
Position=0:00. It parses the manifest but buffers zero data.

NOT AUTH / NOT DELIVERY
App log shows the playlist loads WITH a duration:
[timeline] playlist .../master.m3u8
[timeline] anchor file-aligned (covered): playlist 3566s vs window 3600s
[seek] asked 08:53:26 landed 08:53:22 off -3.4s in 2224 ms
Proxy access log shows AVPlayer (AppleCoreMedia UA) getting HTTP 200 with full
segment data (master/index m3u8, init.mp4, seg-*.m4s all 200, 1-5 MB each).

THE LOOP (why it stalls)
Right after the playlist loads, this repeats every few seconds and playback never
advances:
[net] URL race won by https://nvr.example.com/ (with slash)
[net] URL race won by https://nvr.example.com (no slash)
[timeline] buffer is thin and the server has moved to nvr.example.com; rebuilding
[timeline] playback has not advanced; resolving the server again
Two URLs that differ only by a trailing slash are treated as different servers;
the URL race flips between them, each flip reads as "server moved," and the player
is torn down and rebuilt before the buffer fills, resetting to 0s. Reducing to a
single URL helps but doesn't stop the "resolving the server again / rebuilding".
A few AVPlayer/probe requests also go out WITHOUT the cookie and get a 302 to the
login page, which seems to feed the same "server moved -> rebuild".

SUSPECTED BUGS

1. URLs differing only by a trailing slash (or internal vs external) are treated
   as different servers -> "server moved" -> player rebuild. Normalize the origin.
2. Player is rebuilt on routine re-resolution while segments are returning 200,
   so the buffer never accumulates (Buffered stays 0s).
3. Probe/rebuild requests omit the auth cookie/header and get 302; the app reads
   the redirect as the server relocating. Probes and rebuilt players should carry
   the same auth as normal playback.

EXPECTED
Once the playlist loads and segments return 200, playback should buffer and play.
A trailing-slash / internal-vs-external difference shouldn't count as "moved," and
the player shouldn't be rebuilt on routine re-resolution during playback.

REPRO

1. Put Frigate behind a reverse proxy (auth.enabled false + header auth); auth the
   app via a custom Authorization: Bearer header; proxy issues an AVPlayer cookie
   and 302-redirects unauthenticated requests to a login page.
2. Set At-home and Away to the same host differing only by a trailing slash
   (https://nvr.example.com/ vs https://nvr.example.com). Connect over VPN.
3. Live works; open a camera's timeline -> rebuild loop, Buffered 0s, never plays.
   Same recordings play fine in mobile Safari (Frigate PWA) over the same proxy.

[nulledy]

Thanks for the detailed logs @derekboreman, found and we're fixing it now.

[nulledy]

@derekboreman the problem here was that both your home and away URLs were accessible and neither was "faster". This caused the review player to get stuck in a loop flipping between each of them trying to find the fastest route (and since neither could be determined to be on the same subnet as your WiFi, if you were connected to WiFi, neither was picked decisively) which tore down and re-initialized the review player each time.

Fixed in the next build which is going out momentarily. Please let us know if this solves the problem for you.

[nulledy]

Any luck with the latest versions @derekboreman?

[derekboreman]

I’ll let you know! Thanks! Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: nulledy ***@***.***> Sent: Monday, 14 September 2026 16:41:33 To: 3rdBitLabs/Fregata ***@***.***> Cc: derekboreman ***@***.***>; Mention ***@***.***> Subject: Re: [3rdBitLabs/Fregata] Fregata Mobile for iOS - Beta Access (Discussion #83) @derekboreman<https://github.com/derekboreman> the problem here was that both your home and away URLs were accessible and neither was "faster". This caused the review player to get stuck in a loop flipping between each of them trying to find the fastest route (and since neither could be determined to be on the same subnet as your WiFi, if you were connected to WiFi, neither was picked decisively) which tore down and re-initialized the review player each time. Fixed in the next build which is going out momentarily. Please let us know if this solves the problem for you. — Reply to this email directly, view it on GitHub<#83?email_source=notifications&email_token=AFM6T6PRPMMEBWHNPEOKGOD5PBQY3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGQYDINJVUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18440455>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFM6T6OUCJ6HSBC5FSCKIS35PBQY3AVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRQGMYDEMBSGA5UI2LTMN2XG43JN5XDWMJQG44TKNBUHGQXMAQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[nulledy]

v0.1.0 (552) is going out now with the following fixes:

• Add a dedicated server-wide per-camera notification toggles page in the app settings (requires being logged in as an admin)
• Clarify VPN/Tailscale notification reachability and addresses when initially setting up the server connection
• Don't re-race Home/Away URLs if both are accessible, which can cause review clips to fail to play

[derekboreman]

Do you have a way I can send you a video so you can see what it’s doing? Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: nulledy ***@***.***> Sent: Monday, 14 September 2026 16:53:18 To: 3rdBitLabs/Fregata ***@***.***> Cc: derekboreman ***@***.***>; Mention ***@***.***> Subject: Re: [3rdBitLabs/Fregata] Fregata Mobile for iOS - Beta Access (Discussion #83) v0.1.0 (552) is going out now with the following fixes: * Add a dedicated server-wide per-camera notification toggles page in the app settings (requires being logged in as an admin) * Clarify VPN/Tailscale notification reachability and addresses when initially setting up the server connection * Don't re-race Home/Away URLs if both are accessible, which can cause review clips to fail to play — Reply to this email directly, view it on GitHub<#83?email_source=notifications&email_token=AFM6T6J5CDFC4OJ6ZU34IOT5PBSE5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGQYDKMZYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18440538>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFM6T6OPDPDH2JLY64OR2T35PBSE5AVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRQGMYDEMBSGA5UI2LTMN2XG43JN5XDWMJQG44TKNBUHGQXMAQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[nulledy]

0.1.0 (552) should fix your issue, if it doesn't let us know. You should see it in Testflight now. You can send the engineering team screenshots in Testflight. For video you'd probably need to send those via email if you don't want to post them publicly for privacy reasons. If you aren't a Fregata Server user and need our email address, let us know.

[derekboreman]

Let me know. It’s a 30 second screen grab so. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: nulledy ***@***.***> Sent: Monday, 14 September 2026 17:02:19 To: 3rdBitLabs/Fregata ***@***.***> Cc: derekboreman ***@***.***>; Mention ***@***.***> Subject: Re: [3rdBitLabs/Fregata] Fregata Mobile for iOS - Beta Access (Discussion #83) 0.1.0 (552) should fix your issue, if it doesn't let us know. You should see it in Testflight now. You can send the engineering team screenshots in Testflight. For video you'd probably need to send those via email if you don't want to post them publicly for privacy reasons. If you aren't a Fregata Server user and need our email address, let us know. — Reply to this email directly, view it on GitHub<#83?email_source=notifications&email_token=AFM6T6MIPDQPIIUAM2TH2ED5PBTGXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGQYDMMRVUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18440625>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFM6T6MAFWXRIWDFEVVTKUL5PBTGXAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRQGMYDEMBSGA5UI2LTMN2XG43JN5XDWMJQG44TKNBUHGQXMAQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[derekboreman]

No I have a video but it’s like 15 mb so I don’t know how to get it to you. I’m sure if you see it this would make sense and you guys would know right where to look. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: nulledy ***@***.***> Sent: Tuesday, 15 September 2026 09:42:51 To: 3rdBitLabs/Fregata ***@***.***> Cc: derekboreman ***@***.***>; Mention ***@***.***> Subject: Re: [3rdBitLabs/Fregata] Fregata Mobile for iOS - Beta Access (Discussion #83) Any luck with the latest versions @derekboreman<https://github.com/derekboreman>? — Reply to this email directly, view it on GitHub<#83?email_source=notifications&email_token=AFM6T6LLMONBKCNHPLG7LQD5PFIOXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGUYTGMZTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18451333>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFM6T6M6CXPXMCP22JSEMCD5PFIOXAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRQGMYDEMBSGA5UI2LTMN2XG43JN5XDWMJQG44TKNBUHGQXMAQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[derekboreman]

Sent! Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Derek Boreman ***@***.***> Sent: Tuesday, 15 September 2026 09:53:43 To: 3rdBitLabs/Fregata ***@***.***> Subject: Re: [3rdBitLabs/Fregata] Fregata Mobile for iOS - Beta Access (Discussion #83) No I have a video but it’s like 15 mb so I don’t know how to get it to you. I’m sure if you see it this would make sense and you guys would know right where to look. Get Outlook for iOS<https://aka.ms/o0ukef>

________________________________ From: nulledy ***@***.***> Sent: Tuesday, 15 September 2026 09:42:51 To: 3rdBitLabs/Fregata ***@***.***> Cc: derekboreman ***@***.***>; Mention ***@***.***> Subject: Re: [3rdBitLabs/Fregata] Fregata Mobile for iOS - Beta Access (Discussion #83) Any luck with the latest versions @derekboreman<https://github.com/derekboreman>? — Reply to this email directly, view it on GitHub<#83?email_source=notifications&email_token=AFM6T6LLMONBKCNHPLG7LQD5PFIOXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGUYTGMZTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18451333>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFM6T6M6CXPXMCP22JSEMCD5PFIOXAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRQGMYDEMBSGA5UI2LTMN2XG43JN5XDWMJQG44TKNBUHGQXMAQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[nulledy]

@derekboreman got it, thanks. Could you also email over the full app log after reproducing this and lettings it run for ~25 secs like you did in the video? Settings > Diagnostics > Copy button in the top right corner.

[derekboreman]

I sent it! If you have any other questions I’ll have some time later to send answers or test other things. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: nulledy ***@***.***> Sent: Tuesday, 15 September 2026 10:39:02 To: 3rdBitLabs/Fregata ***@***.***> Cc: derekboreman ***@***.***>; Mention ***@***.***> Subject: Re: [3rdBitLabs/Fregata] Fregata Mobile for iOS - Beta Access (Discussion #83) @derekboreman<https://github.com/derekboreman> got it, thanks. Could you also email over the full app log after reproducing this and lettings it run for ~25 secs like you did in the video? Settings > Diagnostics > Copy button in the top right corner. — Reply to this email directly, view it on GitHub<#83?email_source=notifications&email_token=AFM6T6JLIL6QZNNKOFTVI5L5PFPBNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGUZDCMRZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18452129>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFM6T6NMQ5NAG27MRD3QU2T5PFPBNAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRQGMYDEMBSGA5UI2LTMN2XG43JN5XDWMJQG44TKNBUHGQXMAQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[nulledy]

v0.1.0 (568) is going out now with the following fixes:

• Add a software video decoder for when hardware video decoding fails @jm1175
• Speed up fallbacks when video playback fails Hardware Decoding Main Stream > Software Decoding Main Stream > Fallback to detect or adaptive transcoding streams > JSMPEG Stream
• Fix the order available live streams are shown and played to ensure the main highest quality stream is always tried first
• Fallback to JSMPEG on go2rtc errors
• Extend review clip timeout to prevent the app from restarting the stream too early @derekboreman

[nulledy]

v0.1.0 (579) is going out now with the following fixes:

• Further optimize loading of recording clips on slower connections (This actually went out in 0.1.0 (570))
• Group frame slices together into a single frame before handing off to the decoder for live streams. Should help with non-standard HTTP-FLV streams from some Reolink cams

[nulledy]

v0.1.0 (601) is going out now with the following fixes:

• Further optimizations to playing back review clips and scrubbing on a slow connection
• Prevent one bad/corrupted GOP frame from marking the live stream as undecodable
• Additional fixes for decoding Reolink's sliced HEVC encoding
• Crash fix fromTestFlight report (thanks!)

[nulledy]

v0.1.0 (626) is going out now with the following fixes:

• Prevent audio getting out of sync from video causing stutters in playback
• Add additional guards to keep audio and video in sync to work around a go2rtc bug
• Reviews get a new review details button that shows the GenAI description (if available) and an object by object timeline within the review
• When clicking a notification, don't load the review list before jumping to the review itself. Mainly applies to slower connections
• Add more event details to the event details page
• Add date and time filter to the Explore tab
• Add date and time filter to the Review tab