Multiple Birdseye Views

[DaCeige]

Describe what you are trying to accomplish and why in non technical terms I want to be able to define multiple birdseye views to separate my cameras. I would like an 'inside' and and 'outside' birdseye view with my cameras separated to each. In theory, I would like a third that still has all the cameras on it.

Describe the solution you'd like I would like to be able to define multiple birdseye views per camera. Example:

# Optional: birdseye configuration
# NOTE: Can (enabled, mode) be overridden at the camera level
birdseye:
  # Optional:  Specify which birdseye views this camera should be added to (default: all cameras)
  views:
    - inside cameras
    - all cameras
    - outside cameras

Describe alternatives you've considered I consider setting up a separate frigate instance, but as I understand it, I would not be able to 'share' one coral interface between them. Alternatively, using the newer code, I could potentially separate the detector to run 2 frigate instances with one coral, but that seems overly complicated.
Alternatively, could create a matrix view using individual cameras on a HA dashboard.

Additional context Basically looking for a way to create a matrix view that contains different cameras. Outside cameras are more useful during the day, inside at night and when we're away.

[toxic0berliner]

Would love that too!

[psilantropy]

Came here to post this idea also. My use-case is similar. 6 cameras, 4 outdoor, 2 indoor. With indoor cameras only activated when we are not home.

I found having 6+ cameras in a birdseye view was too many cameras for my liking. I also want these views to all be continuous.

• birdseye1 = dog cam view
• birdseye2 = outdoor x4 view

[blackgold9]

+1 here

[tomgit33]

+1 -> 4 Cams each group, selectable/sortable

[michaellammers]

+1

[nzkiwi68]

Another up vote up for multiple Birdseye views.

I have a use case for a large scale Frigate deployment to replace 4 x NVR's running ~120 cameras. This use case will need 4 or more Frigate servers, but, it will need the ability to have views.

Show me on Frigate server1:

• entrance cameras
• checkout cameras
• yard cameras

Show me on Frigate server2:

• checkout cameras
• loading dock cameras
• building2 outdoor cameras
• building2 internal cameras

etc...

This feature request plus Authorisation Roles #6614 are the two features that I believe will lift Frigate up to make large scale Frigate possible.

Recommendation: Make this a part of "Frigate+".

Thanks for an amazing product!

[markfrancisonly]

Make this a part of "Frigate+"

Can't say I agree with paywalling core features of an open source product. I'm ready to abandon a 15 year use of pfsense for opnsense because the open source aspect of the pfsense product has died with netgate's plus model.

[toxic0berliner]

If it ain't the 20 years old UI that moved you away and towards opnsense then I don't really get you 🤣 I do believe authorization roles can understandably be more of an enterprise feature and therefore paid, but several birdseye for me makes a lot of sense for a lot of small OpenSource free consumers given frigate works well on cheap hardware with cheap cameras it can easily grow to over 9 cams and 2 birdseye make sense. I can setup a frigate with 12 cams for less than $500 wich can make a lot of sense for individuals that don't want a subscription and would still need or at least badly want 2 or more birdseye...

That being said frigate is awesome and I'd gladly pay 50€/year for the privilege of using it as I please on hardware I own and choose

[markfrancisonly]

@toxic0berliner not sure you responded to my concern, but yeah, supporting the devs is cool, breaking the product into a closed-source / open-source model not so much. btw, nice username

[toxic0berliner]

Hmmm, maybe I missed something @NickM-27 but in your PR I read the groups are a per-device setting I don't see how this can close having multiple birdseye request... Maybe I made too many assumptions but I would have expected a way to define birdseyeN in the config as showing came,came and so on, so in the end I could have 3 stream urls birdseye1 birdseye2 and 3 for instance. In your PR I seem to see all is happening in the frontend, am I wrong?

[NickM-27]

to be clear it was not my PR but @hawkeye217

in general birdseye acted as a way to view multiple cameras and see activity that is occurring on each of those cameras. The camera groups are a shared global config, the only thing that is device specific is changing the layout itself. This should serve the vast majority of use cases requiring multiple split camera views and easily being able to switch between them. If there is some birdseye specific use case where the frigate frontend is not usable then I think a new feature request should be created to define that explicitly. The PR linked solves the original request (Basically looking for a way to create a matrix view that contains different cameras. Outside cameras are more useful during the day, inside at night and when we're away.)

[nzkiwi68]

Just thinking...

Allow an optional "TAG" field to each camera under birdseye. Multiple birdseye views would be created, one for each tag name.

cameras:
  entrance:
    ui:
      order: 1
    birdseye:
      order: 1
      tag:
      - outdoor

Add multiple BirdEye views, views based on cameras with the tag of, say "carpark" or "outdoor". With tags, then, one camera could even be present in multiple views.

cameras:
  entrance:
    ui:
      order: 1
    birdseye:
      order: 1
      tag:
      - outdoor
      - carpark