Why Is My Aircon Not Responding To The App Or WiFi?
When app commands do nothing, the break can sit in the phone session, the WiFi adapter, or the unit's cooling circuit. Each layer fails differently, and the fix depends on which one actually dropped.
1. App Or Network Session Issue
How This Works
App control depends on several links: the phone app talks to the brand cloud, the cloud relays the command, and the local network passes it to the WiFi adapter in the indoor unit. Any one of these can drop without affecting the unit itself.
How To Tell
If the app stops working but the remote still controls the unit normally, the break sits in the network or cloud layer. Unlike a WiFi module fault, the adapter typically still appears online in your router's device list. Unlike a cooling-path fault, the unit responds correctly to remote commands.
- App shows sent command but no unit response.
- Remote control still works normally.
- Issue appears after network or phone changes.
How We'd Confirm It
We confirm the command path layer by layer: app login, cloud connection, local network reach, then restore the break point without touching unit hardware.
Do not replace unit parts before the app, cloud, and network path is checked. The break is almost always above the unit, not inside it.
2. WiFi Module Or Communication Path Fault
How This Works
The WiFi adapter, built into the indoor PCB or plugged into a dedicated port, talks to both the router and the indoor board. When the module degrades, it may connect briefly after a power cycle then lose the link under normal load. The app shows the device online, sends a command, gets no response, then shows offline.
How To Tell
A failing module connects briefly then drops again. Unlike an app session issue, the adapter cannot hold a stable link with the router even when no commands are being sent. Unlike a cooling-path fault, the unit shows no acknowledgement at all because the command never reaches the board.
- Device appears offline often.
- Reconnection works briefly then drops again.
- Command delays are inconsistent across attempts.
How We'd Confirm It
We test module signal strength and check adapter seating on the indoor PCB. Then we verify the module holds connection through a full power cycle before recommending replacement.
Do not re-pair repeatedly without checking module signal strength. The connection will keep dropping under load even if it pairs cleanly, and each re-pair masks the underlying instability.
3. Command Accepted But Cooling Path Fails
How This Works
When the communication path works, the indoor unit receives the command, acknowledges it with a beep or display change, and attempts to execute it. If cooling then fails to start, or starts briefly and stops, the problem has shifted from the communication layer to the cooling circuit itself.
How To Tell
If the indoor unit beeps or the display changes when an app command is sent, communication is intact. The break is in the cooling circuit, not the WiFi path. Unlike app session and module faults, the unit acknowledges the command before failing. The next diagnostic is the outdoor unit's behaviour.
- Indoor unit beeps or display changes after app command.
- Cooling does not start or cuts off soon after.
- Flashing light or outdoor no-start pattern may appear.
How We'd Confirm It
Once we confirm the unit receives the command, we shift to cooling-path diagnosis: outdoor startup, refrigerant circuit, and error codes, separately from the app layer.
Do not retry the command repeatedly through the app. The unit is receiving it; further attempts will not change a hardware fault, and may trigger a protection lockout if a refrigerant fault is active.
Related Reading
Ready to Get Started?
Tell us what’s going on. Symptoms, setup, photos, anything we should know. We’ll assess and come back with the right next step.