Having an LLM helping inside HA was okayisch but felt not too well integrated and a little scary. So I wrote a CLI (command line interface) that talks to HA from outside.
It's fine to use by hand. But the point is you can hand it to an LLM — local via Ollama, or Claude Code / whatever — and ask in plain language:
$ "balcony watering didn't run yesterday — why?"
● health → RUNNING, 12 errors
● auto show balcony_minimum_watering → last ran May 22, stopped on a condition
● trace show → condition failed: soil moisture sensor = unknown
Sensor offline since May 22, condition can't evaluate. Probably a dead battery.
The whole thing is built so the agent doesn't drown in context — responses are capped and report their own token count. Writes are staged and need an explicit confirm, and config is validated against HA's real Jinja engine before anything is applied.
It supports caching of local data, and I use it as my daily driver to improve my HA instances — it's been really helpful to discover some nasty template bugs.
There are prebuilt binaries for Linux/macOS/Windows and a small companion add-on for the stuff the API won't expose. Everything's on GitHub:
Install it from HA → Settings → Add-ons, then run hactl setup or hactl health — the companion URL is discovered automatically by enumerating add-ons through the Supervisor WS proxy (supervisor/api).
sorry, if this might not work for you. I just followed the link and installed the companion. You need to add the repo before installing. Or did I miss something in the readme?
I still love it and use it every day. In this case my hermes agent is nannying my instance fully locally (MacM3Ultra running qwen)! Babysitting your and your friends Home Assistant has never been easier. And it is able to find lots of issues which are hard to find in UI.
If you are not a solution institution: give it a try!
HA instance analysis completed
Current status
Item Value
HA Version 2026.6.4
State RUNNING ✓
Errors 35 (no active repairs)
Companion 2026.6.7 ✓
hactl v2026.6.0 ✓
Found issues
Logs last 24h:
⚠️ Template error: Coffee machine missing JSON keys: mix_temperature, steam_state, etc.
⚠️ sensor.gunstigste_stunde_heute: Error with empty Tibber list
⚠️ ESPHome connections: Reconnect problems with officev2
⚠️ better_thermostat Kitchen: Degraded mode, temperature sensor problem
⚠️ Missing entities: References to number.esphome_show_p
