extended_openai_conversation

Report Abuse

Basic Information

Extended OpenAI Conversation is a custom Home Assistant component that extends the built in OpenAI Conversation integration so OpenAI models can perform real Home Assistant actions. It maps OpenAI function calling to Home Assistant service calls and enables the model to execute services, create automations, retrieve entity state history, fetch data from REST APIs or web pages, and optionally receive the active user name as part of the message context. The integration is installed as a custom component via HACS or by copying a folder into custom_components, configured from Settings Devices and Services, and selected as the conversation agent under Voice Assistants. It requires an OpenAI API key and supports specifying a base URL for compatible servers. Users must expose entities in Home Assistant so the model knows available devices.

Links

Categorization

App Details

Features
Supports multiple function types including native functions to execute services, add automation and get history, as well as script, template, rest, scrape, composite, and sqlite function types. Uses OpenAI function calling to let models request actions which the component translates to hass service calls. Configuration options include passing the active user name, limiting maximum function calls per conversation, and defining a list of function specs mapped to executable functions. Provides examples and templates for common tasks such as playing media on TV, adding shopping list items, sending notifications, searching music, scraping a website for version info, querying REST endpoints, and querying Home Assistant SQLite history with optional validation.
Use Cases
It lets voice and chat assistants in Home Assistant perform real world tasks by turning model outputs into service calls and automations, reducing manual setup for routine operations. Users can ask or speak natural language and have the assistant control devices, play media, add automations, fetch calendar events, or retrieve historical state data without writing custom code. The component also supports combining steps into composite workflows, obtaining external data via REST or scraping, and running verified database queries for historical answers. Logging options help monitor API requests and responses. The provided examples and function specs make it easier to configure practical automations for end users and integrators.

Please fill the required fields*