-
-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Try this sequence:
- Open HACS.
- Open the Humidity Intelligence integration entry.
- Use the HACS option to update or refresh repository information if available.
- Re-check the version HACS offers.
- Download/update through HACS.
- Restart Home Assistant after the update.
- Check the integration version again.
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.
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
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.
GitHub release pages, manifest.json, hacs.json, and repository release notes carry
release/package truth. This Wiki explains the support path.
Next: FAQ