Does Apple Home support Matter commissioning using concatenated / multi-device QR codes?

Question

Created 2w

Replies 1

Boosts 0

Participants 2

Hi,

I’m developing a Matter commissioning flow and would like to clarify Apple Home’s support for concatenated (multi-device) QR codes.

In my implementation, I generate a single QR code that contains multiple Matter onboarding payloads (concatenated payloads), intended to commission multiple devices in one scan, similar to a multi-pack / multi-accessory flow.

What I’ve tested:

Standard single-device Matter QR codes work as expected in the Apple Home app

A concatenated QR code (multiple Matter payloads combined into one QR) does not get recognized / commissioned by Apple Home

My questions:

Does Apple Home officially support commissioning via concatenated or multi-device Matter QR codes?

If yes, is there a specific payload format or delimiter that Apple Home expects?

If not, is this a known limitation or something planned for future iOS/Home releases?

Boost

Answer 1

DTS Engineer OP

Apple

2w

Does Apple Home officially support commissioning via concatenated or multi-device Matter QR codes?

We haven't said anything about this officially, but that's because we haven't really said anything all that specific about what parts of Matter HomeKit support. Informally, no, I don't think this works, as support for concatenated payloads was only supported in the Matter project relatively recently (~September 2025).

https://github.com/project-chip/connectedhomeip/pull/40951

HomeKit's Matter support is built on top of that project, so nothing would have really happened before that work was first finished.

If yes, is there a specific payload format or delimiter that Apple Home expects?

The only format we'd support is the format defined in the Matter specification. See section "5.1.6. Concatenation" of the Matter Core Specification.

If not, is this a known limitation or something planned for future iOS/Home releases?

I can't discuss our future plans, but my recommendation would be to file a bug asking us to support this and then posting the bug number. As part of that, please include the details of exactly what you're trying to implement and why this is required, as that context is what's most critical when the engineering team is deciding where to focus their efforts.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0