First working version of Visual Blueprint Editor

[EpicLPer]

Heya,

I've spent an hour or two with Cursor and created the following visual Blueprint editor. I'm not sure however if it's okay to submit entirely AI generated code to this repo, so I'll show it first before submitting it :)

A disclaimer here: I'm not a good programmer myself, so this might be buggy. I'll test it to my best abilities and also try to catch edge-cases as good as I can, however this might not be a fully complete thing. I'm also not entirely sure if I can keep it up-to-date or maintain it properly for the time being due to this.

What this features so far:

• Create new Blueprints directly within the Switch Manager interface
• Image upload
• Live preview of all placed buttons
• Drag and Drop editor including positions and sizes
• Custom SVG code capabilities for weird button shapes via a fully free-text field, also with live preview
• Undo/Redo functions
• Warning upon leaving page with unsaved changes
• Full implementation of actions and conditions
• Probably some more small things I forgot to mention

If you're interested I can create a pull request with what I've got so far!

[macpit]

Hey @EpicLPer — this is a really cool idea, thank you for taking the initiative! 🙌 Writing blueprints by hand today means hand-editing YAML with pixel coordinates (x/y/width/height), so a visual editor with live preview would genuinely lower the barrier for contributors and cut down on mistakes. I'd love to see it.

No worries at all about it being AI-assisted — that's totally fine here. A couple of honest, friendly notes so we set expectations up front:

Please open it as a Draft PR. That way we can look at the actual code together and iterate, without any pressure to merge before it's ready.

The main thing I'll be looking at is how it fits the v4 frontend architecture. The panel was recently reworked to use runtime Home Assistant components (non-iframe) and an ESM/Rollup build — that layer was fragile in the past, so the key question is whether the editor lives as its own self-contained panel/view and respects that runtime-component structure, rather than touching the existing bundle in ways that could regress it. If you can keep it cleanly separated, that makes review and long-term maintenance much easier.

On maintenance: I appreciate you being upfront that you may not be able to maintain it long-term. That's okay — if it lands, ongoing upkeep can be shared/owned on this side. Just wanted to acknowledge it so there are no surprises.

Looking forward to the draft — thanks again for building this! 🚀

[EpicLPer]

PR created :) Thanks for the infos! #39