AI Automation Suggester

An AI‑powered assistant for Home Assistant that leverages large language models to understand your unique smart home environment – your entities, areas, devices, and existing automations. It proposes intelligent, actionable YAML suggestions tailored to your specific setup, helping you unlock your home's full potential.

---

✨ Why does this exist? (Purpose and Problem Statement)

As your Home Assistant setup grows, managing its complexity and identifying new opportunities for automation can become challenging. You might find yourself with:

• Too many possibilities: Every new device adds countless potential interactions.
• Automation "Writer's Block": Translating a complex idea into functional YAML can be daunting.
• Underutilized Potential: Many devices sit idle or require manual control because the right automation hasn't been thought of or created.
• Maintenance Overload: Keeping existing automations relevant as your home evolves is difficult.

The result is often an under-automated house despite having powerful hardware.

The Fix – Your Personal Automation Copilot

The AI Automation Suggester integration solves these challenges by acting as a personal automation consultant. It intelligently analyzes your Home Assistant instance to:

1. Analyze your home's state: Understand your devices, their capabilities, locations, and existing automations.
2. Identify opportunities: Spot gaps, synergies, and potential improvements for energy saving, security, comfort, and convenience.
3. Draft ready-to-paste YAML: Provide concrete, tailored automation ideas as YAML snippets you can review, tweak, and implement directly.

In essence, this integration turns the complexity of a large Home Assistant environment into actionable insights and tangible benefits, guiding you toward a more efficient, comfortable, and secure smart home.

---

🚀 How It Works (The Solution)

The integration follows a simple, effective process:

Step	What happens?	Details
1 · Snapshot	Collects data about your home.	On manual trigger or schedule, the integration gathers information on your entities (including attributes), devices, areas, and existing automations. You can control the scope using filters and limits.
2 · Prompt Building	Structures the data for the AI.	This snapshot is embedded into a detailed system prompt describing your specific Home Assistant setup. You can enhance this with a custom prompt to steer suggestions towards specific goals (e.g., "focus on presence lighting").
3 · Provider Call	Sends the prompt to the AI.	The crafted prompt is sent to your configured AI provider (OpenAI, Azure OpenAI, Anthropic, Google, Groq, LocalAI, Ollama, Mistral, Perplexity, OpenRouter, Requesty, MiniMax, LiteLLM, or another OpenAI-compatible endpoint).
4 · Parsing	Processes the AI's response.	The integration asks capable providers for structured JSON, falls back to fenced YAML parsing, validates returned YAML, and records warnings for missing or possibly truncated output.
5 · Surface	Delivers and stores the suggestions.	Suggestions appear as Home Assistant persistent notifications, sensor attributes, and stored history that can be used by the bundled dashboard card or your own cards.

Randomized entity selection (configurable) helps ensure each analysis run can surface fresh ideas rather than repeating the same suggestions.

---

📸 What to Expect (Screenshots)

Suggestions are delivered directly within Home Assistant notifications:

You can also build custom dashboard cards to display suggestions using sensor attributes:

Here's an example of displaying suggestions on a dashboard:

---

🏆 Benefits

Leveraging the AI Automation Suggester provides several key benefits:

• Time Saving: Reduces the effort and guesswork involved in designing complex automations.
• Context-Aware Suggestions: Ideas consider your specific devices, areas, and current setup for realistic, tailored recommendations.
• Model-Agnostic Flexibility: Supports cloud and local AI models, letting you choose based on cost, privacy, and performance preferences.
• Improved Usability: Makes automation creation more accessible, even for users less familiar with YAML.
• Dynamic Inspiration: Provides fresh ideas as your home and devices change, keeping your automations evolving.
• Enhanced Control: Custom prompts, entity limits, and domain filters give you command over the suggestion generation process.
• Safe to Try: Suggestions are presented for review; nothing is automatically implemented without your explicit action.

---

📦 Features

