FLODE — Visual Flow + Node Editor for Home Assistant (Fork of C.A.F.E., Testers Wanted!)

Hi everyone,

today I'd like to introduce FLODE — a visual flow editor for Home Assistant automations, similar to Node-RED, but without an external server and with 100% native HA YAML as output.

GitHub: GitHub - SH1FT-W/flode: Visueller Flow-Editor für Home Assistant · GitHub


First things first: This is a fork — full transparency

FLODE is not a completely original project, but a fork of C.A.F.E. by @FezVrasta. I loved the core idea of the original: draw your automations visually as a diagram, while the result is still plain Home Assistant YAML — no vendor lock-in, no additional service, and everything remains editable in the built-in HA editor.

In practice, however, I ran into a number of bugs that bothered me in daily use (import crashes, broken rendering of choose: blocks, missing translations, etc.). Instead of just filing issues, I started fixing things myself — and that's how FLODE came to be.

Being honest here too: I develop this project in my spare time and actively use Claude (Anthropic) as a coding assistant. This is also stated in the README. However, every change is tested by me and properly documented in the CHANGELOG.


What is FLODE?

FLODE stands for Flow + Node Editor. The core idea:

  • Visual flow editor — connect triggers, conditions, and actions via drag-and-drop on a canvas
  • 100% native YAML — FLODE translates the flow into standard HA automation YAML, stored directly in HA core. No proprietary format!
  • Bidirectional — import existing automations, edit them visually, and save them back
  • Trace integration — debugging via the official HA trace view
  • State machine support — complex loops and branches are mapped automatically
  • German & English — full translation of the entire UI
  • Dark & light mode — automatically follows your HA theme

Node types: trigger (yellow), condition (blue), action (green), OR/AND/NOT groups (purple).

(You can find screenshots in the README on GitHub — light and dark mode side by side.)


What has changed compared to the original?

Since the fork (baseline 0.6.0), more than a dozen releases have accumulated. A selection of the most important fixes and improvements:

Bug fixes:

  • Fixed import crash with non-standard trigger formats ("Graph must have at least one trigger node")
  • Fixed crash with time conditions (after/before)
  • The variables: section was being overwritten during the save/import cycle — fixed
  • stop: actions were displayed as "Unknown node" — they are now parsed and exported correctly
  • choose: blocks are now visualized correctly: cases attach to a shared entry point, triggers are matched to their corresponding trigger-ID condition, no more crossed lines
  • Device triggers showed UUIDs instead of device names — fixed
  • Various UI fixes (save dialog on small screens, cursor in light mode, etc.)

Improvements:

  • Complete German translation of the entire UI, including all validation errors
  • Service dropdown shows friendly names ("Turn on" instead of light.turn_on), search works for both
  • Automatic layout (ELK) significantly improved — clean column layout for triggers | conditions | actions
  • Connections rendered as smooth Bezier curves, loops recognizable by a dashed back-arrow
  • HACS validation runs automatically on every push/PR

The full list is in the CHANGELOG.


Installation

Via HACS (recommended)

  1. Open HACS → Integrations → ⋮ → Custom repositories
  2. Enter the URL https://github.com/SH1FT-W/flode, select type Integration → Add
  3. Search for FLODE → Install
  4. Restart Home Assistant
  5. Settings → Devices & Services → Add Integration → FLODE

The README also includes a My Home Assistant button for one-click installation.

Manual

Download flode.zip from the releases page, copy the flode/ folder to config/custom_components/flode/, restart HA, and add the integration.

FLODE will then appear in the HA sidebar.


:warning: Beta notice

FLODE is currently in beta. The editor is designed not to overwrite any existing data — nevertheless, I strongly recommend backing up your automations (or your entire config) before editing. Better safe than sorry.


Why I'm posting here: Testers wanted! :folded_hands:

I'm actively developing FLODE in my spare time and testing as much as I can — but every HA installation is different, and especially with YAML import there are countless edge cases that I could never cover on my own.

So here's my request:

  • Try out FLODE and import your existing automations — does the round trip (import → edit → save) work cleanly?
  • Please report bugs as a GitHub issue — ideally with the YAML of the affected automation (with any sensitive data removed first, of course)
  • Feedback on the UI, translations, and missing features is just as welcome
  • Pull requests, naturally :wink:

I appreciate any feedback — whether it's praise, criticism, or a bug report. The more people testing, the faster this thing gets really polished.

Thanks for reading — and a big thank you to @FezVrasta for the fantastic original project, without which FLODE wouldn't exist!

License: Apache 2.0 Repo: GitHub - SH1FT-W/flode: Visueller Flow-Editor für Home Assistant · GitHub

Hi there,

While it's a nice fork, please notice that this forum is English only (see this: How to help us help you - or How to ask a good question)

Hi,

thanks for the hint!
The post and title have been updated, everything is in English now.

Update!!! FLODE is now at v1.3.0 :tada:

Thanks to everyone who tried it out since the original post! A lot has happened since v0.8.0
here's the highlight reel:

Native Home Assistant UI (v1.2.0)
FLODE now uses HA's own UI components throughout, native entity/device/area/service pickers, ha-select/ha-switch/selectors, and full theming via HA's CSS variables. It's mounted as a real panel via Shadow DOM (no more iframe), so it feels like part of Home Assistant rather than a separate app bolted on.

Full targeting support (v1.3.0)
Actions can now target areas, devices, labels, and floors directly in the editor, not just entities.

Save dialog metadata (v1.3.0)
Assign icon, category, labels, and area to your automation right from the FLODE save dialog, same as the native editor.

Trace overlay on the canvas (v1.3.0)
Run an automation and see the execution path highlighted directly on your flow, executed/error/skipped states per node.

Deep links (v1.3.0)
Open a specific automation directly via URL (?automation=<entity_id>) or jump straight into a new automation (?new=1), handy for dashboard buttons.

Diagnostics, Repairs & language option (v1.3.0)
Standard HA diagnostics download, import warnings now surface as proper Repair issues instead of vanishing toasts, and a new option to force English/German regardless of your HA language.

Also since the original post: OR/AND condition visualization, choose-block improvements, templated delay support, a big dependency/security overhaul, and general hardening.

Full changelog: [link zu CHANGELOG.md]
Latest release: Release v1.3.0 · SH1FT-W/flode · GitHub

Still looking for testers and feedback, especially on the native UI migration and the new targeting options!

Hi. New to both Home Assistant as well as FLODE, but have been using Hubitat for the past 5+ years.

FLODE looks like a real cool addon to Home Assistant and am looking forward to explore its capabilities.

I’ve installed FLODE and am running into an issue when I try to open an existing automation. I have two automations and they are both located in the “Garage” area and, when I attempt to open with FLODE, I’m getting a yellow bar with the word “Garage” in white and I’m unable to do anything at this point - please see attached.

Any thoughts as to what’s happening?

Thanks and I appreciate the hard work!

Hello,
Thank you very much for your feedback. That’s a “bug”; I’ll fix it as soon as possible.