Code appears after cleaning
The cooktop was sprayed or wiped down, then the code showed up when you tried to use it.
Start here: Dry the glass and control area thoroughly and give the unit a longer power-off reset before assuming a bad part.
Direct answer: A Miele cooktop showing F31 or FE31 is usually dealing with a touch-control or internal electronics fault, often triggered by moisture on the panel, a stuck key area, or a control that did not recover after a power glitch.
Most likely: The most common homeowner-fix path is to fully shut power off at the breaker, dry the glass and control area completely, then restart and check whether one touch key is acting stuck or unresponsive.
Start with the simple outside checks before opening anything. On touch-control cooktops, a wet surface, cleaner residue, a pan sitting over the control area, or a short power interruption can all throw a code that looks worse than it is. Reality check: if the code clears after a long power reset and stays gone, you probably did not have a failed part. Common wrong move: wiping the panel quickly and turning power right back on before trapped moisture has actually dried out.
Don’t start with: Do not start by ordering a cooktop control board just because the code came back once. These faults are often caused by moisture, residue, or a temporary lockup first.
The cooktop was sprayed or wiped down, then the code showed up when you tried to use it.
Start here: Dry the glass and control area thoroughly and give the unit a longer power-off reset before assuming a bad part.
Liquid ran across the glass, near the touch keys, or around the burner area before the fault started.
Start here: Let the surface cool, clean up the spill, and focus on moisture or residue affecting the touch controls first.
You shut power off and back on, but the code returns immediately or within a minute.
Start here: Look for a stuck touch area, damaged glass over the control zone, or a failed cooktop control panel or cooktop control board.
Some controls respond, others do not, or the unit beeps as if a button is being pressed constantly.
Start here: Treat that like a touch-control fault first, not a burner problem.
This is the most common real-world trigger after cleaning, steam, or a spill. The control reads a wet or contaminated surface like a finger that never lifted.
Quick check: With power off, dry the glass completely, especially around the control markings and edges, then wait before restoring power.
Touch cooktops can fault when something rests on the control area or when greasy film bridges the touch points.
Quick check: Remove everything from the top and clean the control area with a barely damp cloth followed by a dry cloth.
If one key area does not respond correctly, beeps on its own, or the code returns immediately after a proper reset, the touch interface itself becomes more likely.
Quick check: After reset, try each control area one at a time. A dead, always-on, or erratic key points toward the cooktop control panel.
When the surface is dry, nothing is sitting on the controls, and the code comes back instantly, the main electronics may not be processing the touch inputs correctly.
Quick check: If the breaker reset changes nothing and the behavior is exactly the same every time, the cooktop control board moves up the list.
These codes are commonly caused by something simple on the glass, especially after cleaning, steam, or a spill.
Next move: If the code does not return after the surface is dry and clear, the problem was likely moisture, residue, or something sitting on the controls. If the code is still present or comes back as soon as power is restored, move to a full power reset.
What to conclude: A cooktop that recovers here usually does not need parts.
Touch-control cooktops often need a longer power-down to clear a locked-up control state. A fast breaker flip usually is not enough.
Next move: If the code clears and the cooktop starts normally, watch it through a few uses before buying anything. If the code returns immediately or within the first minute, the issue is probably not just a temporary glitch.
What to conclude: A reset that holds points to a one-time control lockup or moisture event. A reset that fails points toward a stuck touch area or failed electronics.
F31 and FE31 are more often tied to the control side than to the heating elements. You want to separate a bad touch input from a deeper board fault.
Next move: If all keys respond normally and the code stays gone, keep using the cooktop and monitor it. If one touch area is clearly erratic or dead, the cooktop control panel is the strongest part-failure suspect.
This is the point where the two most likely repair paths separate, and it keeps you from guessing at parts.
Next move: If the symptoms clearly match one of those two patterns, you have a reasonable next step instead of replacing random parts. If the symptoms are mixed, intermittent, or changed after a spill inside the unit, professional diagnosis is the safer move.
Once the simple causes are ruled out, this is either a control replacement job or a clean stop point for service.
A good result: If the cooktop powers up cleanly and all keys respond normally without the code returning, the repair path was correct.
If not: If the code remains after the suspected part is replaced, stop and get model-specific service diagnosis rather than stacking more parts.
What to conclude: A successful repair confirms the failed control component. A failed repair usually means the fault was misidentified or there is deeper electronic damage.
Repair Riot may earn a commission from qualifying purchases, at no extra cost to you.
In plain terms, it usually means the cooktop is seeing a control-side problem. The most common causes are moisture, residue, a stuck touch area, or a failed control component.
Yes. That is one of the first things to suspect. A wet control area, trapped moisture at the glass edge, or cleaner residue can make the cooktop think a touch key is being pressed continuously.
Sometimes. A proper reset can clear a locked-up control after a power glitch or moisture event. If the code comes right back after a full reset and a dry surface, the problem is more likely a failed control panel or control board.
Usually no. F31 and FE31 are more consistent with the control side of the cooktop than with a surface heating element. If one burner is not heating but there is no control fault, that is a different diagnosis.
Not first. Start by drying the surface, clearing the control area, and doing a real breaker reset. If one touch area is clearly the problem, the cooktop control panel is often the better first part. If the whole interface is unstable, the cooktop control board becomes more likely.
Call for service if the breaker trips, the glass is damaged, liquid likely got inside the unit, or the code stays after one careful repair attempt. That is where guessing gets expensive.