Claude c654e0ec42 test(smoke): masonry of a real plan must not break
Eight closed issues on wall junctions — #271, #272, #275, #276, #277, #278,
\#279, #280 — shipped in beta.9, and the break in the owner's real plan
survived. Every one of them was accepted on synthetic fixtures: a cell-5
mixed-depth T, a rectilinear T with three equal half-depths. On those the fixes
work.

The smoke asks the product itself, through isPointInFill on the wall path,
whether masonry exists where the model promises it. That is independent of both
resolution and the pixel-diff thresholds which miss this class: a 45-step break
on a large plan is a fraction of a per cent of the frame, well under the 0.05
per cent scene tolerance.

Measured on the shipped code: four breaks, 181 grid steps in total, 45.25 each.
That number is derivable rather than incidental — the node joins a 30 cm
exterior wall, a 30 cm spur and an arm five steps long; half-depth 15,
MITRE_LIMIT 4, corridor radius 60, and 60 − 15 = 45 steps are cut out of the
neighbouring 20 cm wall. The corridor eats the masonry, which is what #271 and
\#275 describe.

The fixture is privacy-minimised — neutral room names and ids, no device
bindings — and keeps its coordinates, because they are the point. It lives in
test/fixtures rather than demo/fixtures on purpose: sourceFingerprint hashes the
.mjs of demo/fixtures and demo/golden, so anything added there staleizes the
committed bundle and the screenshot manifest at once. Verified after this
commit: bundle still fresh, screenshots still current.

The debt is recorded as numbers and compared exactly. Better and the test asks
for the numbers to be updated, which proves the improvement; worse and it
catches the regression. Verified by execution in both directions.

Issue: #285
User-Visible: no
2026-08-24 13:02:56 +03:00
2026-08-24 10:55:56 +03:00

🏠 House Plan — a live home map for Home Assistant

HACS Custom GitHub release CI Live demo Telegram chat

📘 Full user guide · 🇷🇺 Русский · 🗂 Project issues

Your whole home at a glance

House Plan turns Home Assistant into a live map of your home. Upload a plan or draw rooms directly on the dashboard, bind them to Home Assistant areas, and the area's devices appear automatically. You can immediately see where a light is on, a door is open, a room is too cold, Zigbee signal is weak, or a leak sensor has fired.

Synthetic home in View mode with rooms, devices, light and climate

Setup is entirely graphical: no floor-plan YAML, Inkscape, or external editor. Plan data and device positions live on the Home Assistant server and stay in sync across screens.

Edit on a desktop computer. View and kiosk are fully supported on phones and tablets. The editors are designed primarily for a mouse and keyboard; individual touch editing operations may be awkward or unavailable. See the exact touch support contract.

What House Plan provides

  • Live state and safe actions. Lights and other safe devices can toggle from the plan; a lock cannot be opened by an accidental plan tap.
  • Three built-in editors. Plan creates rooms, walls and openings; Device places and configures markers; Background adds lines, labels and furniture.
  • Area-aware rooms. New devices appear automatically, while room cards can show temperature, humidity, light state and average LQI.
  • Light and environment. Room fills, lamp Glow, wall shadows, a day-cycle backdrop and sunlight through windows.
  • Doors, windows, gates and vacuums. Openings follow real contacts and locks; a robot can show its position, dock and travelled path.
  • Several floors and screens. Space tabs, swipe navigation, local viewport, and a separate initial floor for each card.
  • Wall-display kiosk. A plan-only view with fullscreen navigation and icon sizes saved for that display.

The same synthetic home in touch View mode

Your first working room

  1. Install the integration and add the card to a dashboard.
  2. Create the first space: upload SVG/PNG/JPG/WebP, reuse an uploaded image, or choose no image and draw the plan by hand.
  3. In Plan, select Room outline, place vertices, and click the first point to close the outline.
  4. Name the room and bind it to a Home Assistant area. Use “No area” for a room that has no devices.
  5. Open Device: devices from the bound area are already placed; drag their markers to the correct positions.
  6. Optionally use Background for lines, text and furniture.
  7. Return to View. The plan now displays live state and accepts safe actions.

Creating the first space

Closing a room outline on its first point

A selected partition and the Plan context tray

Device settings with binding provenance and the exact action result

Live presentation preview for the same device

Every workflow and edge case is in the full user guide. The Background editor contract and vacuum guide are the authorities for those subsystems.

Installation

HACS

Open the repository in HACS

  1. In HACS open ⋮ → Custom repositories.
  2. Add https://github.com/Matysh/houseplan-card as an Integration.
  3. Install House Plan and restart Home Assistant.
  4. Open Settings → Devices & services → Add integration → House Plan.

The card is registered automatically. If you manage Lovelace resources manually, use the URL served by the integration:

resources:
  - url: /houseplan_files/houseplan-card.js
    type: module

Do not use the on-disk path inside custom_components; Home Assistant does not serve that path as a JavaScript module.

Manual installation

Copy custom_components/houseplan to config/custom_components, restart Home Assistant, and add the House Plan integration.

Add the card

Create a dashboard view (Panel works best) and add the card in the UI or as:

type: custom:houseplan-card
title: House plan

Different screens may start on different spaces:

type: custom:houseplan-card
default_floor: ground

All cards share server-side rooms and coordinates. Current mode, viewport and selected space remain local to the screen. Revision checks and live sync cover concurrent clients, but avoid editing the same object in two browsers at once.

Detailed documentation

Support and feedback

  • Questions and plan examples: Telegram @ha_houseplan.
  • Bugs and proposals: GitHub Issues.
  • Before reporting, update House Plan, restart HA and hard-refresh the page. Include the version, browser, logs and reproduction steps; private entity IDs may be replaced with fictional ones.

Documentation screenshots are produced by the reproducible npm run build && node demo/docs/capture.mjs command using synthetic data only. Scenario version, source fingerprint and every image hash are recorded in the screenshot index.

License: MIT.

S
Description
Интерактивный план дома для Home Assistant — Lovelace card + custom component
Readme MIT
542 MiB
Languages
JavaScript 51%
TypeScript 35.8%
Python 12.9%
Shell 0.2%