Symptom
- Home Assistant unreachable (
https://192.168.0.10:8123from Mac times out) ha-mcpshowsServer transport closed unexpectedlyin~/Library/Logs/Claude/mcp-server-ha-mcp.logfpve.netbird.cloudnot pingable from home- MCP health monitor Gotify-alerts
ha-mcpfailure counts
Diagnose from home
# Can the home Proxmox reach the farm Proxmox?
ssh pve 'ping -c 3 -W 2 fpve.netbird.cloud'
# 100% packet loss = NetBird mesh is broken between hpve and fpve
# Is the NetBird mesh API up?
curl -s -o /dev/null -w 'HTTP %{http_code}\n' https://app.netbird.io
# Check NetBird peer status (requires netbird MCP loaded)
# mcp__netbird__list_peers — fpve should appear with status: online
If fpve.netbird.cloud is the only unreachable peer:
- NetBird daemon on fpve is down or disconnected, OR
- Farm’s Starlink/Omada lost internet, OR
- fpve itself is powered off / kernel-panicked
You can’t diagnose from home if the host is unreachable. You need farm-LAN access.
Fix (farm-side)
When physically on the farm or when LAN reachability returns:
# 1. Verify fpve is up
ssh root@192.168.0.191 'uptime; netbird status'
# 2. If NetBird daemon is dead, restart it
ssh root@192.168.0.191 'systemctl restart netbird; netbird status'
# 3. If fpve had a reboot, the IPv6 sysctls aren't persistent — re-apply
ssh root@192.168.0.191 'sysctl -w net.ipv6.conf.vmbr0.accept_ra=2 net.ipv6.conf.vmbr0.autoconf=1 net.ipv6.conf.vmbr0.accept_ra_defrtr=1 net.ipv6.conf.vmbr0.accept_ra_pinfo=1'
# 4. Check HA is up
ssh root@192.168.0.191 'pct exec 100 -- ping -c 2 192.168.0.10'
# HA itself is a separate VM/CT; should respond independently of fpve uptime
Verify from home
# Mesh restored
ssh pve 'ping -c 3 -W 2 fpve.netbird.cloud'
# HA reachable
curl -s -o /dev/null -w 'HTTP %{http_code}\n' --max-time 5 http://192.168.0.10:8123
# Restart Claude Desktop so ha-mcp reconnects
osascript -e 'tell application "Claude" to quit'
sleep 2
open -a Claude
In a new Cowork session, smoke-test ha-mcp: ask it to list HA areas. Should return 13 areas (Barn, Garage, Kitchen, etc.).