I’ve been hacking on the official homey CLI together with Claude Code for the past few weeks, and the result is a skill I want to share. It runs locally, no cloud involved, and covers a wide chunk of the local API including advanced flows, raw API and HomeyScript.
The feature I use most: ask the agent “suggest some flows based on my devices” and it reads your device inventory, checks what flows you already have, and proposes ideas in a browser picker. You tick what you want, click Submit, and the agent builds the picked flows.
What’s in it
You can read everything: devices, zones, flows, apps, moods (about 50 managers via homey api). Build standard and advanced flows with the full graph editor — trigger / condition / action / start / delay / all / any / note cards. Set capability values, trigger flows, rename and move devices. Raw API for whatever the managers don’t expose directly. HomeyScript when a flow genuinely can’t do the job. Token-mode if you want to bypass the cloud entirely.
The bit I’m most glad I added: a 10-point validation that runs before every flow push. It catches the broken: false trap (Homey marks flows with dead device refs as healthy, which is exactly as annoying as it sounds).
Install
mkdir -p ~/.claude/skills
git clone https://github.com/timvdhoorn/homey-cli-skill.git ~/.claude/skills/homey-cli
And the homey CLI itself:
npm install -g homey
homey login
homey select --id <your-homey-id>
Restart Claude Code, that’s it.
How I use it day to day
Usually I open with “what else could I automate with these devices?”. The agent pulls inventory, compares against existing flows, suggests. Some are obvious (evening dim ramp), some I wouldn’t have come up with myself (Sonos auto-pause on Ring doorbell with a TV-room chime).
For specific flows it works the same way: “build a flow that turns the driveway lights on when the Ring doorbell triggers after 22:00”. The agent finds the right card IDs, builds the JSON, validates, pushes. No manual flow-card hunting.
Repo + feedback
I’m actively maintaining this and would love to hear from you. Suggestions, feature requests and bug reports are all welcome. Open an issue on the repo, drop a reply in this thread, or PR directly. Particularly keen on hearing about flow patterns the suggestion engine should know about but doesn’t yet — the current starter set only covers what I happen to own.
