Skip to main content
WhatsApp

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.

SAFETY WARNING

Stop using the unit and contact a technician if you notice burning or electrical smell, repeated breaker trips on startup attempts, sparking or crackling near any unit, or water near live electrical points.

Power-Supply Path Interruption

If upstream power is cut or unstable, the unit may show no lights, no beep, and no startup response.

  • No indicator light at all.
  • No startup beep response.
  • No indoor or outdoor startup sound.

We trace power from the DB board through the isolator and terminal block to find where the supply drops out, then restore or replace the failed point. Replacing boards before checking the power path can add avoidable cost.

Command-Link or Handoff Failure

The unit can have standby power but still fail to start when the communication wire between indoor and outdoor units carries a corrupted signal.

  • Standby indication exists but no cooling cycle starts.
  • Response is on-and-off across attempts.
  • Behavior changes without a stable pattern.

We check the communication wire voltage, sensor readings, and indoor-outdoor handshake sequence to isolate the break point. Assuming remote failure alone can delay deeper control-path checks.

Control-Board or Protection Lock

Safety logic can block startup when earlier fault conditions stay active. A prior overcurrent or sensor fault may have triggered a lockout that persists across power cycles.

  • Unit appears alive but startup does not complete.
  • Short startup attempt then immediate stop.
  • No sustained cycle despite repeated commands.

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 can hide the pattern data needed for accurate checks.

Other Possible Causes

Timer, sleep, or grouped settings can block startup on purpose. It feels like hard failure, but control logic is overriding your command.

How to Tell

  • 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:

  • 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

Same situation with your aircon?

Describe what’s happening. We’ll work out the likely cause and tell you the right next step.

WhatsApp us