Repository navigation
Home Assistant as a first-class integration #175
Description
Home Assistant exposes an official MCP server, and community dynamic discovery claims about 95% token reduction. One test found local-only setups answered 7 of 19 prompts against 11 of 19 with a cloud LLM, so the model should see only the entities it needs.
Idea: A native Home Assistant connection with an entity picker. Known commands take the LOCAL-8 deterministic path, and the model receives only the relevant entities through dynamic discovery, never the full list.
Status in Sentient today: Partial. The MCP client can already connect to Home Assistant's MCP server, but there is no packaged experience.
Where: A plugin in sentient/integrations/plugins/ (or a preset on sentient/integrations/mcp.py), an entity picker in desktop/src/features/integrations/, and the fast path from LOCAL-8.
Done when:
- connecting Home Assistant with a URL and token lists entities to pick
- "turn off the kitchen lights" works without sending all entities to the model
Sources:
- https://www.home-assistant.io/integrations/mcp_server/
- https://community.home-assistant.io/t/mcp-assist-95-token-reduction-for-voice-assistants-with-local-cloud-llms/977977
- https://www.michaelsleen.com/ha-voice-pe/
Roadmap ID: INT-1 · Priority: P1 · Size: M
Activity
feat(integrations): Home Assistant as a first-class integration (exis…
itsskofficial commentedon Oct 16, 2026
Note from #390 / #400: Sentient's own alarms now have
stop_alarmandsnooze_alarmtools. With nothing ringing,stop_alarmanswers "No Sentient alarm is ringing right now.", and the model should then move on to the house alarm. When this issue is built, its real test should include "stop the alarm" with Home Assistant connected and no Sentient alarm ringing: the house alarm must be the one acted on, with approval.feat(quick): stop or snooze a ringing alarm by saying so (#400)