Faikin Ninja — Pairing and Network Guide
Faikin Australia
Getting a Faikin Ninja (P1P2 for Daikin, X-Y for Mitsubishi Heavy) onto your WiFi and into Apple Home, Google Home or Home Assistant, including re-pairing after a reset.
All control is local · no cloud, no account · the same codes on your module's sticker work for life.
On this page
- 1. Read the LED first
- 2. Which code to use: Matter vs HomeKit
- 3. Network requirements checklist
- 4. Do you need a hub?
- 5. Re-pairing after a reset
- 6. After pairing: the web dashboard
- 7. Troubleshooting
1. Read the LED first
The LED at power-up tells you which setup path your module uses. Check it before anything else.
| LED at power-up | Meaning | What to do |
|---|---|---|
| Fast blue flash, then fast red flash | WiFi pairing mode. The module is broadcasting its own network, named FaikinAC followed by four characters. | Join that network from your phone and the setup page opens. Enter your home WiFi name and password. |
| Slow blue flash (about once a second) | Matter / HomeKit Bluetooth pairing mode. It joins your WiFi as part of the pairing. | Pair from a smart-home app using the Matter code on the sticker. See sections 2 and 4. |
The newest modules do both: they broadcast the FaikinAC setup network and accept Bluetooth pairing, so either path works.
2. Which code to use: Matter vs HomeKit
Your module's sticker can carry two pairing codes. They are not the same thing.
- The Matter code (11 digits) always works. The module advertises Matter over Bluetooth out of the box. Use this one first, in the Apple Home app, Google Home app, or any Matter app.
- The HomeKit code (8 digits) only works when HomeKit is switched on in the module's own settings (Setup > Others > Homekit), and it is off by default. After a factory reset it is off again. If both codes seem to fail, this is usually why the HomeKit one does.
Recommended order: pair with the Matter code first. Once the module is on your WiFi, you can switch HomeKit on from its web page if you prefer the native HomeKit connection.
3. Network requirements checklist
Before pairing, make sure of the following. These cover the great majority of failed or timed-out pairings.
| Requirement | Must / recommended | Detail |
|---|---|---|
| Bluetooth on, phone near the module | Must | Pairing starts over Bluetooth. Stand within a few metres. |
| Phone joined to the WiFi you want the module on | Must | The pairing passes that network's name and password to the module. |
| The WiFi name broadcasts on 2.4GHz | Must | A combined 2.4/5GHz network is fine, and your phone can be on the 5GHz side. A 5GHz-only network will not work. |
| Security WPA2, or mixed WPA2/WPA3 | Must | Pure WPA3-only networks do not work. Mixed (transition) mode is fine. |
| IPv6 enabled on the router | Must | Matter requires it. It is on by default on most home routers. |
| No client or AP isolation on the WiFi | Must | Devices on the network must be able to see each other. Guest networks commonly have isolation on, so avoid pairing onto a guest network. |
| One VLAN while pairing | Must (if you run VLANs) | Put your phone, the module and any hub on the same VLAN or subnet while pairing. |
| VPN off on your phone | Recommended | Phone VPNs and private relays can break local discovery during pairing. |
| Hub powered, same WiFi, up to date | Recommended | If you use an Apple TV, HomePod or Google hub, have it on and updated before you start. |
| Location services on | Recommended (Android only) | Android needs it for Bluetooth scanning. |
4. Do you need a hub?
Matter needs a controller in your home. Whether you need to buy one depends on your ecosystem, and you may already own one without knowing.
Apple Home
An iPhone or iPad on iOS 18 or newer pairs the module and controls it on its own while you are at home, no extra hardware needed. An Apple TV or HomePod (any model) adds control when you are away from home and rock-solid day-to-day operation, so use one if you have one.
Google Home
Google requires a physical Google hub, the app will not complete pairing without one on your account. Any of these works: Google TV Streamer (4K), Nest Hub (1st or 2nd gen), Nest Hub Max, Nest Wifi Pro, Nest Audio, Nest Mini, Google Home or Google Home Max. An Android phone on its own cannot do it.
Hubs you may already own
- Many newer Samsung TVs, Smart Monitors and Family Hub fridges contain a SmartThings hub. Pair through the free SmartThings app.
- Amazon Echo speakers from about the 3rd generation onward are Matter controllers. Pair through the free Alexa app.
- A Home Assistant server (even on an old PC) has a Matter controller built in, and also finds the module over MQTT with no Matter involved at all.
Strictly Android household with none of the above? Contact us and we will walk you through the options.
5. Re-pairing after a reset
A factory reset clears the module's pairings but not its identity. The codes on the sticker are permanent, it is simply a fresh start.
- Remove the old accessory from the app first. Open Apple Home or Google Home and delete the module's old entry, including any half-added ones. A reset module will time out against a stale entry every time, and this is the most common cause of failed re-pairing.
- Run the checklist in section 3.
- Pair again with the Matter code. Remember the HomeKit switch is off again after a reset, so the 8-digit HomeKit code will not work until you re-enable it from the web page.
6. After pairing: the web dashboard
The moment the module is on your WiFi it has its own local control page, independent of any smart-home app.
- Browse to http://faikinac-xxxx.local, where xxxx is the four-character code on the module's sticker.
- If .local does not load, open your router's admin page or app, find the device list, and note the IP address next to FaikinAC-xxxx (something like 192.168.1.57). Browse to that IP instead.
- Bookmark it, or use your phone browser's Add to Home Screen, and it opens like an app from then on.
The page works from any device on your network, Android, iPhone, Windows or Mac, and never needs the internet. Home Assistant users can also connect over MQTT, set up from the module's Setup page.
7. Troubleshooting
| Symptom | Likely cause and fix |
|---|---|
| Pairing times out on a previously-paired module | Stale entry in the app. Remove the old accessory from Apple Home / Google Home and try again. |
| Both codes fail | The HomeKit code is expected to fail while the HomeKit switch is off (the default). Use the Matter code. |
| Google Home refuses to start pairing | No Google hub on the account. See section 4. |
| QR will not scan | Type the code manually: in Apple Home choose More options, then set up without a code. |
| Times out on a fresh module with everything correct | Usually the network: isolation on the WiFi, WPA3-only security, IPv6 off, or a router that blocks discovery traffic (some UniFi setups are known for this). Work through section 3, or tell us your router model. |
| No FaikinAC network appears | Check the LED. Slow blue means it is a Bluetooth-pairing unit, so use the Matter code instead of looking for the network. |
| Paired, but the aircon will not respond to commands | Open the module's web page and check Setup > Activation Code is present. Reading works without it, control does not. |
Applies to the Faikin Ninja P1P2 (Daikin) and Faikin Ninja X-Y (Mitsubishi Heavy Industries). Need a hand? Contact us with your module's four-character code and a photo of the LED, or join the Faikin Australia WhatsApp channel.