• Multi-Provider Support: Connect to OpenAI, OpenAI Azure, Anthropic, Google, Groq, LocalAI, Ollama, Mistral, Perplexity, OpenRouter, Requesty, MiniMax, or LiteLLM (100+ backends) with full configuration options:
  • Temperature control for all providers (0.0 - 2.0)
  • Model selection with provider-specific defaults
  • Secure API key storage
  • Custom endpoints for compatible providers
  • Ollama's Disable Think option sends native think: false and the legacy /no_think prompt hint. Leaving it off preserves the model's default thinking behavior.
• Customizable Prompts and Filters: Tailor suggestions using system prompts, domain filters, and entity limits.
• Persistent Suggestion History: Retain recent suggestions with provider/model metadata, review status, warnings, and generated YAML.
• Review Actions: Mark stored suggestions as accepted, declined, or dismissed through services or the bundled dashboard card.
• Randomized Entity Selection: Prevent repetitive suggestions and discover new opportunities.
• Context-Rich Insights: Incorporates device and area information for smarter, more relevant ideas.
• Persistent Notifications: Receive suggestions directly in your Home Assistant interface.
• Service Call Integration: Manually trigger suggestions via the ai_automation_suggester.generate_suggestions service with full parameter control.
• Diagnostics Sensors: Monitor suggestion status and provider connection health.
• Example Automations: Includes YAML examples for new entity detection and weekly reviews. Import and enable them yourself; the integration does not install automations or a schedule.
• Dashboard-Friendly Output: Sensor attributes provide description and YAML blocks ready for Lovelace cards.

---

🛠️ Prerequisites

• Home Assistant: Version 2024.1 or later.
• AI Provider Setup: You will need access to an AI model.
  • For cloud providers (OpenAI, Anthropic, Google, Groq, Mistral, Perplexity, OpenRouter, Requesty, MiniMax), you will need API keys.
  • For local models (LocalAI, Ollama), ensure the local servers are running and accessible from Home Assistant.

---

⬇️ Installation

HACS (Recommended)

1. Install HACS if you haven't already.
2. In HACS → Integrations, click the + button.
3. Search for AI Automation Suggester.
4. Select the integration and click Download.
5. Restart Home Assistant.
6. Go to Settings → Devices & Services → + Add Integration and search for AI Automation Suggester.

When a GitHub release is published, HACS can detect the new version and show it as an available update. Update through HACS, then restart Home Assistant so the custom integration is reloaded.

Manual Installation

1. Download the contents of this repository.
2. Copy the custom_components/ai_automation_suggester folder to your Home Assistant custom_components directory.

   <homeassistant_config_dir>/
   └── custom_components/
       └── ai_automation_suggester/
           ├── __init__.py
           └── ... (other files)
   

3. Restart Home Assistant.
4. Go to Settings → Devices & Services → + Add Integration and search for AI Automation Suggester.

---

⚙️ Configuration

1. Add the integration via the Home Assistant UI: Settings → Devices & Services → + Add Integration → AI Automation Suggester.
2. Follow the setup wizard:
   • Select your AI Provider: Choose from the dropdown list.
   • Enter API Keys or Endpoint: Provide the necessary credentials or local server URL based on your provider choice.
   • Select Model: Choose the specific model variant you wish to use.
   • Set Max Tokens: Define the maximum length for the AI's response (influences the length of suggestions).
   • (Optional) Custom System Prompt: Provide an initial prompt to guide the AI's overall perspective (e.g., "You are an expert in energy-saving automations for smart homes.").

You can adjust these settings later via the integration options in Settings → Devices & Services.

---

🛠️ Advanced Configuration

Global Settings

• Temperature Control:

  • Available for all providers
  • Range: 0.0 (more focused) to 2.0 (more creative)
  • Default: 0.7
  • Configurable in both initial setup and options

