FAQ

FAQ

What is the Wiki for?

The Wiki is the public support manual.

Runtime behavior, entity semantics, generated dashboard logic, diagnostics, services, release state, and migration requirements are defined by the repository source, DESIGN_BRIEF.md, README.md, docs/, manifest.json, hacs.json, and release notes.

How does Humidity Intelligence make control decisions?

Humidity Intelligence is deterministic. It resolves one explainable control decision per evaluation cycle using configured Home Assistant telemetry, gates, profiles, mappings, and priority rules.

Why does the reason panel matter?

The reason panel shows why Humidity Intelligence selected the current runtime state. It reflects backend truth and keeps dashboard language tied to the active decision.

If the reason panel and generated dashboard disagree with runtime behavior, report it as a UI truth consistency issue.

What role do generated dashboards play?

Generated dashboards are a supported display surface. Backend runtime behavior remains owned by the integration, while optional frontend cards improve presentation where available.

Why is a chip or dashboard row missing?

Usually because the source data is outside the current configuration, unavailable, optional, or absent from the current generated-card mapping. Optional UI stays safest when it appears only with real source truth behind it.

What does output detail visibility change?

Output detail visibility changes the generated-card display. Lane selection, output writes, manual override behavior, isolation switches, diagnostics, and entity names remain backend-owned.

How should I handle carbon-monoxide safety?

Use certified carbon-monoxide alarms as the primary safety system.

Humidity Intelligence can reflect configured carbon monoxide telemetry and can use configured carbon monoxide data in its emergency behavior where supported by the current release. It acts as an additional Home Assistant awareness layer.

Install and maintain certified carbon monoxide alarms according to local regulations, manufacturer guidance, and applicable safety requirements.

Why do maintainers ask for diagnostics?

Diagnostics show the configured Home Assistant context: version, selected entities, runtime state, gates, warnings, generated-card summary, and unavailable or unknown configured entities. This is much faster and safer than guessing from screenshots.

Which diagnostics file should I share?

Use native Home Assistant diagnostics for public GitHub issues unless a maintainer asks for another file.

The humidity_intelligence.dump_diagnostics service is a fuller local debug export and may contain more local context. Review it carefully before sharing.

HACS still shows an old version. What should I check?

HACS and Home Assistant update state can be stale even when the GitHub release exists. Refresh HACS repository information, update or re-download through HACS, restart Home Assistant, and then check the installed version again.

Can I use private entity names in an issue?

Public GitHub issues are public. If entity names reveal private rooms, people, addresses, devices, or routines, sanitize them first.

Use examples like:

sensor.example_room_humidity
switch.example_fan
binary_sensor.example_gate

How do community comments or reactions affect features?

Comments and reactions are useful interest signals. Maintainer review and the proposal/release process decide what gets implemented.

---

Previous	Next
HACS and Updates	Configuration Walkthrough