Skip to content

Generated Dashboards

Senyo edited this page Jun 7, 2026 · 8 revisions

Generated Dashboards

Humidity Intelligence can generate Lovelace dashboard YAML so the UI reflects the same runtime truth used by the backend. The dashboard is not a second control engine. It is a display surface for configured telemetry, mappings, diagnostics, and reason text.

Core Rule

Generated dashboards must reflect backend truth.

They must not invent:

  • entities
  • rooms
  • zones
  • services
  • alert sources
  • lane decisions
  • output actions
  • air-quality thresholds
  • health claims

If a value is unknown, unavailable, optional, or not configured, the generated UI should hide or degrade safely rather than pretending data exists.

When To Refresh Or Export

Refresh or export generated dashboards after changes such as:

  • editing Humidity Intelligence options
  • changing output detail visibility
  • adding or removing configured telemetry
  • changing zone, room, output, humidifier, or air-quality mappings
  • installing or removing optional frontend cards
  • updating Humidity Intelligence to a version with generated-card changes

The README and service documentation remain the source of truth for the exact services available in the current release.

Optional Frontend Cards

Optional frontend cards can improve presentation, but they must not block core Humidity Intelligence runtime behavior.

If a frontend dependency is missing or Home Assistant cannot expose enough Lovelace resource information, treat it as a dashboard/support issue first. It does not automatically mean the backend control engine is broken.

Common Symptoms

The dashboard still looks old after an options change

Try:

  1. Run the supported dashboard refresh/export flow from the current README.
  2. Reload the dashboard in Home Assistant.
  3. Clear browser/app cache if the old card layout is still visible.
  4. Restart Home Assistant if the generated entities or card data still look stale.

A card is missing a chip or row

Check whether the source data is configured and available. Optional rows should not appear when their required backend or diagnostics truth is missing.

A card shows unavailable entities

Check the configured entities in Home Assistant first. The generated card can only show truth from the entities and mappings Home Assistant provides.

Output details are hidden

Output details visibility is a generated-card display option. It should not change runtime output behavior, lane selection, manual override behavior, isolation switches, diagnostics, or entity names.

What To Attach In A UI Issue

Include:

  • Humidity Intelligence version
  • Home Assistant version
  • generated layout name if known
  • what changed before the issue appeared
  • screenshot with private details removed
  • native Home Assistant diagnostics download
  • whether optional frontend cards are installed
  • whether the dashboard was refreshed/exported after the change

Do not post private entity IDs, local URLs, addresses, device IDs, tokens, or full personal dashboards publicly.

Clone this wiki locally