Troubleshooting Generated UI

Troubleshooting Generated UI

Generated dashboards are display surfaces. They should show what Humidity Intelligence knows from backend telemetry, mappings, diagnostics, and runtime state.

If the UI looks wrong, start by separating three things:

• backend runtime truth
• generated card export state
• Home Assistant dashboard/browser cache state

That keeps a dashboard symptom from being misread as a control-engine failure.

Quick Checks

1. Check the active HI runtime mode and reason text.
2. Check whether the relevant configured entities are available.
3. Run the supported dashboard refresh or export service from the README.
4. Reload the dashboard.
5. Clear browser or app cache if an old layout still appears.
6. Download native Home Assistant diagnostics if the issue continues.

Old Layout Still Showing

This is usually one of:

• dashboard YAML still needs a fresh export
• Manual card YAML still needs the refreshed export pasted in
• browser/app cache is showing an older dashboard
• Home Assistant still needs to reload generated entity/card data

Try:

1. run humidity_intelligence.dump_cards or the current supported export flow
2. open the generated YAML file in Home Assistant's config folder
3. paste the refreshed YAML into the relevant Manual card
4. reload the dashboard
5. restart Home Assistant if generated entity/card data still looks stale

Missing Chips Or Rows

Missing optional UI is usually safer than fake UI.

A chip or row may be hidden because:

• the source telemetry is outside the current configuration
• the source entity is unavailable
• the optional row is disabled
• diagnostics still need the required mapping
• the current layout uses a different optional display set

The generated UI stays trustworthy by showing rows only when the required source truth is available.

Wrong Room, Zone, Or Source Label

Room, zone, source, and output labels should come from configured telemetry, mappings, diagnostics, or backend truth.

Check:

• telemetry room labels
• level assignments
• zone room assignments
• output mappings
• diagnostics mapping summary
• generated card export after saving options

Use configured labels and sanitized examples rather than hand-written private placeholder labels in public card examples.

Output Details Are Hidden

Output details visibility is a generated-card display option.

Backend truth continues to own:

• selected lane
• output writes
• entity names
• manual override behavior
• isolation switches
• diagnostics
• runtime control

After changing this option, refresh or export the generated dashboard so the Manual card has the latest YAML.

Alert-Only Mode Looks Different

Alert-only mode intentionally changes what the generated UI should show. Control surfaces and reason text should match the intentionally reduced control surface.

After toggling alert-only mode:

1. save options
2. let HI reload/regenerate
3. export or refresh cards if needed
4. update Manual card YAML

What To Attach In A UI Issue

Attach or include:

• HI version
• Home Assistant version
• layout name if known
• what option or update happened before the issue
• native Home Assistant diagnostics
• sanitized screenshot if useful
• whether card YAML was refreshed/exported
• whether browser/app cache was cleared

Use sanitized screenshots and examples so private entity IDs, addresses, local paths, device IDs, tokens, and personal telemetry stay private.

---

Previous: Air Quality and CO Safety | Next: Release Validation for Users