Hi everyone! I’d like to share DRADIS, a Home Assistant app - human architected, AI implemented.
DRADIS lets you talk to an AI agent directly from Telegram — ask questions, search the web, check weather, manage your
Google Calendar and Gmail, or set up scheduled automations that deliver summaries every morning.
Key features:
Multi-provider LLM support (OpenRouter, OpenAI, Gemini, Groq, GitHub Models)
Web search sub-agent (Tavily), Weather (Open-Meteo, no API key needed)
Google Calendar & Gmail integration via OAuth2
Voice message transcription (Groq Whisper)
Cron-based scheduled tasks delivered to Telegram
Fallback model per agent — auto-retry on API errors
Token usage tracking per agent
Full configuration from the built-in Web UI — no restart required
The Add-on term has been replaced some months ago. All your documentation points the add-ons which will confuse users trying to load this and cause you many headaches.
Perhaps you or whatever you collaborated with is working off of out dated information.
For the sake of the user base and anyone that wants to try your software, perhaps a revision is in order.
Welcome aboard — DRADIS as a Telegram-native HA agent fills a real gap. The multi-provider angle (OpenRouter / OpenAI / Gemini / Groq / GitHub Models) is the part I’d love to ask about: how are you handling provider rotation when one rate-limits or hits a regional outage? Asking because that’s the exact piece we’re solving on the connectivity side.
One small consideration if you’re planning to ship beyond your own setup: openai_api_key, gemini_api_key, groq_api_key, etc. all sitting in the add-on config means each new user has to wire up 5+ provider accounts before they can try it. That tends to be the biggest install dropoff in multi-LLM tools.
We’ve been building an open-source Agent Connectivity Gateway called NyxID (github.com/ChronoAIProject/NyxID) that does provider credential injection + per-agent scoping at the proxy layer. So instead of DRADIS asking the user for 5 API keys, it could ask for one NyxID URL, and the gateway routes calls + injects per-provider creds + handles rotation. Open-source, self-hostable, no vendor lock-in — same values as the HA ecosystem.
Architecture-wise it sits between DRADIS and the LLM providers, not between you and HA. So your add-on stays unchanged, the friction just moves out of the user’s setup checklist.
Happy to compare notes if you’re considering scaling DRADIS past single-user deployments.