Skip to content

Account and Service Setup

barneyonline edited this page May 10, 2026 · 5 revisions
Account and Service Setup banner

Use this page to understand Groq account entries, service subentries, model discovery, and reauthentication.

Contents

Account entry

Add a Groq account from Settings -> Devices and services -> Add integration -> Groq.

The setup flow asks for:

  • Name: a friendly label for the Groq account, API key, or billing project.
  • Groq API key: the key used by services created under this account.

The API key is stored by Home Assistant and redacted from diagnostics.

Step Screenshot
Add the Groq integration. Add integration dialog showing Groq
Enter the account name and Groq API key. Groq account setup form

Multiple accounts

Add another Groq account when you want to separate:

  • API keys
  • Groq projects
  • billing or rate-limit pools
  • production and testing services

Services use the API key from their parent Groq account.

Service entries

After adding an account, open the Groq integration page and choose one of the service-specific buttons:

  • Add Text Generation
  • Add Speech-to-Text
  • Add Text-to-Speech
  • Add Image Recognition

Each service has a friendly name. Home Assistant uses that name for generated entities and for selecting defaults when service calls do not explicitly name a Groq account or service.

Service type Home Assistant surface Main guide
Text Generation Conversation entity, AI Task entity, groq.generate_text, groq.generate_structured Text Generation
Speech-to-Text STT entity for voice pipelines, groq.transcribe_audio Speech-to-Text
Text-to-Speech TTS entity for tts.speak Text-to-Speech
Image Recognition groq.analyze_image, groq.extract_text_from_image Image Recognition
Step Screenshot
Open the Groq integration page. Groq integration entry
Choose a service-specific add button. Groq service subentry buttons
Complete the service setup form. Text Generation service setup form

Model discovery

During service setup, the integration asks Groq for active models available to the selected API key and filters them by service type.

Built-in model lists are used as a fallback when discovery is unavailable. Because Groq model availability can change, the list shown in your setup flow may differ from the built-in fallback list.

Use groq.list_models from Developer Tools -> Actions when you need to inspect model data for a configured account.

List models action

Reauthentication

If Groq reports that credentials are invalid, Home Assistant starts a reauthentication flow. Enter a new API key to keep existing services attached to the same account entry.

Groq reauthentication flow

Related pages

Clone this wiki locally