Generated Dashboards

Generated Dashboards

Humidity Intelligence can generate Lovelace dashboard YAML so the UI reflects the same runtime truth used by the backend. The dashboard works as a display surface for configured telemetry, mappings, diagnostics, and reason text.

Core Rule

Generated dashboards are designed to reflect backend truth.

Dashboard content is grounded in backend and repository truth for:

• entities
• rooms
• zones
• services
• alert sources
• lane decisions
• output actions
• air-quality wording
• supported safety guidance

When a value is unknown, unavailable, optional, or outside the current configuration, the generated UI can stay honest by hiding that surface or showing a safe degraded state.

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, while the core Humidity Intelligence runtime remains backend-owned.

When a frontend dependency is missing or Home Assistant exposes limited Lovelace resource information, start with the dashboard/support path first. The backend control engine has its own runtime evidence surfaces.

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 appear when their required backend or diagnostics truth is present.

A card shows unavailable entities

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

Output details are hidden

Output details visibility is a generated-card display option. Runtime output behavior, lane selection, manual override behavior, isolation switches, diagnostics, and entity names stay owned by the backend.

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

Keep private entity IDs, local URLs, addresses, device IDs, tokens, and full personal dashboards out of public issue text.