CookGauge

Model first

Read the controller before you read the code

An error label is not universal. Record the exact display, brand, controller family, model, and point in the cook before using a troubleshooting path.

Capture these details before resetting

  1. Exact code, spelling, punctuation, and whether it stays on screen.
  2. Brand, full model name, controller or app family, and serial number if available.
  3. Whether it appeared at startup, during preheat, while cooking, or during shutdown.
  4. What the cooker did: continued running, cooled down, stopped feeding, or began shutdown.

Traeger

Match the controller family

Traeger documents different error displays across non-WiFIRE, WiFIRE and newer controller families. For example, LEr is documented for certain non-WiFIRE three-digit controllers, while low-temperature and failed-ignition messages appear differently on newer families. Use the official article that lists your model before following a procedure.

Open the Traeger owner hub

Traeger examples

Verified codes, still model-limited

These are documented Traeger examples, not a universal decoder. Match the displayed code and controller family against the linked official article before acting.

LEr

Low Error Reading

Documented for certain non-WiFIRE grills with three-digit digital controllers. It follows a sustained low-temperature condition and shutdown.

Shutdown path
0002
ER02

Low Temp Error

Documented on applicable WiFIRE families. The official procedure varies by model and may include a re-ignition or shutdown sequence.

Low-heat path
0007
ER07

Failed to Ignite

Documented across several newer display families. Treat it as a fire-pot, fuel, airflow, ignition, or power path — not an automatic part order.

Ignition path
ERR
ER1–ER4
ER06

Sensor or connection family

These labels appear on specific controller families and can involve an RTD, thermocouple, connection, or fan. The exact manual decides the next step.

Probe path

Pit Boss

Separate a real error from a startup display

Pit Boss directs owners to the manual for their exact grill when an error appears. Its FAQ also notes that a brief code shown immediately after plugging in can be a programming code rather than a fault. Do not treat a disappearing startup display as a repair diagnosis.

Open the Pit Boss owner hub

Use the symptom when the code is unclear

If the display does not map cleanly to a verified manual, use the observable symptom and stop conditions rather than guessing. A no-ignite path, low-heat path, probe-reading path, or shutdown path gives the next safe check without assuming part compatibility.

A code narrows the question; it does not name the failed part

When the model and controller are not confirmed, write down the cook stage and the observable behavior first. A no-ignite event, repeated shutdown, weak heat, or implausible sensor reading has a safer next path than an online search for the code alone.

How to use the code references

The examples on this page retain their published controller limits. They do not transfer a meaning, reset procedure, firmware behavior, or part number to another brand or another controller generation.

Sources consulted