Repository navigation
Output Monitoring
Optional output monitoring adds reported device conditions and gaps in monitoring to HI's dashboard. Introduced in v2.1.0, it remains available in v2.1.1. Check the version offered in HACS before updating.
Monitoring is disabled by default and native Outputs remains the default view. The observer reads configured outputs and diagnostic sources. It does not select control lanes, send output commands, change helpers or repair devices. An On state means Home Assistant reports On; it does not prove physical airflow, moisture production or device health. Missing or unavailable evidence remains a monitoring gap.
- Open Configure → Output monitoring.
- In Monitoring and dashboard view, enable monitoring and choose Native Outputs panel or Adaptive Outputs panel.
- Choose Add a monitoring rule, then select a configured output, its monitoring source, a meaning and an exact rule. Enumeration rules need active and clear values; numeric comparisons use the selected units without guessing.
- Review the preview and confirm the rule into the draft.
- Choose Keep changes and return, then Save changes on the main settings page to persist the draft.
Keep changes and return does not itself save. Discard this visit's monitoring edits restores the state from entry into that subflow while retaining earlier main-settings edits. Closing an unsaved flow writes nothing. Saving uses HI's usual entry reload, which resets existing in-memory runtime history, including Stability.
Use Manage monitoring rules to edit, revoke confirmation, replace a source, retain it as context only or explicitly resume interpretation. A replacement entity does not automatically inherit the old identity's meaning. To manage a formerly automatic source while observation is disabled, enable monitoring, save, then reopen Manage monitoring rules so the observer can load its saved history.
Select Add custom meaning while adding a rule, or use Manage reusable meanings to rename, edit or remove existing definitions. A meaning combines a name, an existing HI classification and optional What to do guidance. Each source keeps its own rule, threshold and identity. Guidance is plain text, not an executable action.
Names are limited to 80 characters, guidance to 240, and each HI entry supports up to 32 meanings. Editing an in-use classification requires review of affected rules; deleting an in-use meaning requires a replacement or explicit removal of its rules. Missing definitions remain unavailable rather than falling back to invented health. See the canonical meanings guide for cancellation, validation and recovery details.
Native Outputs uses Home Assistant entity rows without an additional resource. For adaptive presentation, manually register this JavaScript module in Home Assistant dashboard resources:
/humidity_intelligence/hi-adaptive-output-card.js
HI serves the file; it does not register resources or edit dashboards. The adaptive panel shows a compact attention summary, with the full evidence and preserved native controls under Outputs & controls. Incomplete monitoring remains visible separately from reported attention. Native controls remain available even when observation data is unavailable.
After choosing or changing the view, use the fresh generated export and replace the
complete saved Manual-card YAML. If regeneration is incomplete, use refresh_ui then
dump_cards or view_cards. Refresh the client after resource changes. Follow the
card update sequence.
If the resource fails to load, select native presentation, save, export again and replace the card. If moving from a companion prototype, disable that companion and remove its old resource before registering the packaged resource; they use the same custom-element name. Imports require explicit confirmation and do not remove the companion or import its monitoring history/custody.
Keep the prior complete package, saved entry settings, monitoring custody and saved card YAML together. Older packages reject the custom-meaning library key even when empty and lack its reference handling. A downgrade therefore requires matching settings and custody as well as the earlier package; retain the newer backup separately.
To remove adaptive presentation, select native Outputs, regenerate/export and replace the saved card before removing its resource. Disable observation if its earlier implementation cannot preserve the current custody safeguards. Installing or rolling back a package requires a full Home Assistant restart; it clears in-memory Stability history. See the canonical output guide for identity custody, companion migration and failure boundaries.