Appearance
types/info.proto
Table of Contents
types/info.proto
ResourceSupport
ResourceSupport describes how a trait resource supports read/write/subscribe apis.
For sensor traits any write oriented properties should be and will be ignored.
Field | Type | Label | Description |
---|---|---|---|
readable | bool | Whether the device supports querying, i.e. get apis | |
writable | bool | Whether the device supports writable actions, i.e. update or action apis | |
observable | bool | Whether the device supports subscriptions, i.e. pull apis | |
writable_fields | google.protobuf.FieldMask | Which fields can be written to. Relative to the resource type, not the message (FooRequest) type. If this field is absent, the list of updatable fields is unknown, assume all. Check the response to your Update request for the values that were updated. An attempt to explicitly (via update_mask) write to a non-writable field will error. | |
pull_support | PullSupport | How Pull is implemented by the server | |
pull_poll | google.protobuf.Duration | If Pull is emulated, how often updates can be expected. This is not strict, updates may be less or more frequent. |
PullSupport
PullSupport describes how Pull methods are implemented by the server
Name | Number | Description |
---|---|---|
PULL_SUPPORT_UNSPECIFIED | 0 | How subscriptions are implemented is not known. |
PULL_SUPPORT_NATIVE | 1 | Subscribing is supported natively by the underlying system. |
PULL_SUPPORT_EMULATED | 2 | Subscribing is supported in the driver, rather than natively. Usually the driver will poll the system for data. |