v0.13.2 — Live Home Assistant Connectivity

Live Home Assistant connectivity restored

This patch fixes the reported guarded-tool result:

Cannot send message (get_states): Home Assistant not connected

Root causes fixed

• Updated the Home Assistant client for websockets 16.1: Supervisor upgrade headers now use additional_headers instead of removed extra_headers.
• Disabled environment proxy auto-discovery for local Home Assistant and Supervisor WebSockets.
• Separated direct LLAT authentication from Supervisor-proxy authentication so credentials are never mixed.
• Added optional ha_url; direct mode defaults to http://homeassistant:8123 inside the add-on.
• Closed the command-response race by registering pending futures before sending.
• Pending calls now fail immediately and diagnostically when a connection drops.

Ollama tool continuation fixed

Live logs also exposed an Ollama 0.6 Pydantic validation failure after the first tool call. Provider-neutral history is now converted to Ollama's native schema: tool arguments are dictionaries and tool results use tool_name.

Diagnostics

• /api/health now reports HA connection mode, endpoint, HA version, attempts, timestamps, and last error without credentials.
• /api/health/home-assistant runs a real read-only state probe and returns only entity/domain counts and latency.
• Portal status now reflects actual HA connectivity, not only the dashboard WebSocket.

Live and automated verification

• 192.168.68.57:8123 reachable; WebSocket reports Home Assistant 2026.7.2.
• Authenticated MCP reads returned calendars, panels, and a full health audit.
• Patched client reached the live HA auth exchange without legacy-header/proxy failures.
• 281 backend tests passed; 4 optional live-MCP tests skipped.
• React/Vite production build passed; npm audit found 0 vulnerabilities.