HACS and Updates

HACS and Updates

HACS update visibility can lag behind GitHub release state. When Home Assistant still shows an older Humidity Intelligence version, start with the update path Home Assistant and HACS can actually see.

First Checks

Check:

• the installed Humidity Intelligence version in Home Assistant
• the latest GitHub release
• whether the repository is still added in HACS
• whether HACS has refreshed repository information
• whether Home Assistant has been restarted after install/update

Latest releases:

Humidity Intelligence releases

The repository may stage a newer manifest.json version before a GitHub release is published. HACS users should treat GitHub Releases and the installed Home Assistant version as the user-facing publication evidence.

For v2.0.8, the repository metadata may show Home Assistant Core 2026.7 percentage-unit compatibility before the matching GitHub Release is visible. After installing and restarting, computed humidity, target, drift, and delta sensors should keep the same entity IDs, values, diagnostics meaning, and generated-card display behavior.

After The V2.0.9 Update

After HACS offers v2.0.9 and the matching GitHub Release is published:

1. update or re-download the integration through HACS
2. perform a full Home Assistant restart
3. refresh or re-export generated cards where relevant
4. verify new JSON and card YAML under /config/humidity_intelligence/exports/ and /config/humidity_intelligence/ui/
5. update any file-sensor, script, shell-command, or support-tool consumers that still point at a retained config-root file
6. run self_check or v205_release_check and review the fresh output before cleaning up a legacy file

HACS availability follows the matching GitHub Release and HACS refresh state rather than repository metadata alone.

v2.0.10 Beta Candidate Boundary

Repository identity 2.0.10-beta.7 is an unreleased validation candidate, not a published HACS or Stable claim. If Senyo separately authorizes a candidate install, install the exact custom_components/humidity_intelligence/ package as one coherent directory and fully restart Home Assistant. Do not copy the repository root into custom_components; docs, tests, site sources, workflows, and gallery examples are not part of the installable payload.

The candidate requires no config-entry, entity-registry, stored-data, threshold, service, or lane migration. Its one-row/cyan V2 card change does require a fresh card export and complete Manual-card YAML replacement, followed by a frontend refresh if cached. Candidate install, restart, playback, and soak are optional advisory Lab activities, not promotion or release gates. Publication and Stable promotion remain governed by canonical validation, review, CI, version governance, and explicit maintainer approval.

If HACS Still Shows An Older Version

Try this sequence:

1. Open HACS.
2. Open the Humidity Intelligence integration entry.
3. Use the HACS option to update or refresh repository information if available.
4. Re-check the version HACS offers.
5. Download/update through HACS.
6. Restart Home Assistant after the update.
7. Check the integration version again.

Always perform a full Home Assistant restart after replacing the integration package. A config-entry reload alone cannot activate newly installed Python modules or changed service schemas; use entry reload only after the updated package code is already loaded.

When the GitHub release exists and Home Assistant still offers an older version, stale local HACS/Home Assistant update state is the most useful first thing to clear.

What To Include In A HACS Issue

Include:

• version shown by GitHub releases
• version shown by HACS
• version shown by Home Assistant after restart
• whether HACS repository information was refreshed
• whether the integration was re-downloaded or updated
• whether Home Assistant was restarted after the update
• native Home Assistant diagnostics if available

Keep The Evidence Clean

Use a careful sequence before changing files by hand:

• collect version evidence before removing the integration
• let HACS manage files for HACS-managed installs
• handle dashboard symptoms through the generated-UI path
• handle runtime symptoms through diagnostics and reason text

Keep the evidence simple: GitHub release version, HACS offered version, Home Assistant installed version, and what refresh/restart steps were tried.

Source Of Truth

GitHub release pages, manifest.json, hacs.json, and repository release notes carry release/package truth. This Wiki explains the support path.

---

Previous	Next
Services Reference	FAQ