LLM Vision Blueprint 1.4.0: Important Updates & Changes
Blueprint requires LLM Vision 1.4.0.
The LLM Vision Blueprint has received a major update in version 1.4.0 with significant changes and new features. Please review the updates carefully before upgrading.
Breaking Changes
Frigate Mode Removed: The blueprint no longer supports Frigate mode. However, you can still use Frigate by utilizing camera entities and binary sensors from the Frigate integration.
Deprecated Options:
input_mode has been removed
**detail**has been removed. Use target_width to control the resolution of images.
New Features
Run Condition: Set custom conditions to control when the blueprint runs (e.g., only when no one is home or when the alarm is enabled).
Notification Delivery Modes:
Dynamic: Sends an initial live camera preview notification, then silently updates with the summary. (Live Preview not compatible with Android)
Consolidated: Sends a single notification when the summary is ready.
Use Memory Toggle: Enables access to stored information for improved context and automation.
How to Update
Re-import the updated blueprint.
Review and adjust your settings according to the new structure.
Read the full release notes here. Happy automating!
@valentinfrich These are welcome changes. However, I get the following log errors with no notification generated.
Error while executing automation automation.ai_event_summary_llm_vision_v1_3_8: Error rendering data template: UndefinedError: ‘dict object’ has no attribute ‘key_frame’
7:33:12 AM – (ERROR) Automation
AI Event Summary (LLM Vision v1.3.8): Choose at step 6: choice 1: (Snapshot) Update notification on notify devices: Error executing script. Error for call_service at pos 1: Error rendering data template: UndefinedError: ‘dict object’ has no attribute ‘key_frame’
7:33:12 AM – (ERROR) Automation - message first occurred at 7:33:12 AM and shows up 3 times
Template variable warning: ‘dict object’ has no attribute ‘title’ when rendering ‘{{response.title}}’
7:33:12 AM – (WARNING) helpers/template.py - message first occurred at 7:33:12 AM and shows up 2 times
@valentinfrlch Yes, I have done that. I have also deleted the original automation and created a new one with the updated blueprint. I get the same errors.
Error while executing automation automation.ai_event_summary_v1_4_0: Error rendering data template: UndefinedError: ‘dict object’ has no attribute ‘key_frame’
8:14:27 AM – (ERROR) Automation
AI Event Summary (v1.4.0): Choose at step 6: choice 1: (Snapshot) Update notification on notify devices: Error executing script. Error for call_service at pos 1: Error rendering data template: UndefinedError: ‘dict object’ has no attribute ‘key_frame’
8:14:27 AM – (ERROR) Automation - message first occurred at 8:14:27 AM and shows up 3 times
Template variable warning: ‘dict object’ has no attribute ‘title’ when rendering ‘{{response.title}}’
8:14:27 AM – (WARNING) helpers/template.py - message first occurred at 8:14:27 AM and shows up 2 times
I also had a question regarding the timing and responsiveness of the notification. As an example, if a car drives up my driveway, most of the time the notification I get is “No vehicles or people detected” and the snapshot sent is usually an image after the event has already taken place. I’m wondering if it’s the number of snapshots sent or the recording period which needs to be changed? I currently have it at 3 frames over 3 seconds.
You can now use the image and camera entities exposed by the frigate integration directly. If you use frigate, you’ll also have some binary_sensors for motion and object detection. You can use those as ‘Motion Sensors’. The automation will then be triggered when one of those sensors changes to on. Keep in mind that the order of the cameras and motion sensors must be the same if you have multiple.
Breaking Changes
New Features
How to Update