All 55 3D Print 6 AI & Agents 8 Cases 5 E-commerce 6 Front-End 10 Smart Home 5 UX/UI Design 15

Published on: 16/08/2026 · ID 224

Lovelace: Hygiene of Entity IDs (Home and Studio)

Dead IDs on the dashboard: mmWave, ZHA→Z2M, WLED, Echo, pool. Unavailable ThinQ ≠ typo of the card.

Smart Home

What type of article is this? A maintenance ritual for Lovelace — what I corrected in the Home and Studio views when the house ‘seemed offline’ and it was merely an old ID.

Thesis The dashboard is a mirror. A dead entity ID lies louder than a light turned off.
Map of dead IDs Lovelace
Figure 1 — Recent mapping: presence, occupancy, Echo, WLED, pool; ThinQ aside.

Mapping That Was Worthwhile

  • mmWave office → Wi-Fi presence (correct role).
  • ZHA TV room → Z2M occupancy.
  • media_player.office → oficina_echo_dot_office.
  • WLED DigQuad / Central → Gledopto (and check the ping of IPs .180–.183).
  • Heating card → Z2M pool entity.
  • Repellent / UPS studio → current Z2M ID.
Views Home Studio
Figure 2 — Views by context: Home, Studio, office, pool.

How to Diagnose in 3 Minutes

  1. Unavailable card → open entity. Does it exist?
  2. Device UniFi home + climate unavailable → ThinQ/API, not a typo.
  3. Hue light unavailable + AP ok → physical/cloud Hue offline.
  4. WLED dead → ping the IP before ‘fixing’ the YAML.

A mature smart home has a SOP for renaming: update integration → entity → automation → Lovelace in the same mental commit.

Continue reading