Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image entities with zone (camera_zone_object and zone_object) #679

Open
Mincka opened this issue May 12, 2024 · 11 comments
Open

Image entities with zone (camera_zone_object and zone_object) #679

Mincka opened this issue May 12, 2024 · 11 comments

Comments

@Mincka
Copy link

Mincka commented May 12, 2024

Is your feature request related to a problem? Please describe.
It would be great to have image entities per object type for each zone (of each camera or globally).

Currently, they are created per object type for each camera.
The issue is that you may not want to update the image when the object is not in the zone you want.
Also, you may want the latest object event in a specific zone that is covered by multiple cameras.

image.camera_zone_object
Use case: I have one camera in the garden, but I would like to show on my dashboard the latest image of someone in the garden zone, not in the crop_field zone.

image.zone_object
Since we have sensors for zones (occupancy and count), I think it could be great to also have image.
Use case: I would like to show on my dashboard the image of the latest person in my garden with two cameras pointing to it.

Describe the solution you'd like
Create additional entities with this format (camera_zone_object):

  • image.frontyard_street_car
  • image.frontyard_street_person
  • image.frontyard_driveway_car
  • image.frontyard_driveway_person

Create additional entities with this format (camera_zone_object):

  • image.street_car
  • image.street_person
  • image.driveway_car
  • image.driveway_person

Describe alternatives you've considered
Snapshot manually the camera entity on MQTT event.

Additional context
None

@NickM-27
Copy link
Sponsor Collaborator

The issue is that you may not want to update the image when the object is not in the zone you want.

This can already be controlled by MQTT -> required_zones in the frigate config

@Mincka
Copy link
Author

Mincka commented May 12, 2024

I am not sure how it would help for this specific issue.
I am already doing MQTT filtering myself based on the zone and other attributes of the payload to trigger the alarm.

Do you mean that using required_zones in the MQTT section would change how the integration is updating the image entity of a camera?

Like I wrote, as an alternative solution, I can snapshot the camera for a specific zone and save it somewhere as camera_zone_person_latest.jpg. Or more precisely, use the image_best_snapshot of the latest event that matched my criteria, and again, save it somewhere as the latest one.

@NickM-27
Copy link
Sponsor Collaborator

along with snapshot -> required_zones and record -> events -> required_zones frigate also has mqtt -> required_zones which controls what zones an object must enter to update the mqtt image entity.

@Mincka
Copy link
Author

Mincka commented May 13, 2024

Ok thank you. That's not what I need because the image and zone I need depend on the scenario.
E.g.: MQTT image used by Double Take for processing, but not in a specific zone while I'd like an image of the latest person in a specific zone on my HA dashboard.

@PablaV
Copy link

PablaV commented May 31, 2024

I second this request..

Copy link

github-actions bot commented Jul 1, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Jul 1, 2024
@Mincka
Copy link
Author

Mincka commented Jul 1, 2024

Still interested

@github-actions github-actions bot removed the Stale label Jul 2, 2024
Copy link

github-actions bot commented Aug 1, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Aug 1, 2024
@Mincka
Copy link
Author

Mincka commented Aug 3, 2024

Still interested

@github-actions github-actions bot removed the Stale label Aug 4, 2024
Copy link

github-actions bot commented Sep 3, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Sep 3, 2024
@Mincka
Copy link
Author

Mincka commented Sep 5, 2024

Still interested

@github-actions github-actions bot removed the Stale label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants