FAQ

FAQ

Is the Wiki the source of truth?

No. The Wiki is a 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.

Does Humidity Intelligence use AI to make control decisions?

No. 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 is meant to show why Humidity Intelligence selected the current runtime state. It should reflect backend truth, not decorative dashboard logic.

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

Are generated dashboards required?

No. Generated dashboards are a supported display surface. Backend runtime behavior must not depend on optional frontend cards.

Why is a chip or dashboard row missing?

Usually because the source data is not configured, unavailable, optional, or not exposed in the current generated-card mapping. Missing optional UI should degrade safely rather than inventing data.

Does output detail visibility change runtime behavior?

No. Output detail visibility is a generated-card display choice. It should not change lane selection, output writes, manual override behavior, isolation switches, diagnostics, or entity names.

Does Humidity Intelligence replace carbon monoxide alarms?

No.

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 is not a certified carbon monoxide alarm, life-safety device, or compliance system.

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.

Should I upload dump_diagnostics?

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. Is the release broken?

Not necessarily. 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?

You can, but 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

Do community comments or reactions approve a feature?

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