-
Notifications
You must be signed in to change notification settings - Fork 36
Description
Home Assistant 2025.7 version implemented "sub-entries" support so users do not need to enter their API keys and cloud accounts to multiple integrations, so wondering if this custom component use such "sub-entries" for the integrations that now support sub-entries?
It allows users to configure their Ollama server or API key for OpenAI once, and create many different agents using different models or configuration underneath.
The architecture discussion gives more background why this make usage the same API keys and cloud accounts much more user-friendly:
This makes it easier for integration authors to allow users to add, modify and remove pieces of configuration which share some common resource, for example a cloud account or an MQTT broker.
Integration sub-entries
Ever wondered why you had to enter your API keys for every AI agent you created, even though they all used the same key? Or why you had to authenticate for every calendar you added, regardless of the fact that they all shared the same account? Or why you couldn’t add MQTT devices from the UI?
This release solves that with the introduction of integration sub-entries. This allows you to add a sub-entry to an existing integration entry. In practice, this means that your integration entry has your credentials, and all the sub-entries use these credentials. In the sub-entry, you can then configure what should be done with these credentials, such as fetching a specific calendar, adding three AI agents with different prompts using the same OpenAI account, or in the case of MQTT, configuring devices that are connected to your MQTT broker.
Screenshot showing how you can now add MQTT devices directly through the user interface.
The following integrations now support sub-entries as of this release: Anthropic, Google Generative AI, MQTT, Ollama, OpenAI Conversation, and Telegram Bot.
Integration page gets an overhaul
The integration page got a big overhaul! It now has support for sub-entries, allowing you to easily add a sub-entry to an integration entry along with being able to see which devices and services belong to which sub-entry.
But we took the opportunity to do more. Instead of just showing your integration entries, it now also shows the devices and services provided by that configuration entry. This makes it much easier to manage your devices and see the relationship between your devices and their integrations at a glance.
