docs+log v1.16.2 (issue #2): document correct card resource URL /houseplan_files/houseplan-card.js and warn against the /custom_components/... on-disk path (text/plain → 'Custom element doesn't exist'); integration logs the served URL + YAML-mode manual-add hint. README en+ru troubleshooting note.

README.md

@@ -60,6 +60,21 @@ Key advantages in short:
 
 The card is registered automatically — no need to add a Lovelace resource manually.
 
+> **Card doesn't load (`Custom element doesn't exist: houseplan-card`) or you manage Lovelace
+> resources in YAML?** Add the resource manually pointing at the URL the integration *serves*:
+>
+> ```yaml
+> resources:
+>   - url: /houseplan_files/houseplan-card.js
+>     type: module
+> ```
+>
+> Do **not** use `/custom_components/houseplan/frontend/houseplan-card.js` — that is the file
+> on disk, which Home Assistant does not serve over HTTP (you'll get a `text/plain` MIME error
+> and the element never registers). The correct, integration-served URL is
+> `/houseplan_files/houseplan-card.js`. Both cards (`houseplan-card` and
+> `houseplan-space-card`) ship in that one file — no separate resource is needed.
+
 ### Manually
 
 1. Copy the `custom_components/houseplan` folder into the `config/custom_components` directory of your Home Assistant.

README.ru.md

@@ -60,6 +60,21 @@ House Plan показывает ваш умный дом так, как он в
 
 Карточка подключается автоматически — добавлять ресурс Lovelace вручную не нужно.
 
+> **Карточка не грузится (`Custom element doesn't exist: houseplan-card`) или вы ведёте ресурсы
+> Lovelace в YAML?** Добавьте ресурс вручную, указав URL, который *раздаёт сама интеграция*:
+>
+> ```yaml
+> resources:
+>   - url: /houseplan_files/houseplan-card.js
+>     type: module
+> ```
+>
+> **Не** используйте `/custom_components/houseplan/frontend/houseplan-card.js` — это путь к файлу
+> на диске, который Home Assistant не отдаёт по HTTP (получите ошибку MIME `text/plain`, и элемент
+> не зарегистрируется). Правильный URL, который раздаёт интеграция, — `/houseplan_files/houseplan-card.js`.
+> Обе карточки (`houseplan-card` и `houseplan-space-card`) лежат в этом одном файле — отдельный ресурс
+> не нужен.
+
 ### Вручную
 
 1. Скопируйте папку `custom_components/houseplan` в каталог `config/custom_components` вашего Home Assistant.

custom_components/houseplan/__init__.py

@@ -79,8 +79,21 @@ async def async_setup_entry(hass: HomeAssistant, entry: HouseplanConfigEntry) ->
     # start of the mobile app). If the resource registry is unavailable (YAML-mode
     # Lovelace, old versions) — fall back to extra_module_url.
     module_url = f"{FRONTEND_URL}?v={VERSION}"
-    if not await _register_lovelace_resource(hass, module_url):
+    registered = await _register_lovelace_resource(hass, module_url)
+    if not registered:
         add_extra_js_url(hass, module_url)
+    # Tell the user exactly where the card lives — the #1 support issue is people adding a
+    # Lovelace resource pointing at the on-disk path (/custom_components/...), which HA does
+    # not serve (wrong MIME → "Custom element doesn't exist"). The correct served URL is below.
+    if registered:
+        _LOGGER.info("House Plan card auto-registered as a Lovelace resource: %s", module_url)
+    else:
+        _LOGGER.info(
+            "House Plan card is served at %s . Lovelace resources look YAML-managed — add it "
+            "manually under `resources:` as { url: %s, type: module }. Do NOT use the on-disk "
+            "path /custom_components/houseplan/frontend/houseplan-card.js (HA does not serve it).",
+            module_url, module_url,
+        )
 
     await async_check_plan_files(hass, entry)
     return True

custom_components/houseplan/const.py

@@ -11,7 +11,7 @@ PLANS_DIR = "houseplan/plans"  # relative to the HA configuration directory
 FILES_URL = "/houseplan_files/files"
 FILES_DIR = "houseplan/files"
 CONF_ADMIN_ONLY = "admin_only"
-VERSION = "1.16.0"
+VERSION = "1.16.2"
 
 DEFAULT_CONFIG: dict = {
     "spaces": [],

custom_components/houseplan/manifest.json

@@ -16,5 +16,5 @@
   "issue_tracker": "https://github.com/Matysh/houseplan-card/issues",
   "requirements": [],
   "single_config_entry": true,
-  "version": "1.16.0"
+  "version": "1.16.2"
 }

docs/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog
 
+## v1.16.2 — 2026-07-11 (docs+log: correct card resource URL — fixes "Custom element doesn't exist")
+- **Support issue #2**: users adding a Lovelace resource that points at the on-disk path
+  `/custom_components/houseplan/frontend/houseplan-card.js` get a `text/plain` MIME error and
+  "Custom element doesn't exist: houseplan-card" — HA does not serve `custom_components/` over
+  HTTP. The integration serves the card at **`/houseplan_files/houseplan-card.js`** (verified:
+  `200 text/javascript`) and auto-registers it as a Lovelace resource in storage mode.
+- README (en+ru) now documents the correct URL and the common mistake, incl. a YAML-mode
+  `resources:` snippet.
+- On setup the integration logs (INFO) the exact served URL and, when Lovelace resources are
+  YAML-managed, how to add it manually — so the fix is discoverable from the logs.
+
+## v1.16.1 — 2026-07-08 (space-card shows room fills as configured)
+- **The static `houseplan-space-card` now renders room fills exactly as configured on the
+  full card** (temperature / signal / lights coloring), as a snapshot of the states passed
+  in via `hass` — reverting the v1.16.0 omission. The card still does not subscribe to state
+  changes itself and stays non-interactive (`pointer-events:none`); fills refresh when HA
+  hands the card an updated `hass`. Added shared `areaLqi()` in devices.ts.
+
 ## v1.16.0 — 2026-07-08 (new: houseplan-space-card + deep-link)
 - **New second card `custom:houseplan-space-card`** — a READ-ONLY, static schematic of a
   single space, embeddable on any dashboard. Draws the configured plan + room borders/names +

docs/STATUS.md

@@ -13,7 +13,7 @@
 
 | Item | State |
 |---|---|
-| Version | **v1.16.0** everywhere (manifest, const.py, package.json, CARD_VERSION) |
+| Version | **v1.16.2** everywhere (manifest, const.py, package.json, CARD_VERSION) |
 | GitHub | https://github.com/Matysh/houseplan-card — branch `main`, releases v1.9.3…v1.11.2 |
 | CI | `.github/workflows/validate.yml` (hacs + hassfest + frontend + backend) — **fully green** since v1.11.1; `release.yml` auto-attaches the card bundle (needs `permissions: contents: write`, fixed) |
 | HACS | Works as custom repository (id 1290210112 on the home instance). **Inclusion PR: https://github.com/hacs/default/pull/9004** (queue ≈2 months as of 2026-07). Lesson: #8995 was auto-closed by hacs-bot — the PR body MUST be their exact template with every checkbox ticked and all 3 links (release, HACS action run, hassfest run); a custom body gets closed without discussion |
@@ -65,6 +65,8 @@
 - **v1.16.0** — NEW read-only `houseplan-space-card` (static single-space schematic,
   pointer-events:none, deep-link button) + `#space=<id>` deep-link in the full card; shared
   space-geometry/space-render + module-level config cache (config-store).
+- **v1.16.1** — space-card renders room fills as configured on the full card (snapshot),
+  no longer omitted; +shared areaLqi().
 
 ## Where things live
 

docs/TESTING.md

@@ -171,7 +171,7 @@ require hands on real hardware — they remain for the human pass.
 
 ## houseplan-space-card (read-only embedded)
 - [ ] `type: custom:houseplan-space-card, space: <id>` renders the space identical to the full
-      card's plan (background + configured borders/names + icons), no header/controls [auto]
+      card's plan (background + configured borders/names + room fills + icons), no header/controls [auto]
 - [ ] The schematic is fully non-interactive: click/hover anywhere does nothing — no more-info,
       no tooltip, no drag (`.hp-static-stage` is pointer-events:none) [auto]
 - [ ] Footer button opens the full component already showing that space (deep-link `#space=<id>`) [auto]

package.json

@@ -1,6 +1,6 @@
 {
   "name": "houseplan-card",
-  "version": "1.16.0",
+  "version": "1.16.2",
   "description": "Interactive house plan Lovelace card for Home Assistant",
   "license": "MIT",
   "type": "module",

src/devices.ts

@@ -315,6 +315,17 @@ export function areaLights(hass: any, devices: { area: string; entities: string[
 }
 
 /** Average temperature across the area's devices (null when nothing reports one). */
+/** Average zigbee signal (LQI) across an area's non-virtual devices, or null. */
+export function areaLqi(hass: any, devices: { area: string; virtual?: boolean; entities: string[] }[], area: string): number | null {
+  const vals: number[] = [];
+  for (const d of devices) {
+    if (d.area !== area || d.virtual) continue;
+    const l = lqiFor(hass, d.entities);
+    if (l != null) vals.push(l);
+  }
+  return averageLqi(vals);
+}
+
 export function areaTemp(
   hass: any,
   devices: { area: string; icon?: string; entities: string[] }[],

src/houseplan-card.ts

@@ -26,7 +26,7 @@ import './space-card';
 import { cardStyles } from './styles';
 import { langOf, t, type I18nKey } from './i18n';
 
-const CARD_VERSION = '1.16.0';
+const CARD_VERSION = '1.16.2';
 const LS_KEY = 'houseplan_card_layout_v1';
 const LS_CFG = 'houseplan_card_cfg_v1'; // cache of the server config+layout for instant rendering
 const LS_ZOOM = 'houseplan_card_zoom_v1';

src/space-render.ts

@@ -1,13 +1,14 @@
 /**
  * Shared STATIC renderer for a single houseplan space — used by the read-only
  * `houseplan-space-card`. Draws exactly what is CONFIGURED (plan background,
- * configured room borders/names, device markers at their saved positions), with
- * NO live states, NO status/temperature fills, and NO event handlers.
+ * configured room borders/names, device markers at their saved positions), with NO interactivity
+ * (pointer-events:none) and NO state subscription; room fills are rendered exactly as
+ * configured on the full card (a snapshot of the current states passed via `hass`).
  * Geometry/model math lives in space-geometry.ts (pure, unit-tested).
  */
 import { html, svg, nothing, type TemplateResult } from 'lit';
-import { buildDevices } from './devices';
-import { spaceDisplayOf } from './logic';
+import { buildDevices, areaLqi, areaLights, areaTemp } from './devices';
+import { spaceDisplayOf, roomFillColor } from './logic';
 import { DEFAULT_ICON_RULES, compileIconRules, EXCLUDED_DOMAINS } from './rules';
 import { t, type Lang } from './i18n';
 import type { ServerConfig } from './types';
@@ -67,8 +68,25 @@ export function renderSpaceStatic(o: StaticRenderOpts): TemplateResult | null {
       let style = '';
       if (disp.showBorders || disp.fill !== 'none') {
         cls += ' styled';
-        // STATIC: only the configured border; status fills (lqi/light/temp) are live and omitted
-        style = `--room-stroke:${disp.color};--room-stroke-op:${disp.showBorders ? disp.opacity : 0};--room-fill:transparent;--room-fill-op:0`;
+        const parts = [`--room-stroke:${disp.color}`, `--room-stroke-op:${disp.showBorders ? disp.opacity : 0}`];
+        // fill rendered exactly as configured on the full card (snapshot of current states)
+        const fillC = r.area
+          ? roomFillColor(
+              disp.fill,
+              disp.fill === 'lqi' ? areaLqi(o.hass, devs, r.area) : null,
+              disp.fill === 'light' ? areaLights(o.hass, devs, r.area) : 'none',
+              disp.fill === 'temp' ? areaTemp(o.hass, devs, r.area) : null,
+              disp.tempMin,
+              disp.tempMax,
+            )
+          : null;
+        if (fillC) {
+          cls += ' filled';
+          parts.push(`--room-fill:${fillC}`, `--room-fill-op:${(0.3 * disp.opacity).toFixed(3)}`);
+        } else {
+          parts.push('--room-fill:transparent', '--room-fill-op:0');
+        }
+        style = parts.join(';');
       }
       const svgLabel = !space.bg && !disp.showNames;
       const c = roomCenter(r);