Matter OTA test with Alliance-issued Vendor ID

[keruhome]

Hi everyone.
We try to test Matter OTA use Google Developer Center documents as a reference.

I try to upload OTA image refered to Prepare an OTA image in step6(OTA) but I couldn't find "New Image" button.

My understanding New Image button is shown after registered Matter development device with Alliance-issued Vendor ID in Developer Console.
But to register Alliance-issued Vendor ID, we cannot use Testnet DCL and have to verify Vender ID via MainNet DCL.

Does this mean that there is a requirement to register Mainnet DCL and costs will be incorred for use it even if the device is under development?

I think when I use Mainnet DCL, we have to get PAA and paid some fee for get PAA.

We have Alliance-issued Vendor ID and Matter development device.

I've already reviewed the following topics.
https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/Testing-Matter-OTA-with-Google-Hom...

Please help for set OTA image uploading and verify Alliance-issued Vendor ID in Google developer console.
Many thanks.

 

- Prepare an OTA image
https://developers.home.google.com/matter/ota/configuration?authuser=1

- Verify a Vendor ID
https://developers.home.google.com/matter/integration/vid-verification?authuser=1

[jamesmartinsjte · Accepted solution]

It sounds like you’re referring to testing a Matter Over-the-Air (OTA) update using a vendor ID issued by the Connectivity Standards Alliance (CSA, formerly known as the Zigbee Alliance). This would be relevant for manufacturers or developers working with Matter, which is a standard for smart home devices.

For such a test, you'd typically need:

1. Vendor ID: Ensure you have your unique Vendor ID from the CSA.
2. Firmware: The firmware for your device should include the Matter protocol and be updated to handle OTA updates.
3. Testing Tools: Utilize tools and frameworks provided by the CSA for testing OTA updates.
4. Test Environment: A controlled environment to simulate OTA scenarios and monitor the update process.
5. Compliance: Ensure that the update process adheres to the Matter specification and CSA guidelines.

[keruhome]

Thank you for your reply.

We've already got VenderID from Alliance and created Vender info in TestNet DCL.

After that we try to set device info used for Vender ID in Google Developer Console, but we got the error which is shown as below. 

 

[eme_solution1]

Hi @jamesmartinsjte 

We are seeing exactly the same issue.

Our vendor ID is already assigned by CSA months ago. And we have registered in TestNet/MainNet last week.

We see the exact same error despite the vendor ID being valid.

Could you please help on this?