Humidity Intelligence v2.0.12 — Manual handover and Home Assistant 2026.9 compatibility

Manual control: a smoother handover

Previously, switching Manual on could return ordinary outputs to their default or off
state as HI handed control back. Now, HI cancels its pending ordinary work and leaves
those devices as they are, ready for you to control.

The reason panel explains what Manual means, and humidifier status follows what Home
Assistant actually observes. When you're ready for HI to take over again, switch
Manual off to return to AUTO.

Use Manual when you want to take control yourself. AUTO continues to manage your
configured outputs; this update does not add a temporary manual override while AUTO
is still enabled.

Configured CO emergency ventilation remains the sole ventilation exception while
Manual is active. Certified carbon-monoxide alarms remain your primary detection and
alerting system.

A few improvements behind the scenes

These changes help HI work more consistently with Home Assistant, without changing
your existing entity IDs, service names or control priorities.

• Time gates follow your Home Assistant clock. If you've set an allowed time
  window, HI now uses Home Assistant's local time rather than the computer or container
  clock underneath it. Windows crossing midnight and daylight-saving changes keep
  their intended boundaries.
• Timers leave less unfinished work behind. Replacing, cancelling or removing a
  timer clears its old callbacks. Remaining time refreshes at most once per minute,
  and a pause countdown update alone won't make HI run through its control decision
  again.
• Setup suggestions understand child devices better. On Home Assistant 2026.9,
  a child device without its own Area can use its immediate parent's Area for setup
  suggestions. Your chosen mappings still take priority. Missing or ambiguous parent
  information won't result in an invented Area assignment.
• The support tools stay familiar. Native diagnostics keep schema 1 and the
  existing privacy protections, with added context for Manual control. The familiar
  v205_release_check service now supports v2.0.12.

Easier to find your way around

The README now has expandable sections, so you can open the guidance you need. The
website, Wiki and support notes have been brought into line.

Validation

The exact final package was checked after startup for its loaded version, integration
setup, entities, services, diagnostics and release checks. Repository tests and
main-branch CI cover the code changes.

The Manual runtime observations were carried out on the exact beta.4 package. Those
observations are separate from the final-package registration checks; they are not
independent physical measurements, and CO was not live-actuated.

A note from Senyo

A personal thank you to @Dorikumi for raising the
'manual control' concern in issue #114
and bringing it to my attention. It prompted a closer look at how HI hands control
back, and the Manual mode function is now repaired.

When you choose to take control of a device, the handover now releases authority over to you.
I have also made other improvements to help maintain everyday reliability.
Thank you to everyone taking the time to report problems and share how HI works in
your home. your continuous efforts help make the project better.

Senyo

Install or update

Ready to get started? Humidity Intelligence is available in the HACS default
integration repository. The button opens its HACS page; installation and restart
remain in your hands.

1. New to HI? Select Download. Already using it? Select Update when offered.
2. Fully restart Home Assistant and wait for startup to finish.
3. New users: go to Settings → Devices & services → Add integration →
   Humidity Intelligence and complete setup. Existing users keep their configuration.
4. Confirm HI has loaded and its entities and services are available. Use the
   loaded-version checks in the Wiki
   rather than relying only on the manifest saved on disk.

You don't need to re-export your Manual cards or migrate configuration/data for
v2.0.12. Generated-card source bytes are unchanged. If you're upgrading from before
v2.0.9 and use external tools that read HI's exported files, follow the
owned-directory migration guidance.

In the observed beta.4-to-Stable update, the exact final v2.0.12 package registered
after one completed restart. The two restarts used during beta validation were
part of that candidate procedure, not a permanent Stable installation rule. This
result isn't a guarantee for every starting version or installation method.

If HI hasn't registered correctly, check setup errors and duplicate-domain discovery
before restarting again. Keep rollback copies outside custom_components.