Getting Help
Most Humidity Intelligence support is easier when the issue starts with the right context. A useful report simply shows what changed, what Home Assistant is seeing, and what Humidity Intelligence is saying about its own state.
Open a GitHub issue from the Humidity Intelligence repository:
Open Humidity Intelligence issues
Pick the template that best matches the problem:
- bug report
- configuration help
- feature request
- UI gallery submission
If you are choosing between templates, configuration help or bug report is a good starting point. The maintainer can reroute it after triage.
Include these whenever practical:
- Humidity Intelligence version
- Home Assistant version
- HACS install or manual install
- affected area: runtime, config flow, generated dashboard, services, diagnostics, documentation, HACS/install, or release/governance
- what you expected to happen
- what actually happened
- whether this started after an update, reinstall, restart, or config change
- screenshots with private data removed
- downloaded Home Assistant diagnostics when available
Keep secrets, access tokens, internal URLs, addresses, device IDs, and private telemetry out of public issue text.
For most runtime, configuration, generated dashboard, HACS, and support issues, the most useful attachment is the native Home Assistant diagnostics file for Humidity Intelligence.
See Diagnostics and Support Bundle for the exact download path.
A useful issue usually looks like this:
Version: Humidity Intelligence x.y.z
Home Assistant: 2026.x
Install path: HACS
Affected area: Generated UI/dashboard
What happened:
The generated mobile dashboard still shows the older output detail layout after I
changed the output details option.
What I tried:
- restarted Home Assistant
- ran the dashboard export service
- checked that the configured entities are available
Diagnostics:
Attached native Home Assistant diagnostics download.
Use sanitized entity examples if needed:
sensor.example_room_humidity
switch.example_fan
binary_sensor.example_gate
The most helpful reports keep the evidence clean:
- sanitize secrets, tokens, and private dashboard details
- separate generated dashboard symptoms from runtime-control symptoms
- separate HACS update visibility from release availability
- keep one symptom in one issue where practical
Issue labels, priority, and next steps are manual maintainer decisions. Community comments and reactions are useful interest signals; maintainer review and the release process carry approval and scheduling authority.
| Previous | Next |
|---|---|
| Home | Diagnostics and Support Bundle |