Field Actions
DISPATCHAlways disconnect appliance from 230V/400V mains before opening panels. Use CAT III multimeter for circuit testing.
Frequently Asked Questions: LG ER RT
FAQ TREEWhat does error code ER RT mean on a LG appliance?
LG error code ER RT indicates: On LG Refrigerator: Room temperature sensor failure (ambient temperature detection problem) / ABNORMAL AMBIENT SENSOR.
What is the root cause of LG error code ER RT?
The primary root cause for LG code ER RT is: On LG Refrigerator: Room temperature sensor disconnection or short circuit. Ambient Sensor short&open circuit..
How do I fix or resolve LG error code ER RT?
To resolve error code ER RT: On LG Refrigerator: Unplug the appliance and wait for 20 seconds, then restart. Check if the connector at the PCB or at the hinge is removed or loose, then re-insert. Check if the connector measures out of 5 ~ 400 kilo-ohm range (normal is 13 kilo-ohm at 20 degrees Celsius). Replace the assemblies if the problem is not solved.
Is it safe to clear LG error code ER RT by resetting power?
Resetting power (unplugging for 5–10 minutes) clears temporary memory errors. However, if LG code ER RT persists, the physical component causing On LG Refrigerator: Room temperature sensor disconnection or short circuit. Ambient Sensor short&open circuit. must be inspected or replaced.
How do I test electrical resistance for LG code ER RT using a multimeter?
Set a digital multimeter to ohms (Ω). Disconnect power and test NTC Temperature Sensor Probe (Thermistor) across Across sensor pins 1-2 (unplugged harness). Expected nominal reading is 4.8kΩ–12kΩ (at 20°C–25°C). Tolerance: Negative temperature coefficient: resistance drops smoothly when warmed with fingers. OL = open circuit..
What safety protocol must be followed before servicing LG code ER RT?
Standard electrical safety protocol: 1. Disconnect 230V mains power before opening panels. 2. Verify zero voltage at test points. 3. Allow hot water or heating elements to cool below 30°C before handling.
Community Verification
COMMUNITYDid this solution resolve the issue?



