Aircon Cannot Turn on
A dead aircon could be a tripped isolator, a failed capacitor, or a locked-out control board. The difference between a five-minute fix and a major repair depends on where the power path breaks.
Why this happens
A quick summary of the most likely causes and what to look out for.
| Possible cause | What happens | Severity |
|---|---|---|
| Power-Supply Path Interruption | Power loss can prevent any startup response. | Needs assessment |
| Command-Link or Handoff Failure | Command-link issues can block startup even when standby power is present. | Needs assessment |
| Control-Board or Protection Lock | Control-board or safety-lock behavior can stop startup. | Needs assessment |
1. Power-Supply Path Interruption
When upstream power is cut or unstable, the unit shows no lights, no beep, and no startup response.
Signs to look for
- No indicator light at all.
- No startup beep response.
- No indoor or outdoor startup sound.
How to tell this is the cause
Unlike command-link failure, there is no indicator light at all.
What the repair involves
We trace power from the DB board through the isolator and terminal block to find where the supply drops out. Once located, we restore or replace the failed point.
Replacing boards before checking the power path adds avoidable cost.
2. Command-Link or Handoff Failure
Standby power reaches the unit, but a corrupted signal on the communication wire between indoor and outdoor sides blocks the start sequence.
Signs to look for
- Standby indication exists but no cooling cycle starts.
- Response is on-and-off across attempts.
- Behavior changes without a stable pattern.
How to tell this is the cause
Unlike power-path interruption, standby indication exists but no cooling cycle starts.
What the repair involves
We check the communication wire voltage, sensor readings, and indoor-outdoor handshake sequence to isolate the break point.
Assuming remote failure alone delays deeper control-path checks.
3. Control-Board or Protection Lock
Safety logic blocks startup when earlier fault conditions stay active — a prior overcurrent or sensor fault triggers a lockout that persists across power cycles.
Signs to look for
- Unit appears alive but startup does not complete.
- Short startup attempt then immediate stop.
- No sustained cycle despite repeated commands.
How to tell this is the cause
Unlike command-link failure, the unit appears alive but startup does not complete.
What the repair involves
We read the board fault memory, clear the protection lock if safe, and verify the original trigger is resolved before allowing normal restart.
Forcing repeated startups hides the pattern data needed for accurate checks.
Other Possible Causes
Timer, sleep, or grouped settings block startup on purpose — it feels like hard failure, but control logic is simply overriding your command.
How to tell this is the cause
- No-start appears at similar times instead of fully random intervals.
- Other units respond while one specific unit stays blocked.
- Behavior began after app or scene setting changes.
If this is the case we will tell you before recommending hardware repair.
Help Us Diagnose Faster
Just observe, no opening needed:
What to check before calling
| Check | Look for |
|---|---|
| Indicator status | on / off / on-and-off |
| Startup response | beep / click / brief attempt / no response |
| Breaker behavior | stable / trip-on-start / random trip |
| Timing pattern | constant no-start / on-and-off no-start windows |
Cases like this
Related Reading
Guides, troubleshooting, and diagnostic case studies to help you make informed decisions.
Same situation with your aircon?
Tell us the symptom and the unit type. We’ll help you figure out what’s going on.
WhatsApp us