Skip to content
SH1FT-WPublic

About

See your Home Assistant automations and scripts as a flow — edited with Home Assistant's own editors, real runs on the canvas, optional AI help. Saved as plain Home Assistant YAML.

Topics

Resources

Contributing

Stars

43 stars

Watchers

0 watching

Forks

Latest commit

 

History

532 Commits

Folders and files

Repository files navigation

FLODE: See your automations. The editor inside Home Assistant with a flow of two triggers, a condition and actions.

FLODE shows Home Assistant automations and scripts as a flow you can read, test and understand.
Edited with Home Assistant's own editors, saved as plain Home Assistant YAML. No server, no lock-in.

Version Home Assistant HACS License

Website  ·  New  ·  How it works  ·  Runs  ·  AI  ·  Features  ·  Install  ·  Internals  ·  Changelog


JUST ARRIVED

Branches on the canvas. Flows top to bottom.

The last releases opened up the blocks: Choose and If-then show their branches as cards, flows can run top to bottom, and touch screens got menus of their own.

Top to bottom (3.4.0): every flow runs left to right or top to bottom, the direction is saved with the flow. Branches as cards (3.2.0): Choose and If-then draw each branch as cards, nested as deep as you like, in YAML it stays a plain choose or if. Run this card (26.10.15): runs one step for real in Home Assistant, without everything after it, inside branches too. Made for fingers (26.10.11): press and hold opens a card's menu on touch screens, on the iPhone too.

Also new: a "+" on an output that already leads on asks whether the step goes in between or in parallel, dragging a connection onto a free card pulls it into the branch, a toolbar toggle shows card text in Home Assistant's own wording, and when Home Assistant refuses to save, FLODE marks the card red and takes you there. Every change, release by release, in the changelog.


MADE OF HOME ASSISTANT

Nothing new to learn. It's the editor you already know.

Every trigger, condition and action opens in Home Assistant's own editor, with the same forms, pickers and dialogs as in Settings. FLODE adds the canvas, so you see how it all connects. Repeat and Parallel stay single blocks; Choose and If-then show their branches as cards.

Home Assistant's editors: every step opens in Home Assistant's own editor, with the same forms, pickers and dialogs as in Settings. Your icons, language, theme: cards show the entity's own icon with its live state, light or dark, on desktop, tablet and phone. Plain YAML, both ways: open any automation, change it visually, save it back, it stays editable in Home Assistant's own editor. Home Assistant's table: the start page is the same table as under Settings, with filters, grouping, labels and bulk actions.
What a flow looks like in YAML

FLODE saves exactly what Home Assistant's own editor would save. Uninstall FLODE and every automation keeps working. A step that calls an action or entity Home Assistant does not have turns red on the canvas.

alias: Evening light
triggers:
  - trigger: sun
    event: sunset
    offset: "-00:15:00"
conditions:
  - condition: state
    entity_id: input_boolean.evening_mode
    state: "on"
actions:
  - action: light.turn_on
    target:
      entity_id: light.bedroom
    data:
      brightness_pct: 40
  - if:
      - condition: state
        entity_id: switch.string_lights
        state: "off"
    then:
      - action: switch.turn_on
        target:
          entity_id: switch.string_lights
mode: restart

RUNS AND RELATIONS

Know what happened. And why.

Runs. Home Assistant's trace timeline next to the canvas, the path drawn on the cards, the branch that ran marked, and Run from here for any step, with the data of the last trigger. Relations. Conflicting automations, self-triggering ones, chains, missing entities, and where is this used? for any entity.

A real run: Home Assistant's trace timeline and the steps that ran highlighted on the canvas. Conflicts, self-triggering automations, chains and what controls a light.


AI HELP

Stuck? Ask.

If you have set up an AI in Home Assistant (Anthropic, OpenAI, Google Gemini, Ollama and others) and chosen it as the default for AI tasks, FLODE can use it. It uses Home Assistant's own ai_task, no extra key, no extra service. Without an AI task these buttons simply do not appear; everything else works the same.

Explain a run. Why an automation did or did not do its job, in plain words. Assistant. Ask about the open flow, find mistakes, get a better version (shown first, one step to undo). Create with AI. Describe what should happen, get a draft built from your real entities.

The AI explains a failed run in plain words. A draft automation built by the AI, not yet saved.


EVERYTHING ELSE

Small things that add up.

Scripts, too: with fields, a run button that asks for them, and Run from here for any step. Template workshop (⌘J): Jinja rendered live by Home Assistant, with the result type and the variables of a real run. Commands and shortcuts (⌘K): everything in one search, right-click menus, copy, paste, duplicate, and an overview on ?. Tabs and minimap: several flows open at once, each with its own undo, a minimap for big ones, tidy up in one click. Import, export, merge: paste YAML, save as copy, FLODE files, and merge several automations into one. Careful with your data: warns when it cannot read part of an automation, keeps unknown fields as written, opens blueprints read-only. Readable zoomed out: below 60 percent the cards show icon, title and one line in large type, below 35 percent just the icon. On the go: on a phone the tools move into a swipeable strip and the editor slides up as a sheet.
More screenshots

Start screen with Home Assistant's own table of automations and scripts. The AI assistant lists problems in the open flow. Describe an automation in a sentence and get a draft. The template workshop renders Jinja live. The command palette. The right-click menu on a card. FLODE on a phone: the editor as a sheet.


INSTALL

Three steps. Then it's in your sidebar.

Open in HACS

  1. HACS → search for FLODE → Download.
  2. Restart Home Assistant.
  3. Settings → Devices & services → Add integration → FLODE. It appears in the sidebar (admins only).

Requires Home Assistant 2026.3 or newer. To install by hand, unzip flode.zip from the latest release into config/custom_components/flode/.

Versions and coming from 2.x

Since October 2026 FLODE uses calendar versions YY.M.N: year, month, and the number of the release within that month. 26.10.15 is the 15th release of October 2026. Every release, feature or fix, gets the next number. Tags, release titles and the version badge are just the number, without a leading "v". Calendar versions count as newer than every 3.x version, so updates through HACS work as before.

Coming from FLODE 2.x? Your automations open and save as before. FLODE 3 replaced the old editor: the simulation gave way to real runs and Run from here, and FLODE follows Home Assistant's language and theme instead of its own settings. Details in the changelog.


CREDITS

Built on C.A.F.E.

FLODE is a fork of C.A.F.E. by Federico Zivolo. It never overwrites anything it was not asked to save. Back up your automations before big edits anyway.

How FLODE reads, draws, edits, writes and runs automations is described in docs/architecture.md. FLODE is an independent project and is not affiliated with Home Assistant or Nabu Casa. Licensed under Apache 2.0.


A SH1FT-W project  ·  Casora  ·  Pulse  ·  Evenlight  ·  AgentBar  ·  ShareMount  ·  Built with Claude

About

See your Home Assistant automations and scripts as a flow — edited with Home Assistant's own editors, real runs on the canvas, optional AI help. Saved as plain Home Assistant YAML.

Topics

Resources

Contributing

Stars

43 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages