Fixed
-
The integration failed to start on Home Assistant 2026.10.0 with "Setup failed for custom integration 'home_generative_agent': Requirements for home_generative_agent not found: ['langchain-openai==1.0.3']". Home Assistant 2026.10 moved to
openai3.10.0, and the pinnedlangchain-openai1.0.3 only acceptsopenaibelow 3, so the requirements could not be installed. This blocked every install, including Ollama-only ones that never use OpenAI.langchain-openaiis now 1.6.7, which acceptsopenai2.45 and later. Both providers built on it (OpenAI and OpenAI-compatible) stay on the Chat Completions API they used before; langchain-openai 1.6 would otherwise switch some model names to the Responses API on its own. The minimum Home Assistant version is now 2026.8.0. Home Assistant 2026.3 to 2026.7 pinopenai2.21, and nolangchain-openairelease accepts both that and theopenai3 that 2026.10 requires, so HACS no longer offers this update on those versions; they keep 3.43.2 until Home Assistant is updated (#735). -
On Home Assistant 2026.10 the agent could not use any Home Assistant tool: every device command and state lookup failed with "Object of type ToolResult is not JSON serializable", so chat and voice could neither read nor control the home. Home Assistant 2026.10 returns tool results wrapped in a new
ToolResultobject, and also renamed the chat log's tool result field. With schema-first YAML turned on, every turn that used a tool failed after the device had already acted. A critical action confirmed with the PIN (unlocking a lock, disarming an alarm) ran and then replied with an error instead of confirming. Both are fixed, and the integration reads and writes tool results the way each Home Assistant version expects. A PIN-confirmed action that a tool reports as failed is now reported as failed and stays pending so it can be retried, a failed live-context lookup is no longer reported as "no open windows", and tool calls rejected by routing policy show as errors in Show Details (#735).