Recognize heater troubleshooting boundaries that require a licensed gas or electrical trade
domain: equipment-operations · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check water chemistry and flow first — scale buildup from persistently high LSI, a dirty filter, or low flow are common non-gas causes of heater fault codes and should be ruled out before assuming a heater hardware failure.
Perform only routine, non-gas, non-electrical maintenance within scope: clearing debris/vent obstructions, checking the flow switch's mechanical operation, reading displayed fault/error codes, and confirming adequate water flow.
Do not open, adjust, or repair anything on the gas supply line, gas valve, burner assembly, manifold, gas pressure, or venting/flue system.
Do not perform line-voltage electrical repairs on the heater's control board or wiring.
Document the fault code and observed symptoms, then refer the repair to a state-licensed gas fitter/plumber or electrician as required by local contractor licensing law.
Known gotchas
Attempting gas-side or line-voltage electrical repairs without the required trade license is both a licensing-law violation in most states and a genuine safety hazard (carbon monoxide exposure, gas leak, fire) — treat this as a hard boundary, not a judgment call based on comfort level.
Misdiagnosing a water-chemistry or flow problem as a 'heater failure' can trigger an unnecessary and costly trade-call — check chemistry and flow before referring out.
Scope boundaries for what a pool tech can touch on a heater vary somewhat by state licensing law — when uncertain, treat the more restrictive interpretation as the safe default.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?