DescribeThingResponse

import type { DescribeThingResponse } from "https://aws-api.deno.dev/v0.3/services/iot.ts?docs=full";

The output from the DescribeThing operation.

interface DescribeThingResponse {

attributes?: {

[key: string]: string | null | undefined;

} | null;

billingGroupName?: string | null;

defaultClientId?: string | null;

thingArn?: string | null;

thingId?: string | null;

thingName?: string | null;

thingTypeName?: string | null;

version?: number | null;

}

§Properties

attributes?: {

[key: string]: string | null | undefined;

} | null

[src]

The thing attributes.

billingGroupName?: string | null

[src]

The name of the billing group the thing belongs to.

defaultClientId?: string | null

[src]

The default MQTT client ID. For a typical device, the thing name is also used as the default MQTT client ID. Although we don’t require a mapping between a thing's registry name and its use of MQTT client IDs, certificates, or shadow state, we recommend that you choose a thing name and use it as the MQTT client ID for the registry and the Device Shadow service.

This lets you better organize your IoT fleet without removing the flexibility of the underlying device certificate model or shadows.

thingArn?: string | null

[src]

The ARN of the thing to describe.

thingId?: string | null

[src]

The ID of the thing to describe.

thingName?: string | null

[src]

The name of the thing.

thingTypeName?: string | null

[src]

The thing type name.

version?: number | null

[src]

The current version of the thing record in the registry.

Note: To avoid unintentional changes to the information in the registry, you can pass the version information in the expectedVersion parameter of the UpdateThing and DeleteThing calls.