Repository navigation
Migration Guide V1 to V2
V1 was template-based. V2 is a structured integration with configuration flow and runtime validation. Migration is required for the V1 backend. Existing V2 users should use HACS and Updates instead.
The preserved V1 migration reference records the original transition. This guide uses the current HACS integration listing and separates the retired V1 backend from the retained V1 presentation skin.
Keep a restorable Home Assistant backup and copies of the V1 package, template, configuration includes and saved dashboard YAML before making changes. Check for any local additions before removing a file or include.
V1 was registered as a Template in HACS and installed under custom_templates.
Open its HACS entry, remove that old Template registration, then restart Home
Assistant as required by the removal flow. It must not remain the update path for V2.
Remove the retired V1 backend files from the active configuration after backing them
up, along with only their corresponding includes in configuration.yaml:
/config/custom_templates/humidity_intelligence.jinja
/config/packages/humidity_intelligence.yaml
Preserve unrelated templates, packages and includes. Check the configuration and restart Home Assistant to unload the retired backend before enabling V2 control. The old and new engines must not operate the same outputs in parallel.
HI is included in the HACS default integration repository. Find Humidity Intelligence under integrations, then download the published package. Check GitHub Releases and the version offered in HACS; repository source or a draft is not an available update.
The component belongs at:
/config/custom_components/humidity_intelligence/
Do not copy the repository root into custom_components or nest another
custom_components/humidity_intelligence tree inside the component. Keep old package
backups outside Home Assistant's integration discovery directory.
Fully restart Home Assistant after installation. Add Humidity Intelligence from Settings → Devices & services → Add integration, then use the Configuration Walkthrough to map sensors, gates, zones and outputs. Verify the actual selected entities rather than assuming V1 names carry over automatically.
V2 preserves the drift meaning: current HI house average humidity minus the seven-day mean. Create or verify the existing Home Assistant Statistics helper:
| Setting | Value |
|---|---|
| Name | House Humidity Mean 7d |
| Source | The actual registered HI House Average Humidity entity |
| State characteristic | mean |
| Max age | 7 days |
| Expected helper entity | sensor.house_humidity_mean_7d |
Do not create a duplicate helper if the correct one already exists. Missing,
unavailable, non-numeric or insufficient history is reported through the drift sensor,
Diagnostics, self_check, v205_release_check and Repairs. Allow Home Assistant to
build real history; do not fabricate samples or treat warm-up as a healthy reading.
Frontend dependency detection does not establish drift-helper readiness.
Back up and remove only the retired V1 UI references you actually used, such as old
files under /config/www/ or /config/lovelace/. Preserve unrelated dashboard content.
Use Home Assistant's supported dashboard editing/reload flow for the affected view.
The V2-generated v1_mobile compatibility skin is a separate, retained presentation
option. It remains exportable in v2.1.1 but is deprecated for new dashboards; prefer
V2 Mobile or Tablet. Removing the old V1 backend does not require deleting that
V2-generated skin.
Run refresh_ui, export with view_cards or dump_cards, and replace the complete
saved Manual-card YAML. Refresh the browser/app after saving. Follow
Generated Dashboards for revision and client checks.
Confirm the V2 entry loads, the actual entities and services are registered, the reason panel matches runtime state, and the saved dashboard reflects the correct exports. Check that retired template references no longer participate in control. Download reviewed diagnostics if an issue remains.
Rollback restores the matching prior backend, configuration and saved dashboard from your backups. Do not run V1 and V2 control in parallel. Package rollback requires a full restart; restoring a package alone does not restore pasted dashboard YAML.