Skip to content
Open
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
85ca391
Add LiteLLM integration documentation
luismalves Jun 3, 2026
d68944d
Clarify LiteLLM prerequisites and retrigger build
luismalves Jun 3, 2026
32da794
Quote configuration_basic descriptions to fix Netlify build
luismalves Jun 3, 2026
6d08c9a
Minimize litellm page to bisect Netlify failure
luismalves Jun 3, 2026
a4f48a1
Bisect: full body without configuration_basic block
luismalves Jun 3, 2026
abffd4c
Bisect: config_basic with simple descriptions
luismalves Jun 3, 2026
d8be2cf
Bisect: full descriptions but URL without scheme/port
luismalves Jun 3, 2026
f7a68d5
Fix Netlify build: avoid literal http:// URL in configuration descrip…
luismalves Jun 3, 2026
9bdd9af
Clarify prerequisites wording (address review feedback)
luismalves Jun 3, 2026
f1452ca
Merge branch 'next' into litellm-docs
c0ffeeca7 Jun 4, 2026
d5d144f
Merge branch 'next' into litellm-docs
luismalves Jun 4, 2026
2f8f22e
Docs: AI-only category and link expose-entities guide
luismalves Jun 4, 2026
7d7b955
Clarify that LiteLLM proxy can be hosted or self-hosted
luismalves Jun 4, 2026
a6227d5
Set IoT class to Cloud Polling
luismalves Jun 4, 2026
bd77120
Update source/_integrations/litellm.markdown
luismalves Jun 5, 2026
02f7cf2
Clarify what each LiteLLM prerequisite is for
luismalves Jun 5, 2026
3647337
Clarify what each LiteLLM prerequisite is for
luismalves Jun 5, 2026
df31bfe
Update source/_integrations/litellm.markdown
luismalves Jun 5, 2026
4c0b458
Update source/_integrations/litellm.markdown
luismalves Jun 5, 2026
b8750e7
Fold conversation agent setup into the configuration section
luismalves Jun 6, 2026
c62433f
Restore "Adding a conversation agent" heading within setup section
luismalves Jun 6, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 46 additions & 0 deletions source/_integrations/litellm.markdown
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
title: LiteLLM
description: Instructions on how to integrate LiteLLM as a conversation agent
ha_category:
- AI
- Voice
ha_release: 2026.7
ha_iot_class: Local Polling
ha_config_flow: true
ha_codeowners:
- '@luismalves'
ha_domain: litellm
ha_integration_type: service
ha_platforms:
- conversation
ha_quality_scale: bronze
---

The [LiteLLM](https://www.litellm.ai/) {% term integration %} allows you to use a self-hosted LiteLLM proxy as a conversation agent in Home Assistant.

LiteLLM exposes an OpenAI-compatible API in front of a wide range of model providers. Because the proxy is self-hosted, this integration lets you point Home Assistant at your own endpoint instead of a hosted service.

{% include integrations/config_flow.md %}

{% configuration_basic %}
URL:
description: The base URL of your LiteLLM proxy, including the host and port (for example `http://homeassistant.local:4000`). The integration automatically appends the OpenAI `/v1` path if it is missing.
Comment thread
luismalves marked this conversation as resolved.
Outdated
API key:
description: An optional LiteLLM API key or virtual key. Leave it empty if your proxy does not require authentication.
{% endconfiguration_basic %}

## Prerequisites
Comment thread
luismalves marked this conversation as resolved.
Outdated

You need a running [LiteLLM proxy](https://docs.litellm.ai/docs/simple_proxy) that is reachable from your Home Assistant instance, with at least one model configured. The proxy exposes the available models through its `/model/info` (or `/models`) endpoint, which the integration uses to populate the model selection.
Comment thread
luismalves marked this conversation as resolved.
Outdated

## Supported functionality

### Conversation agent

The integration adds a conversation agent for each configured model that can be used in [Assist](/voice_control/). When you grant it control of Home Assistant, the agent can call the configured tools to interact with your devices and entities.

## Removing the integration

This integration follows standard integration removal, no extra steps are required.
Comment thread
luismalves marked this conversation as resolved.

{% include integrations/remove_device_service.md %}