Smart Home quotas and limits

Google Home limits resource allocation and use and enforces appropriate quotas on a per-project basis. Specific policies vary depending on resource availability, user profile, service usage history, and other factors, and are subject to change without notice.

HomeGraph API limits

This section lists the rate limits for the Google Home Graph API. These limits apply to both the REST and RPC API.

Google applies the default limit of 6,000 requests per 60 seconds to the aggregate of your query, sync, delete, Report State, and asynchronous request sync API calls, on a per Cloud-to-cloud integration basis.

To request an increase in quota, reach out to ha-certification@google.com with the following information:

  • Email subject: Request to increase ReportState API Quota
  • Email content:
    • Project ID
    • Your company name
    • Current quota
    • Reason why you want to increase your quota
Quota Limit Can be increased
RequestSync (synchronous mode) Maximum of 1 concurrent request per agentUserId. No
RequestSync (asynchronous mode) Default limit of 6,000 requests per 60 seconds per Cloud-to-cloud integration. Yes
Query Default limit of 6,000 requests per 60 seconds per Cloud-to-cloud integration. Yes
Sync Default limit of 6,000 requests per 60 seconds per Cloud-to-cloud integration. Yes
Delete Default limit of 6,000 requests per 60 seconds per Cloud-to-cloud integration. Yes
ReportStateAndNotification Default limit of 6,000 requests per 60 seconds per Cloud-to-cloud integration. Yes

Debug quota issues

If your integration experiences rate limiting, use the following guidelines to diagnose and resolve quota issues:

  1. Google will rate limit API calls that exceed your quota. This negatively affects your integration by causing state mismatches. For example, if a ReportStateAndNotification request is dropped due to rate limiting, the physical device status will fail to sync, leaving the Google Home app (GHA) with outdated information.

  2. If RequestSync is the primary API experiencing errors, check that your service doesn't try to make more than one concurrent call per agentUserId.

  3. Review the growth of your traffic over time. If this growth is consistent with an increase in the number of devices, the launch of a new device type, or some other expected launch, request a quota increase. If this increase is unexpected, review your integration to determine if an unexpected change is causing more traffic to be sent to the Home Graph API.