v1.5.0

New features

• The node property panel's ID field now works correctly for triggers, so {{ trigger.id }} templating and choose:/condition: trigger routing can be set up entirely from the canvas.
• FLODE now warns (inline in the property panel and with a badge on the canvas node) if two triggers in the same automation end up with the same ID, since that would make routing ambiguous or fail to load in Home Assistant.

Bug fixes

• Fixed the ID field silently producing an invalid save ("extra keys not allowed") when set on action, delay, wait, or set_variables nodes — Home Assistant's schemas only support a per-step id: on triggers, so the field is now scoped to trigger nodes only.