1. Verify the exact model or documented family
We first confirm the model number against a manufacturer product page, owner manual, or official support library. Similar-looking machines and neighboring model numbers are not treated as interchangeable. Family-level guidance is used only when the manufacturer explicitly groups that exact model into the documented family.
2. Classify how the machine actually humidifies
Ultrasonic, evaporative, and hybrid machines behave differently. A no-visible-mist complaint can be normal on an evaporative unit and a real symptom on an ultrasonic unit. That technology check happens before we choose a troubleshooting path.
3. Attach the diagnosis to the source that supports it
A model can have several official sources, but an issue guide should point readers to the manual, FAQ, or support page that actually supports that symptom. We reorganize manufacturer guidance for faster diagnosis; we do not invent service codes, reset combinations, or hidden procedures.
4. Resolve conflicts between official pages
Manufacturer help centers, product listings, and older manuals can disagree after revisions. When that happens, we prefer the exact-model manual or the most specific current support article, record the discrepancy during review, and avoid publishing a universal reset or code meaning until the revision is clear. An official source conflict is a reason to narrow the claim—not to average the instructions together.
5. Use cross-model hubs for comparison—not generic fixes
Broad pages such as “no mist” are comparison indexes. They show why the same symptom has different meanings across models and then route the reader into an exact-model guide.
6. Keep evidence gaps visible
If we can verify a model but not a symptom-specific path, we leave that path unpublished rather than filling the site with a cloned checklist. Coverage grows only when the evidence gate is met.
7. Stop at the consumer-safe boundary
We cover controls, settings, removable parts, manufacturer cleaning procedures, filters/wicks, water level, tank seating, app pairing, and other user-accessible checks. We stop before undocumented internal electrical work or bypassing safety controls.
8. Separate normal behavior from real faults
We explicitly record whether a model should create visible mist and whether controls such as a humidistat can intentionally stop the fan or mist. A “false problem” is useful search intent when the manufacturer documents the behavior as normal.
9. Decode indicators before calling them errors
A display state is not automatically a fault. We preserve the manufacturer’s distinction between maintenance reminders, low-water/refill states, control locks, humidity-range displays, and true sensor/error codes. The Code & Light Decoder is generated only from issue paths that pass the same model-specific evidence gate.
10. Re-review support that can change
Guides carry a reviewed date. Manufacturer support pages, manuals, app behavior, and model lineups can change, so pages that begin receiving search impressions should be rechecked against the primary source.