You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
(Blueprint) Snapshot preview shows wrong camera when multiple cameras are configured #739
I'm running the newest version of LLM Vision. (v1.7.2 per HACS. Note: the v1.7.2 tag's manifest.json still says 1.7.1; see comment below.)
I have enabled debug logging for the integration. (Not relevant here: the integration behaves correctly. The bug is in the blueprint's templates. See "Logs" below.)
I have filled out the issue template to the best of my ability.
This issue only contains 1 issue.
This is a bug and not a feature request.
I have searched open issues for my problem.
Describe the issue
(Blueprint) With more than one camera in camera_entities, the Snapshot preview notification shows the wrong camera. Sometimes it shows a broken image.
Cause, in blueprints/event_summary.yaml:
camera.snapshot targets every camera in camera_entities, not just the one that triggered.
camera_file_path is always built from camera_entities_list[0].
So every camera writes to the first camera's last_motion.jpg. The notification attaches whichever camera wrote last. If the phone fetches the file while it's being rewritten, you get a broken image.
Reproduction steps
Set up the AI Event Summary blueprint with two cameras (e.g. camera.front_yard_camera, camera.right_camera) and their motion sensors, Preview mode = Snapshot.
Trigger motion on the second camera only.
Notification says "Right camera has detected activity." but the thumbnail is from the front yard camera. Sometimes it's a broken image.
Logs
No integration error: the integration does what the blueprint asks. Related note: the obvious one-line fix (entity_id: "{{ camera_entity }}" on the legacy service: form) is rejected by config validation:
Blueprint 'AI Event Summary (v1.6.0)' generated invalid automation ...: not a valid value for dictionary value @ data['actions'][2]...['sequence'][0]['entity_id']. Got '{{ camera_entity }}'
so the fix needs target: entity_id:.
Fix
PR #738 snapshots only camera_entity (via target:) and builds camera_file_path from it.
Correction: I am on v1.7.2, not 1.7.1. HACS reports v1.7.2 installed.
I got confused because the v1.7.2 tag still has "version": "1.7.1" in custom_components/llmvision/manifest.json, so the installed files say 1.7.1. You may want to bump that in the next release, since HA shows the manifest version on the integration page.
I updated the checklist above. This bug is still present on v1.7.2 and on main.
Activity
zestysoft commentedon Sep 27, 2026
Correction: I am on v1.7.2, not 1.7.1. HACS reports v1.7.2 installed.
I got confused because the
v1.7.2tag still has"version": "1.7.1"incustom_components/llmvision/manifest.json, so the installed files say 1.7.1. You may want to bump that in the next release, since HA shows the manifest version on the integration page.I updated the checklist above. This bug is still present on v1.7.2 and on
main.