---
name: jarvis-ha-integration
description: "JARVIS ↔ Home Assistant two-way integration — status, what's installed, how it works"
metadata: 
  node_type: memory
  type: project
  originSessionId: d9685e6b-8f79-4948-82e5-fbae607f7aa0
---

HA is accessible at https://hoa.orbishosting.com (via NPM) or http://10.48.200.97:8123 (LAN direct).
HA login: myronblair@outlook.com / Joker1974!!!
After 2026-06-22 Proxmox restore: HA is now VM 109 (was VM 101). QEMU guest agent not installed.
HA token (Jarvis2): eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiIzNmI0N2I1Njk5ZGQ0MTQ2ODMwZWFmYjZiYTQ1MjJkMSIsImlhdCI6MTc4MDIwMzU5NCwiZXhwIjoyMDk1NTYzNTk0fQ.sYRok-jRDlA4lFgWxLQELcEjkJNGQdprk6ZziLwLtXE

## Custom Component (installed 2026-05-31)
Repo: myronblair/jarvis → ha_integration/custom_components/jarvis_agent/
Installed at: /config/custom_components/jarvis_agent/ on HA VM (10.48.200.97)
Config added to /config/configuration.yaml (jarvis_agent: block at end)

**Why:** Replaces PHP→DDNS→HA REST API with HA-initiated outbound polling — more reliable.

## How it works
- HA pushes all entity state changes to JARVIS /api/agent/ha_state (debounced 2s)
- HA polls /api/agent/heartbeat every 10s for queued commands
- JARVIS admin panel toggle → queues command in agent_commands table → HA executes natively
- 212 entities live in ha_entities DB table, updated in real-time
- Agent registered as ID 15, hostname "homeassistant", IP 172.30.32.1 (Docker network)

## JARVIS Admin Panel HOME tab
- 4-column table: domain icon | device name | state | toggle/run button
- Unavailable entities filtered out automatically (reappear on next cache refresh)
- Scenes get ▶ RUN button; switches/lights get toggle slider
- Cache refreshed every 5 min by stats_cache.php cron

## Webhook fix (2026-05-31)
webhook.php had wrong require path (../../ instead of /../) causing 500 since May 25.
Fixed and committed. Auto-deploy pipeline working again.

## HA VM SSH
- Port 22 on orbisne.fortiddns.com forwards to HA Ubuntu VM (not PVE1)
- Password auth failing — likely key-only or fail2ban
- Use HA web terminal (Settings → Add-ons → Advanced SSH & Web Terminal) for shell access
- QEMU guest agent NOT installed in VM 101 (qm guest exec doesn't work)

**How to apply:** When working on HA component or HA VM files, use HA web terminal or HA File Editor addon. Cannot SSH directly.