> Documentation index: https://developers.home.google.com/apis/ios/automation/llms.txt

<br />

The Automation API supports most traits, but support for some attributes,
events, and commands in a trait may be limited.

In general:

- Any traits and types that you intend to use in your app with the Automation API must be registered at initialization. See [Home configuration](https://developers.home.google.com/apis/ios/initialize.md.txt#home_configuration).
- Any attribute may be used in starters or conditions.
- Cloud-to-cloud devices that don't report their state cannot be used as triggers in automations, created either manually or through discovery.
- Even if a device supports supports the traits listed here, a device may be
  blocked from use as a starter or action in the Automation API due to
  [Report State](https://developers.home.google.com/cloud-to-cloud/integration/report-state.md.txt)
  quality thresholds:

  - Devices with a Report State success rate lower than 90% are blocked from use as starters.
  - Devices with a command execution success rate lower than 95% are blocked from use as actions.

  Refer to this [list of device models](https://developers.home.google.com/automations/supported-devices.md.txt)
  and the specific starters and actions that they support for the
  Automations API.

  > [!NOTE]
  > **Note:** The Discovery API filters out devices that don't meet the Report State quality thresholds.

- Commands can only be used as actions.

- Some traits, such as
  [`AssistantBroadcastTrait`](https://developers.home.google.com/reference/swift/GoogleHomeTypes/Enums/Google/AssistantBroadcastTrait.md.txt)
  and [`NotificationTrait`](https://developers.home.google.com/reference/swift/GoogleHomeTypes/Enums/Google/NotificationTrait.md.txt),
  are only available for use in the Automation API.

- Some traits have prerequisites:

  - In order to use time-based starters such as [`Google.TimeTrait.ScheduledEvent`](https://developers.home.google.com/reference/swift/GoogleHomeTypes/Enums/Google/TimeTrait/ScheduledEvent.md.txt), [`Google.TimeTrait.RecurringClockTimeScheduledEvent`](https://developers.home.google.com/reference/swift/GoogleHomeTypes/Enums/Google/TimeTrait/RecurringClockTimeScheduledEvent.md.txt), or [`Google.TimeTrait.RecurringSolarTimeScheduledEvent`](https://developers.home.google.com/reference/swift/GoogleHomeTypes/Enums/Google/TimeTrait/RecurringSolarTimeScheduledEvent.md.txt), the structure in which the automation runs must have a street address to determine the local timezone and solar calculations. The address can be provided during structure creation or set in the [Google Home app (GHA)](https://play.google.com/store/apps/details?id=com.google.android.apps.chromecast.app). [Change Google
    home address](https://support.google.com/googlenest/answer/7551002) explains how a user can enter or update the structure address in the GHA. If the address is not set up, `createAutomation(_:)` saves and returns an `Automation` where `isValid == false`, with an `.unsupportedEntityEvent` validation issue containing `.missingStructureAddressSetup`.
  - In order for household members to receive notifications from [`Google.NotificationTrait.sendNotifications`](https://developers.home.google.com/reference/swift/GoogleHomeTypes/Enums/Google/NotificationTrait.md.txt#sendnotificationstitle:body:optinmemberemailsarray:), they must have the GHA installed with notifications enabled. Notifications are delivered to members through the GHA and cannot be sent directly to third-party apps.

Simplified versions of some traits are also available for use in automations.
For more information, see
[Simplified traits on iOS](https://developers.home.google.com/apis/ios/automation/simplified-traits.md.txt).