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 entity update delay #705

Open
cigas4 opened this issue Aug 20, 2024 · 10 comments
Open

Image entity update delay #705

cigas4 opened this issue Aug 20, 2024 · 10 comments

Comments

@cigas4
Copy link

cigas4 commented Aug 20, 2024

Hello,

I have noticed issue after Frigate update to 0.14.0-da913d8 version:
Image entities provided by Frigate integration (version 5.3.0) in HomeAssistant are updated with a delay. Looks like new motion picture is loaded to HA picture entity only when motion is already cleared. On earlier Frigate versions picture entity was updated with new picture at the same moment when motion is detected.

I have motion notifications set up with these image entities as an attachment and now after update it does not work as intended. Normally, when motion is detected by Frigate, at the very same moment, notification with picture entity is sent to my phone. After this update I have started receiving motion notifications including old motion picture (some hours or days old), because picture entity is not yet updated with current motion picture.
As a temporary solution I have to modify my automations, so when motion is detected I have to wait until motion is cleared, only then I can send notification which will include picture with updated picture entity.

Motion

HA is running in Proxmox VM:
Core 2024.8.2
Supervisor 2024.08.0
Operating System 13.0
Frontend 20240809.0

Frigate is running in Proxmox LXC in docker container.

@Benjamin-299
Copy link

@cigas4 I started noticing this same issue several days ago (about a week - never notated the exact date).

I run a HAOS VM inside of proxmox. Frigate runs as an add on of HA, and my notifications are done within nodered. At first I thought it was just a slight delay in the update of the image entity. Tried adding a few second delay before sending the notifications, but didn't help.

Hadn't done much digging yet till this morning and saw this - Believe we are having the same issues. Somehow I had never thought to compare the time stamps between the entities changing! At a glance this morning, it does seem like the person image entity is only updating AFTER the person object has cleared.

Glad to know I'm not alone on this one.

@Benjamin-299
Copy link

@cigas4
Did a bit more investigating here.

My frigate instance (ha addon) is not sending the mqtt message with a person snapshot until the person even has cleared.

Believe this will actually be an issue within Frigate directly, and not the integration.

@NickM-27
Copy link
Collaborator

see the related discussion. Nothing has changed regarding this in frigate so it is not clear why the behavior would be any different blakeblackshear/frigate#11696 (reply in thread)

@mathmaniac43
Copy link

I have been experiencing the same problem, and just fully diagnosed it today. The image is not updated in HA until motion is cleared.

@DastardlyDino
Copy link

Commenting to follow. I have the same issue

@yzjJosh
Copy link

yzjJosh commented Sep 15, 2024

I'm having the same problem.

@TRusselo
Copy link

same here.

as a workaround i changed my home assistant automation
I added first action "wait for trigger" wait for frigate image to change state.

`action:

  • wait_for_trigger:

    • platform: state
      entity_id:
      • image.driveway_person
  • data:
    message: A person has been detected in the Front Yard.
    data:
    clickAction: entityId:camera.blueiris_front_yard
    image: /api/image_proxy/image.driveway_person
    entity_id: image.driveway_person
    actions:
    - action: URI
    title: Open Camera
    uri: entityId:camera.blueiris_front_yard
    tag: person-front
    title: Person Detected
    action: notify.mobile_app_tristyn_s_note_20`

    this results in a 10-30 second delay...
    GROSS!

Copy link

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 Oct 17, 2024
@mathmaniac43
Copy link

This is still a problem.

@cigas4
Copy link
Author

cigas4 commented Oct 17, 2024

This is still a problem.

Same here.

@github-actions github-actions bot removed the Stale label Oct 18, 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

7 participants