Why is my aircon not responding to the app or WiFi?
When app commands do nothing, three very different faults look identical from your phone: the network or cloud session has dropped, the WiFi adapter cannot hold the link, or the unit took the command and failed to cool. What the remote does, and whether the unit beeps, tells them apart.
By Team Snowflake | Reviewed 30 May 2026
1. App or network session has dropped
You tap cool in the app and nothing happens, even though the phone says the command was sent. The remote still drives the unit normally. That means the cooling hardware is healthy and the break sits in the app, brand cloud, login session, router, or handoff to the WiFi adapter.
How to tell
This path fails only through the app. Unlike an adapter fault, the device stays visible on the network. Unlike a cooling fault, the remote makes the unit beep and cool normally. The failure sits above the aircon, usually in the account, cloud relay, or local network handoff.
- App shows the command sent but the unit does nothing.
- Remote control still drives the unit normally.
- The trouble started after a router change, app update, or new phone.
How we confirm it
We walk the command path one link at a time: app login, cloud connection, then local network reach to the adapter. We restore the link at whichever point it broke and confirm the app drives the unit again, without opening or replacing any unit hardware.
If anyone suggests swapping the indoor board or the adapter before the app login, cloud, and network path have been checked, push back. The break is almost always above the unit, and replacing parts will not fix a dropped session.
2. WiFi adapter cannot hold the link
The WiFi adapter, built onto the indoor PCB or plugged into a dedicated port, sits between your router and the indoor board. When it starts to fail, it connects right after a power cycle, then loses the link a short while later under normal running. The app shows the device online, you send a command, nothing comes back, and the device flips to offline.
How to tell
This path repeats after every re-pair. The adapter joins briefly, works for a moment, then drops offline again. Unlike a cloud-session issue, the adapter itself keeps leaving the router. Unlike a cooling fault, the indoor unit never beeps because the command never reaches the board.
- Device shows offline far more often than online.
- Reconnecting works for a moment, then drops on its own.
- Response delays come back different on each attempt.
How we confirm it
We measure the adapter's signal strength at the unit and check how it is seated on the indoor PCB. We then watch whether it holds the link through a full power cycle and a stretch of normal running before we recommend replacing it.
Avoid repeated re-pairing before signal strength and adapter seating are checked. Fresh pairing can hide an adapter that cannot hold the link.
3. Command accepted but cooling fails
You send a cool command from the app and the indoor unit beeps, the display flickers or jumps to a new temperature, and everything looks like it worked. Then no cold air comes, or it blows cool for a few seconds and stops. The beep proves the command got through; the fault has moved past the app and the link into the cooling circuit itself.
How to tell
This path starts with a successful command. Unlike app or adapter faults, the indoor unit beeps, updates the display, or opens the louvre. The failure comes after acknowledgement: no cold air, short cooling, outdoor non-start, or an error code. The next check is the cooling circuit, not WiFi.
- Indoor unit beeps or the display changes when you tap the app.
- Cold air never starts, or stops soon after it begins.
- A flashing light, error code, or silent outdoor unit shows up.
How we confirm it
Once the beep confirms the unit is receiving commands, we move off the app layer entirely and onto the cooling circuit: outdoor startup, compressor behaviour, refrigerant pressure, and any error code on the display.
Stop repeating app commands once the unit has acknowledged them. Further attempts do not fix the cooling fault and may trigger protection lockout.
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.