Does the Aqara FP300 QR code contain the IEEE Address and Install Code?

Developer Hub
, ,
1

Hello Aqara team,

I am integrating the Aqara FP300 with a third-party Zigbee coordinator and would like to understand its commissioning process.

I noticed that some FP300 devices have a QR code that contains information such as the IEEE address and the Install Code, while others appear to have a different QR code format.

Could you please clarify the following?

  1. Does every Aqara FP300 have a Zigbee Install Code?
  2. Does every FP300 have a QR code containing the IEEE (EUI-64) address and Install Code?
  3. If not, is there another way to obtain the IEEE address and Install Code for Zigbee Install Code commissioning?
  4. Is the Install Code available through the Aqara app or any developer tool?

I am asking because I need the IEEE address and Install Code to add the device to a third-party Zigbee Trust Center using Install Code-based joining.

Thank you.

2 Likes
2

Hi. Unfortunately, I cannot answer your first two questions, but I can share some insights on the other two:

Regarding the IEEE address, I suspect that the “Accessory ID” (which can be found in the Aqara Home app under “Device Information”) might correspond to it, though I am not 100% sure.

Furthermore, if you use the Aqara developer API, you can query the DID (Device ID). For many Aqara Zigbee devices, this DID actually contains the IEEE address directly.

Whether using the Aqara Home app or the API, the sensor must first be connected via an Aqara Hub.

Another easy way to retrieve it is by temporarily pairing the sensor to a more open system first. For example, I have integrated one of these sensors via Zigbee2MQTT in Home Assistant, and the IEEE address is clearly visible in the frontend once joined. Keep in mind, though, that while this gives you the IEEE address, no coordinator will be able to extract the Install Code over the air.

I am not aware of any Aqara app or public developer API that exposes the Zigbee Install Code. By design, the Install Code is an out-of-band secret used for secure commissioning and is normally supplied physically with the device, typically via a QR code or a label.

If the QR code supplied with your specific FP300 cannot be parsed by your Trust Center, you aren’t necessarily out of luck. The issue is often a format or parser mismatch rather than a missing code. For instance, systems like Home Assistant (ZHA) had to explicitly add software support to parse Aqara’s specific QR code formats. It might be worth checking if your particular coordinator or software requires an update or a custom parser to properly read Aqara’s QR format.

Please keep in mind that the FP300 can be operated in either Zigbee or Thread mode. Therefore, the alternative format you are seeing might actually be a Matter QR code intended for Thread mode.

2 Likes
3

Yes it does, for Zigbee devices it’s the IEEE address and for IP based devices it’s the MAC address.

And for IP devices you can get the full DID including lumiX. prefix through an mDNS query.

2 Likes
4

Okay, that makes sense. I was just a bit confused because I noticed a different “Accessory ID” in Zigbee mode compared to its MAC address in Thread mode. But I assume the MAC / Accessory ID / IEEE address is simply tied to the respective network interface and differs depending on which mode is currently active.

1 Like
5

That’s my understanding. For dual protocol devices they’re essentially treated as different devices depending on which firmware is installed.

1 Like
6

Okay, it’s kind of confusing in Thread mode in the Aqara app.

The Accessory ID I get is matt.27d9584e2ad3deb1c1432000, and under “Network,” the MAC address is 4E:F4:CB:53:DF:14:3B:43.

Is the Zigbee IEEE address used “matter.” Accessory ID? :confused:

1 Like
7

Not sure about matter/thread devices, only looked into zigbee and IPv4 devices.

2 Likes