Matter device data pipeline

[code_sparrow]

I'm device manufacturer and in future planning to get my device matter certified.

If I want my device data for analytics purpose into my cloud than what is the best way possible.

My research says that the most latest approach suggested by google is,

developing a custom mobile app using device access apis(Home APIs) and subscribe to device state and send it to my cloud.

If I go that route, will it work even though the device was onboarded via google home app and google home hub device is also there.

I want to make sure that both path will be active, device to hub to google home app and device to custom app to my cloud, and both on matter ecosystem.

Also is this https://developers.home.google.com/matter/analytics/monitoring#:~:text=To%20access%20Cloud%20Monitor... older approach and new one is google device access apis?

[Suc1 · Accepted solution]

Yes, both approaches can work simultaneously. The Google Device Access API (newer approach) allows you to build custom applications that can access device data directly, while still maintaining the Google Home integration. This dual-path architecture is supported within the Matter ecosystem.

For implementation details, I recommend:

1. Review the official Matter documentation: https://developers.home.google.com/matter
2. Explore Google's Device Access API: https://developers.google.com/nest/device-access
3. Consider using Google's Pub/Sub for streaming device data to your cloud

The link you shared does reference the monitoring approach, but the Device Access API offers more robust integration options for manufacturers.

[code_sparrow]

In case of custom app development, where device should connected to multiple matter ecosystem and custom app, do I need these both to develop the app where data can be fetched and commands can be sent?
1. https://developers.home.google.com/matter

2. https://developers.google.com/nest/device-access

If only one is fine than which one is the latest and may get updates from google in future.