Repository navigation
v1.5.3
Mid-flow parallel fan-out, now with a working reimport
Fixes #16: a node with multiple outgoing edges (e.g. scene.create linking to several light.turn_on actions) previously kept only the first edge and silently dropped the rest — both when generating the automation's YAML and, in a follow-up round found during testing, when reimporting that very YAML back into FLODE.
This release promotes the v1.5.3-beta.1 through beta.3 line to stable:
Generation (beta.1 + beta.2)
- A node's multiple outgoing edges now fan out into a
parallel:block instead of silently keeping only the first one. - Before inlining a branch, FLODE checks whether that's actually safe — a branch looping back to the fan-out source, branches re-joining at a shared node, or a nested condition whose handle itself fans out to several nodes. When it's not safe, it falls back to the previous sequential behavior plus a warning instead of producing broken YAML (ported from upstream C.A.F.E.'s
planExclusiveFanOut()guard, FezVrasta/cafe-hass#240). - Fanned-out branches can continue past their first node — conditions, delays, waits, set_variables, and nested fan-out all work inside a branch now. The same fix covers trigger fan-out and condition-handle fan-out.
Reimport (beta.3)
- Reimporting a flow with a mid-flow
parallel:fan-out now reconstructs every branch as real canvas nodes and edges, instead of the branches vanishing entirely. - AND/OR condition nodes survive reimport intact instead of collapsing into a generic template condition — compound
and/or/notJinja expressions are now parsed recursively. - A
set_variablesnode reimports correctly instead of silently becoming an empty, disconnected action node.
Testing
Verified against automated tests (330/330 passing) and end-to-end against real Home Assistant automations built from the issue reporter's own entities, structurally matching the originally reported flow — 8 triggers, a 4-way scene.create fan-out, a 3-way trigger convergence through a nested AND into a shared join node, and a downstream OR. Reimported correctly in the FLODE UI with no dropped branches and no collapsed conditions.
Thanks to @NullScope for the detailed reports and for re-testing along the way.