• Token Management:

  • Separate input/output token limits
  • Prevents excessive API usage
  • Optimizes response length
  • Defaults remain 500 tokens per budget for compatibility. For reasoning models or missing/truncated YAML, try 16000 input tokens and 4096 output tokens with a small entity limit, then adjust within your model's limits.
  • Reasoning may consume output tokens before the final YAML is produced. Higher limits can increase usage and cost. Limits are ceilings, not measurements of billed tokens. Check your provider's usage dashboard and current pricing.
  • When a provider reports that it stopped at the output limit (for example Gemini MAX_TOKENS, Anthropic max_tokens, Ollama length, or OpenAI-compatible length), the suggestion includes a truncation warning. If the provider returned no final answer at all, the action fails with a message naming your configured Max Output Tokens value, instead of a generic parsing error.

• History and Filtering:

  • Persistent custom system prompt
  • Excluded domains, entities, and areas
  • Stored suggestion history retention
  • Provider request timeout for slow local or research models, in seconds. Default: 900. Minimum: 10. There is no maximum, so 7200 allows a two-hour request. Zero does not disable the timeout.

---

Supported Providers and Model Notes

Model APIs change quickly, so the integration keeps a compatibility catalog and still allows custom model names. Existing configured model values are preserved on upgrade.

Provider	New default for new configs	Compatibility notes
OpenAI	gpt-5.4-mini	GPT-5 and later models (including GPT-6, such as gpt-6.1-sol) and o-series models use the Responses API, max_output_tokens, and reasoning effort. Temperature is not sent to models known to reject it. Other models use Chat Completions with max_completion_tokens. gpt-5.5 and gpt-5.5-pro are supported when available on your account.
Azure OpenAI	gpt-5.4-mini deployment name	Azure uses deployment names. Configure the deployment ID, endpoint, and API version that match your Azure resource.
Anthropic	claude-sonnet-5-5	Catalog includes Sonnet/Opus/Haiku 5.5 and Fable 5.1. Saved legacy and custom model IDs are preserved. Temperature is no longer sent; the obsolete setup/options control has been removed.
Google Gemini	gemini-3.5-flash	Stable replacement for Gemini 2.5 Flash, which is unavailable to new users. Custom model IDs are still allowed.
Groq	openai/gpt-oss-120b	Replaces llama-3.3-70b-versatile, retired for free/developer accounts on 2026-08-16. openai/gpt-oss-20b is another production option. qwen/qwen3.6-27b is a preview alternative. Enterprise Llama access may remain.
Mistral AI	mistral-small-latest	Supports current *-latest aliases and custom published IDs.
Perplexity AI	sonar	Supports Sonar, Sonar Pro, reasoning, and research-style model IDs where your account has access.
OpenRouter	openai/gpt-5.4-mini	OpenRouter remains dynamic. Use provider-prefixed IDs from OpenRouter's model catalog. openrouter/free (the Free Models Router) receives the structured-output schema, so OpenRouter only routes it to free models that support structured outputs.
Requesty	openai/gpt-4o-mini	OpenAI-compatible router (https://router.requesty.ai) providing 300+ models through a single API key. Use provider-prefixed model IDs.
Cheaper Inference	gpt-5.4-mini

For maximum stability, prefer stable model IDs over preview or latest aliases unless you intentionally want fast-moving behavior.

Claude 4.7-and-later and OpenAI GPT-5-and-later / o-series model names omit temperature through OpenRouter, Requesty, Cheaper Inference, LiteLLM, and custom OpenAI-compatible APIs too. Other routed models retain their configured temperature. The direct Anthropic provider omits temperature for every model, including saved legacy configurations: Anthropic API version 2026-10-21 removes sampling parameters, while newer Claude models already reject non-default sampling on older API versions. The integration still pins its direct HTTP requests to 2023-06-01; this release does not migrate the API version.

Upgrading does not replace saved model selections. If an existing Google or Groq entry returns a model-not-found error, open its integration options and select a current model above. Availability depends on your provider account. See Google's model catalog and Groq's deprecation notices.

The Anthropic provider uses API key authentication. A Claude Pro/Max subscription is not an API key or API credit balance. This integration does not collect Claude.ai session tokens or route requests through subscription credentials. See Anthropic's authentication requirements.

---

✍️ Usage

Automatic Suggestions

Suggestion generation is on demand. The integration does not run inference during startup or have a built-in polling interval. Automatic runs require an enabled Home Assistant automation that calls ai_automation_suggester.generate_suggestions.

The repository includes these examples, but HACS does not register them in your automation list:

• Weekly review: custom_components/ai_automation_suggester/automations/weekly-review-automation.yaml runs on Sundays at 03:00. Change the time and weekday condition to suit your schedule.
• New entity detection: custom_components/ai_automation_suggester/automations/new-entity-automation.yaml responds to entity registry events. It is not a periodic timer.

To install an example, go to Settings > Automations & scenes > Automations > Create automation > Create new automation, open Edit in YAML from the menu, and paste the example's YAML. Save and enable the automation. If you use multiple provider entries, select the intended Provider Configuration in the action editor.

For an optional run after each Home Assistant restart, create a separate automation with this YAML:

alias: AI Suggestions - After Startup
trigger:
    - platform: homeassistant
      event: start
action:
    - delay: "00:01:00"
    - service: ai_automation_suggester.generate_suggestions
      data:
        all_entities: true
        entity_limit: 50
        automation_read_yaml: false
        script_read_yaml: false
mode: single

The delay allows entities time to become available, but does not guarantee a provider is reachable. Every scheduled or startup run can incur API usage. Keep these triggers opt-in and avoid frequent retries after provider errors.

If manual generation works but automatic runs do not, check that the automation is enabled, its trigger and conditions match, and its Traces show the generation action being called. Use all_entities: true for periodic reviews; the default only considers entities not processed by the current integration instance. initializing alone does not mean a request is running.

Manual Trigger

You can trigger the suggestion generation manually using the service call:

1. Go to Developer Tools > Actions (called Services on older Home Assistant versions).
2. Select the service ai_automation_suggester.generate_suggestions.
3. Call the service. You can pass parameters to customize the request:
   • all_entities (boolean, default: false): Set to true to consider all eligible entities, false to only consider entities added since the last successful run.
   • domains (list of strings, optional): Limit the analysis to entities within specific domains (e.g., ['light', 'sensor']).
   • exclude_domains (list of strings, optional): Exclude domains even when considering all entities.
   • exclude_entities (list of entity IDs, optional): Exclude specific entities from analysis.
   • exclude_areas (list of area IDs/names, optional): Exclude areas from analysis.
   • entity_limit (integer, optional): Set a maximum number of entities the AI should consider in this run. Useful for controlling prompt length and cost.
   • custom_prompt (string, optional): Add a specific instruction for this particular run (e.g., "Suggest security automations for doors and windows.").
   • automation_read_yaml (boolean, optional): Include YAML from automations.yaml for deeper review.
   • automation_limit (integer, optional): Limit how many automations are included.
   • script_read_yaml (boolean, optional): Include YAML from scripts.yaml so the AI can reason about scripts you already have. Uses more input tokens — best paired with large-context models.
   • script_limit (integer, optional): Limit how many scripts are included (default: 100).

Suggestion Review Services

• ai_automation_suggester.clear_history: Clears stored suggestion history.
• ai_automation_suggester.update_suggestion: Updates a stored suggestion status. Supported statuses are new, accepted, declined, and dismissed.

The bundled dashboard card also uses these stored suggestion APIs:

• GET /api/ai_automation_suggester/suggestions
• POST /api/ai_automation_suggester/{accept|decline|dismiss}/{suggestion_id}

Dashboard Snippets

The main sensor (sensor.ai_automation_suggestions_<provider_name>) exposes useful attributes for display on dashboards. Replace <provider_name> with the name you gave the integration instance (e.g., openai, ollama).

• Displaying the Description:

  {{ state_attr('sensor.ai_automation_suggestions_<provider_name>', 'description') }}
  

• Displaying the YAML Block:

  {{ state_attr('sensor.ai_automation_suggestions_<provider_name>', 'yaml_block') }}
  

You can use Markdown cards or other card types to present this information cleanly in your Home Assistant dashboard.

---

📊 Monitoring & Diagnostics

The integration provides several sensors for monitoring:

• AI Automation Suggestions: (sensor.ai_automation_suggestions_<provider_name>)

  • State: No Suggestions, New Suggestions Available, Suggestions Available
  • Attributes:
    • description: Human-readable suggestion description
    • yaml_block: Ready-to-use automation YAML
    • last_update: Timestamp of last update
    • entities_processed: List of analyzed entities
    • entities_processed_count: Number of entities analyzed
    • suggestion_count: Number of retained suggestions
    • warnings: Parsing, model, or truncation warnings

• AI Provider Status: (sensor.ai_provider_status_<provider_name>)

  • State: connected, error, initializing
  • Reports the last provider request outcome, not continuous provider health. No inference is started during integration startup. initializing means no provider request outcome is available yet.
  • Attributes:
    • last_error_message: Details of any errors
    • last_attempted_update: Timestamp of last attempt

• Max Input/Output Tokens: (sensor.max_input_tokens_<provider_name>, sensor.max_output_tokens_<provider_name>)

  • Shows configured token limits
  • Helps monitor API usage

• AI Model: (sensor.ai_model_in_use_<provider_name>)

  • Shows current model configuration
  • Useful for multi-instance setups

• Suggestion History Count: (sensor.suggestion_history_count_<provider_name>)

  • Shows how many suggestions are stored in history
  • Includes latest suggestion ID and review status as attributes

• Last Error: (sensor.last_error_message_<provider_name>)

  • Detailed error tracking
  • Includes stack traces for unexpected errors

---

🔍 Error Handling & Troubleshooting

• Stack Traces:

  • Detailed error logging for unexpected issues
  • Available in Home Assistant logs
  • Helpful for debugging API issues

• Common Error Scenarios:

  • API authentication failures
  • Network connectivity issues
  • Token limit exceeded
  • Model availability problems
  • Response parsing errors

• Error Monitoring:

  • Use the Last Error sensor for real-time error tracking
  • Check Home Assistant logs for stack traces
  • Monitor provider status sensor for connection issues

• Debug Logging:

  • To capture the unparsed provider response for a bug report, enable debug logging, restart Home Assistant, and run one generation:

    logger:
      default: warning
      logs:
        custom_components.ai_automation_suggester: debug
    

  • Each generation logs the prompt size and entity count, then the raw response text with the provider's finish reason and token usage. Credentials are redacted. The response can include entity names, areas, and other household context, so review it before posting it publicly.

---

🔒 Security Notes

• API keys are stored in Home Assistant config entries and password fields are masked in the UI.
• Cloud providers may receive entity IDs, states, attributes, device/area context, automation metadata, and prompt text.
• This household context is intentionally retained so suggestions can be genuinely personal and useful. Provider error diagnostics redact authentication credentials, not names, rooms, states, or other home context.
• Local providers such as Ollama and LocalAI can keep model processing on your own network.
• Suggestions are review-only. This integration does not automatically create, accept, or modify automations.

---

Customization and Advanced Usage

Beyond the basic configuration and service call parameters, you can further customize the integration's behavior:

Random Entity Selection

The integration uses randomized entity selection within the entity limit, including when all_entities is true or an installed weekly-review automation runs. This helps ensure variety in suggestions and prevents the AI from focusing only on the same initial set of entities.

Domain Filtering

Use the domains parameter in the service call or your automation configuration to narrow the focus. This is very effective for getting suggestions for specific areas (e.g., only analyze light and switch entities in the living_room area - though area filtering is implicit based on the entities selected).

Entity Limit

The entity_limit parameter is crucial for managing prompt size, particularly with models sensitive to input length or cost. Experiment to find a limit that provides good suggestions without hitting token limits or incurring excessive costs.

Custom Prompts

The custom_prompt parameter allows you to be very specific about the type of suggestions you want for a particular run. Combine it with domain filtering for highly targeted results (e.g., domains: ['climate'], custom_prompt: "Suggest automations to optimize heating/cooling based on occupancy and weather.").

When Home Assistant is configured to a supported non-English language, generated suggestion titles, descriptions, and warnings are prompted in that language. YAML, entity IDs, service names, and code identifiers remain unchanged. Use the persistent custom system prompt or custom_prompt if you want to force a different output language for a specific provider or run.

---

Implementing Automations

1. Review Suggestions: Check the persistent notifications or your dashboard card for new suggestions.
2. Copy YAML: The suggestions are provided as ready-to-use Home Assistant YAML snippets. Copy the yaml_block content.
3. Add to Home Assistant:
   • Paste the YAML into your automations.yaml file and restart Home Assistant.
   • Alternatively, use the Home Assistant Automation Editor UI: create a new automation, switch to YAML mode, and paste the snippet.
4. Adapt as Needed: While the suggestions are tailored, you may need to make minor adjustments to triggers, conditions, delays, or actions to perfectly match your preferences and devices.
5. Test: Always test new automations to ensure they function as expected before relying on them.

---

Sensors

The integration provides two key sensors for monitoring:

• AI Automation Suggestions Sensor: sensor.ai_automation_suggestions_<provider_name>
  • State indicates the status (e.g., idle, generating, suggestions_available).
  • Attributes contain the latest suggestions, including description, yaml_block, and potentially other details depending on the AI provider's response format.
• AI Provider Status Sensor: sensor.ai_provider_status_<provider_name>
  • State indicates the last generation outcome (connected or error), or initializing before a provider request completes.
  • Attributes may provide additional details about the provider status or any errors encountered.

Monitor these sensors to ensure the integration is functioning correctly.

---

⚠️ Important Notes

• Privacy Considerations: If using cloud-based AI providers, be aware that entity data (names, states, attributes) is sent to their servers. Consider using local AI models (LocalAI, Ollama) for full data control if privacy is a major concern.
• API Costs: Some cloud providers charge for API usage based on tokens processed. Be mindful of this and use features like entity_limit and scheduled run frequency to manage potential costs. Monitor your provider's billing.
• No Guarantees: The AI's suggestions are based on patterns and logical inference from the data provided. They are not guaranteed to be perfect or the most efficient solution for every scenario. Always review suggestions thoroughly before implementing them in your live system.
• AI Limitations: Large language models can sometimes hallucinate or provide illogical suggestions. Use your judgment and knowledge of your home setup when reviewing.
• Home Assistant dependency safety: This integration uses plain HTTP calls and does not need the Python openai package. Avoid installing or pinning openai in your HA environment, as mismatched SDK versions can break the official OpenAI Conversation integration.

---

🧩 Troubleshooting

Symptom	Check / Action
AI Provider Status stays initializing	Run ai_automation_suggester.generate_suggestions explicitly with all_entities: true, entity_limit: 50, and automation/script YAML reading disabled. Select the affected provider entry when using multiple instances. Inspect the action result, last_error_message, and last_attempted_update. An empty entity selection makes no provider call and can leave the status unchanged.
Missing or truncated YAML with a reasoning model	Increase input/output budgets as described under Token Management and reduce the entity limit. A message or warning mentioning the Max Output Tokens limit means the provider stopped before finishing; thinking and reasoning tokens count toward that limit. Four-space YAML indentation is valid and is preserved. Complete YAML Markdown fences inside structured output are removed without flattening the content. If YAML still fails, enable debug logging (see Error Handling & Troubleshooting) and include the sanitized raw provider response in your issue report.
No suggestions available	- Verify API key is correct.- Check the AI Provider Status sensor for errors.- Check the Home Assistant logs for errors related to the integration.- Try triggering the service manually with a small entity_limit and no domain filters.- Ensure you have enough entities/devices for meaningful suggestions.
AI Provider Status shows error	- Inspect the Home Assistant log (home-assistant.log) for detailed error messages (look for ai_automation_suggester and processing error).- Check your network connection to the provider's server (if cloud-based) or your local server.- Confirm your API key is active and has permissions.- Ensure your local AI server is running and accessible.
Suggestion prompt is too long	- Reduce the entity_limit parameter when triggering the service or configuring the automation.- Use the domains filter to narrow the scope of entities analyzed.- Shorten or simplify your custom_prompt if you are using one.
Unintended startup suggestions	- Review your Home Assistant automations and scripts to ensure none are configured to call ai_automation_suggester.generate_suggestions on startup or via events you didn't intend.

If you encounter issues not covered here, please open an issue on the GitHub repository with details from your Home Assistant logs.

---

Roadmap

Future planned features and improvements:

• More Interactive Suggestions: Explore feedback mechanisms to help the AI learn from user acceptance or rejection of suggestions.
• One-Click Automation Creation: Streamline the process from reviewing a suggestion to creating the automation in Home Assistant.
• Expanded Localization: Support for more languages through community contributions.
• Improved Entity/Device Context: Enhance the information provided to the AI about device types, capabilities, and relationships.

---

License

This project is licensed under the MIT License. See the LICENSE file for details.

---

Acknowledgments

• Home Assistant Community: For providing a robust and extensible smart home platform.
• AI Providers: OpenAI, Anthropic, Google, Groq, LocalAI, Ollama, Mistral, Perplexity, OpenRouter, Requesty, and LiteLLM for developing and providing access to powerful language models.
• Contributors and Users: For valuable feedback, testing, and contributions that help improve this project.

---

Contributions

We welcome contributions! If you have ideas for new features, improvements, bug fixes, or translations, please feel free to open an issue or submit a pull request on the GitHub repository. Please follow standard development practices.

---

Disclaimer

This is a custom component developed independently. It is not affiliated with, endorsed by, or officially supported by Home Assistant, Nabu Casa, or any of the mentioned AI providers. Use at your own discretion.

---

🤝 Support the Project

If you find this integration helpful and it saves you time and effort in automating your home, please consider supporting its development. Your support helps with maintenance, adding new features, and covering any potential costs associated with development and testing.

---

Additional Information

For further questions, discussions, or assistance, please visit the GitHub repository or the Home Assistant Community Forums thread (if one exists). Your feedback is highly valuable and helps shape the future direction of this project.

---

❓ FAQ

1. How do I update the integration? If installed via HACS, update directly through the HACS interface in Home Assistant. If installed manually, download the latest version of the files from the repository and replace the existing ones in your custom_components/ai_automation_suggester folder, then restart Home Assistant.

2. Can I use this integration without a cloud API key? Yes! You can use local AI models like those provided by LocalAI or Ollama running on your local network. This requires setting up and running the local AI server separately.

3. Is my Home Assistant data safe? When using cloud-based AI providers, specific entity data (names, states, attributes) is sent to the provider's API for processing. Refer to the privacy policies of your chosen AI provider. Using local models keeps all data processing within your local network.

4. I found a bug or have a feature request. What should I do? Please open an issue on the GitHub repository. Provide as much detail as possible, including steps to reproduce the bug, screenshots, and relevant logs. For feature requests, clearly describe the desired functionality and use case.

5. Can I get suggestions in languages other than English? The quality of suggestions in other languages depends heavily on the AI model used. The integration structures the prompt in English, but you can experiment with custom prompts in other languages and see how the model responds. Community translations of the integration's UI and documentation are welcome!

---

With the AI Automation Suggester, you gain an AI-powered ally to help you unlock your home’s full potential. Instead of being overwhelmed by possibilities, receive thoughtful, context-aware suggestions that make your Home Assistant automations more impactful, efficient, and enjoyable.