Release Validation for Users

Release Validation for Users

This page is a user-safe checklist for after updating Humidity Intelligence.

The maintainer release process stays in the repository release governance, version metadata, validation gates, and maintainer approval. This page gives users a safe post-update checklist.

After Updating

Check:

1. HACS or your install method shows the expected version.
2. Home Assistant has been restarted after the update.
3. Humidity Intelligence loads under Settings -> Devices & services.
4. Main HI entities are available.
5. The generated dashboard still renders.
6. The reason panel matches the active runtime state.
7. Native diagnostics can be downloaded if support is needed.

HACS Visibility

If HACS still shows an older version:

1. refresh HACS repository information
2. re-check the offered version
3. update or re-download through HACS
4. restart Home Assistant
5. check the installed version again

See HACS and Updates for the longer support path.

Dashboard Validation

After an update that touches generated cards, options, frontend dependencies, or output details:

1. run the supported card export or refresh flow
2. update Manual card YAML if you use Manual cards
3. reload the dashboard
4. clear browser/app cache if stale UI remains
5. check that chips and reason text reflect backend truth

Generated dashboards stay useful when they mirror backend state. If the dashboard looks more confident than the runtime state, report it.

Runtime Sanity

Check the normal surfaces you already trust:

• active lane or mode
• reason text
• gate status
• configured outputs
• unavailable configured entities
• diagnostics warnings

Normal user validation works through ordinary runtime surfaces. Keep safety and emergency scenarios real-world safe; diagnostics and reason text are the right support path for concerns.

Diagnostics

If anything looks wrong, download native Home Assistant diagnostics before making lots of changes. Diagnostics preserve the useful support snapshot:

• versions
• configured entities
• active lane/mode
• reason text
• gates
• output state
• generated card summary
• unavailable or unknown configured entities

See Diagnostics and Support Bundle.

Local HI-Only Snapshots

Advanced maintainers may use HI's package-local snapshot support where available.

Remember:

• it is local to the HI package
• it supports package-level validation and rollback preparation
• Home Assistant backups remain the right tool for whole-instance protection
• HACS continues to own HACS-managed updates
• restore work remains an explicit maintainer action

When To Open An Issue

Open an issue if:

• the integration fails to load after restart
• expected HI entities are missing
• generated cards contain unresolved placeholders
• the dashboard contradicts backend reason text
• HACS/Home Assistant version state stays inconsistent after refresh/restart
• diagnostics show unavailable configured entities that need explanation

Include the native diagnostics file whenever practical.