Replies: 4 comments 1 reply
-
Hi @tjorim, Thank you for bringing this up! I’m pleased to let you know that in the latest release (v1.04), we’ve addressed this issue. The integration now checks whether the configured scan_frequency has passed before triggering a new persistent notification when restarting Home Assistant or reloading the integration. This should prevent unnecessary notifications from being generated when no new scan is required. |
Beta Was this translation helpful? Give feedback.
-
I can see this has come back after the code review. Will look to resolve this with better frequency settings as they may chew through GPT tokens. |
Beta Was this translation helpful? Give feedback.
-
Testing.... V1.07 Now Provides these asks: Removal of Automatic Scheduling: Removed automatic scanning and suggestion generation due to complexities with triggering and user preferences. Expanded AI Provider Support: Added Support for Multiple LLM Models: Custom LLM Variants: Integration Selection: Users can now select which AI provider integration to trigger when manually initiating the AI analysis. Global Reach: Introduced German language support to make the integration accessible to a wider audience. |
Beta Was this translation helpful? Give feedback.
-
This is still happening during rebooting in V1.08. It's because Home Assistant is reloading the integration. I'll continue to workout how this might be prevented in future releases. For now I will move this issue to upgrade requests. |
Beta Was this translation helpful? Give feedback.
-
When restarting HA (or reloading the integration) it gets triggered and creates a new persistent notification, even when the set scan frequency hasn't passed.
Beta Was this translation helpful? Give feedback.
All reactions