Visual before technical
The editor should let you work with rooms and devices directly instead of making coordinates, SVG details, and YAML the starting point.
HAFloorplan helps Home Assistant users turn the layout they already understand—their home—into a native interactive dashboard without manually assembling every coordinate and YAML element.
Home Assistant includes the Picture Elements card out of the box. It is one of the most flexible ways to create a floor-plan dashboard that reflects the way your home actually looks and behaves.
But creating a floor plan tailored to your home usually means solving several different problems at once: crafting the floor-plan layout, mapping the right Home Assistant entities, positioning each device, defining state-driven room behavior, and building the YAML that ties all of it together.
Even for a seasoned Home Assistant user with the right technical know-how, the initial setup can easily consume a weekend. For everyone else, the bar is even higher. That complexity keeps many people from ever trying one of Home Assistant's most compelling built-in dashboard capabilities.
HAFloorplan exists to lower that bar. The goal is to let anyone get a taste of what Picture Elements can do: create a simple floor plan that represents their home, place and connect devices visually, and generate the native Home Assistant configuration needed to bring it to life.
Visual editor in. Native Picture Elements out.
HAFloorplan should remove authoring friction while preserving the strengths of Home Assistant itself.
The editor should let you work with rooms and devices directly instead of making coordinates, SVG details, and YAML the starting point.
Ask users only for the information HAFloorplan cannot safely infer, then generate the native Home Assistant configuration for them.
HAFloorplan is an authoring companion. The exported dashboard uses Home Assistant Picture Elements rather than a proprietary dashboard runtime.
The current MVP keeps project work in the browser, works without an account, and does not ask for Home Assistant credentials or tokens.
The normal MVP workflow does not require HACS, a custom Lovelace card, or a custom JavaScript resource at runtime.
The goal is the shortest path to a working Home Assistant floor-plan dashboard—not architectural-grade CAD or interior-design fidelity.
HAFloorplan started from a simple frustration: creating an interactive floor-plan dashboard in Home Assistant required too much manual configuration. I built HAFloorplan to explore whether that process could be made visual, simple, and accessible without requiring users to become YAML or frontend experts.
Along the way, the project has also become an exploration of modern AI-assisted software development—from product design and architecture to testing, deployment, and iteration.
These acknowledgements recognize inspiration and infrastructure. They do not imply sponsorship, partnership, or endorsement.
Home Assistant and its community created the platform, entity model, and native Picture Elements capability that HAFloorplan is designed to make easier to author.
Explore Picture Elements ↗Floorplanner is an inspiration and UX benchmark for approachable browser-based floor-plan editing. HAFloorplan is not affiliated with Floorplanner and is not based on or derived from Floorplanner.
Visit Floorplanner ↗Northflank provides hosting and deployment infrastructure used to operate the public HAFloorplan application.
Visit Northflank ↗HAFloorplan is an independent project and is not affiliated with or endorsed by Home Assistant or Nabu Casa.
Draw the rooms you need, place your devices, connect Home Assistant entities, and generate native Picture Elements configuration visually.
Open Editor