Matter OTA with Google Home – How to trigger or shorten OTA query interval (NCS 2.9.0)

RE: Matter OTA with Google Home – How to trigger or shorten OTA query interval (NCS 2.9.0)

AHaug — Wed, 11 Feb 2026 14:52:16 GMT

Noted, that makes sense. Thank you for elaborating. I will discuss this with the Matter team and see if they have some input to this

Kind regards,
Andreas

RE: Matter OTA with Google Home – How to trigger or shorten OTA query interval (NCS 2.9.0)

SunHuang — Wed, 11 Feb 2026 06:29:30 GMT

Thank you for the information. However, since my device is already a production-ready product, I cannot use CONFIG_CHIP_LIB_SHELL=y for validation, as the shell interface is disabled in production builds for security reasons.

My core objective is to understand the workflow in a real-world ecosystem. Once I upload the .ota image to the CSA Distributed Compliance Ledger (DCL) or the manufacturer's backend, how do mainstream Home Hubs (such as Apple TV, Google Nest, or Amazon Alexa) typically handle the update?

Specifically, I would like to clarify:

Polling Mechanism: Do these ecosystems (Apple/Google/Amazon) periodically send the AnnounceOTAProvider command or a QueryImage request to the device automatically?

Notification: Is there a standard latency or trigger that prompts the Home Hub to "realize" there is a new firmware version available on the network?

User Trigger: Does the user always have to manually check for updates in the respective App (Home, Google Home, Alexa), or is the "automatic query" you mentioned handled entirely by the Ecosystem Hub acting as the OTA Provider?

I need to ensure that our end-users receive firmware updates seamlessly through these major ecosystems without needing a CLI tool.

RE: Matter OTA with Google Home – How to trigger or shorten OTA query interval (NCS 2.9.0)

AHaug — Mon, 09 Feb 2026 13:59:43 GMT

Hi,

If you're using Matter shell, then you should be able to trigger an OTA through the command 'matter ota query' which is available with -DCONFIG_CHIP_LIB_SHELL=y. (See DFU over Matter)

Or, from the controller side (e.g., chip-tool), by sending an AnnounceOTAProvider command to the device: ./out/chiptool/chip-tool otasoftwareupdaterequestor announce-otaprovider 1 0 0 0 2 0

Once the device is made aware of the OTA Provider node, it “automatically queries the OTA Provider for a new firmware image.”

Not 100% sure if this is what you were looking for, but let me know if thats the case or not

Kind regards,
Andreas