Home APIs Android SDK release notes

2025-01-07

  Home APIs Public Beta release  

This release contains bug fixes and enhances general availability (GA) quality for the Home APIs Android SDK, including improved support for Google Nest Audio and Google TV devices.

Minimum versions

• Google Play services min version: 24.45.34
• Google hub firmware min versions:
  • Cast version: 3.74.444798
  • Fuchsia min version: 22.20240805.103.161
• Android SDK: home.android.sdk_202411_EAP_1_0_1_RC00
• Google Home app (GHA) min version: works with any version
• androidx.core library min version: 1.10.0
• Matter version: 1.3.0.0
  • Note: Provisional Matter device types and clusters are not supported.

Known issues

• Switching the logged in Google Account may fail and result in an error.
  • Workaround: Re-run the permissions flow or restart the app.
• Google TV devices may not work for automations that use the MediaPlayback trait.
• In a structure that contains only a Google hub:
  • Matter devices may appear to be offline in the Google Home app (GHA).
  • Google Assistant cannot control Matter devices.
  • Smart displays cannot control Matter devices or display the state of any Matter device.
• For some devices, an app may not always reflect accurate state, and your app may report a state that is different from that reported by a Google app such as the Google Home app (GHA). This is usually due to devices not reporting state to Google.
  • Workaround: Checking state with a Google app resolves the mismatch.

Fixed known issues

• Commissioning may fail if the app is minimized during the process.
  • Workaround: Use the suppressHalfSheetNotification() API to suppress halfsheet notifications when the Commissioning API is used in your app.
• A server-side issue may prevent OkGoogle starters from working in automations.
• When using a hub running Fuchsia that doesn't have any Matter devices in the structure, if the hub is left idle for more than 3 hours, commissioning the first Matter device results in the Matter device being offline.
• After a factory data reset is performed for a hub, commands to newly-commissioned devices may fail despite the device being reported as online.