Module aws_sdk_iotwireless::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that AWS IoT Wireless can respond with.
Structs§
ABP device object for LoRaWAN specification v1.0.x
ABP device object for LoRaWAN specification v1.1
The accuracy of the estimated position in meters. An empty value indicates that no position data is available. A value of ‘0.0’ value indicates that position data is available. This data corresponds to the position information that you specified instead of the position computed by solver.
LoRaWAN application configuration, which can be used to perform geolocation.
Beaconing parameters for configuring the wireless gateways.
CDMA local ID information, which corresponds to the local identification parameters of a CDMA cell.
CDMA object for network measurement reports.
CDMA (Code-division multiple access) object.
The cell towers that were used to perform the measurements.
List of sidewalk certificates.
Connection status event configuration object for enabling or disabling topic.
Connection status resource type event configuration object for enabling or disabling topic.
The device attestation key (DAK) information.
Describes a destination.
Describes a device profile.
Device registration state event configuration object for enabling and disabling relevant topics.
Device registration state resource type event configuration object for enabling or disabling topic.
The required list of dimensions for the metric.
The message in the downlink queue.
Event configuration object for a single resource.
Object of all event configurations and the status of the event topics.
List of FPort assigned for different LoRaWAN application packages to use
A FUOTA task.
Gateway list item object that specifies the frequency and list of gateways for which the downlink message should be sent.
Global identity information.
Global navigation satellite system (GNSS) object used for positioning.
GSM local ID information, which corresponds to the local identification parameters of a GSM cell.
GSM object for network measurement reports.
GSM object.
Information about a Sidewalk device that has been added to an import task.
Information about a wireless device that has been added to an import task.
IP address used for resolving device location.
Join event configuration object for enabling or disabling topic.
Join resource type event configuration object for enabling or disabling topic.
Object for LoRaWAN connection status resource type event configuration.
Object for LoRaWAN connection status resource type event configuration.
LoRaWAN object for create functions.
LoRaWAN device metatdata.
LoRaWANDeviceProfile object.
The LoRaWAN information used with a FUOTA task.
The LoRaWAN information returned from getting a FUOTA task.
LoRaWANGateway object.
LoRaWANGatewayCurrentVersion object.
LoRaWAN gateway metatdata.
LoRaWANGatewayVersion object.
LoRaWANGetServiceProfileInfo object.
Object for LoRaWAN join resource type event configuration.
Object for LoRaWAN join resource type event configuration.
LoRaWAN object for list functions.
The LoRaWAN information that is to be used with the multicast group.
The LoRaWAN information that is to be returned from getting multicast group information.
The metadata information of the LoRaWAN multicast group.
The LoRaWAN information used with the multicast session.
LoRaWAN public gateway metadata.
LoRaWAN router info.
LoRaWANServiceProfile object.
The LoRaWAN information used to start a FUOTA task.
LoRaWAN object for update functions.
LoRaWANUpdateGatewayTaskCreate object.
LoRaWANUpdateGatewayTaskEntry object.
LTE local identification (local ID) information.
LTE object for network measurement reports.
LTE object.
Message delivery status event configuration object for enabling and disabling relevant topics.
Message delivery status resource type event configuration object for enabling or disabling relevant topic.
The aggregated values of the metric.
A multicast group.
A multicast group that is associated with a FUOTA task.
Wireless metadata that is to be sent to multicast group.
Network analyzer configurations.
OTAA device object for v1.0.x
OTAA device object for v1.1
Specify the list of gateways to which you want to send downlink data traffic when the wireless device is running in class B or class C mode.
The wrapper for a position configuration.
The wrapper for position solver configurations.
The wrapper for position solver details.
The FPorts for the position information.
Proximity event configuration object for enabling and disabling relevant topics.
Proximity resource type event configuration object for enabling or disabling topic.
Information about the Semtech GNSS solver configuration.
Details of the Semtech GNSS solver object.
Information about a service profile.
Session keys for ABP v1.1
Session keys for ABP v1.1
Information about a Sidewalk account.
Information about a Sidewalk account.
Sidewalk object for creating a device profile.
Sidewalk object for creating a wireless device.
Sidewalk device object.
MetaData for Sidewalk device.
SidewalkEventNotificationConfigurations
object, which is the event configuration object for Sidewalk-related event topics.Gets information about a Sidewalk device profile.
Sidewalk-related information for devices in an import task that are being onboarded.
Sidewalk object used by list functions.
Sidewalk resource type event configuration object for enabling or disabling topic.
Information about a Sidewalk router.
Information about an import task created for an individual Sidewalk device.
Information about an import task created for bulk provisioning.
Sidewalk update.
Sidewalk object information for updating an import task.
The configuration of summary metrics.
The summary metric query object.
The result of the summary metrics aggregation operation.
A simple label consisting of a customer-defined key-value pair
TD-SCDMA local identification (local Id) information.
TD-SCDMA object for network measurement reports.
TD-SCDMA object.
Trace content for your wireless devices, gateways, and multicast groups.
ABP device object for LoRaWAN specification v1.0.x
ABP device object for LoRaWAN specification v1.1
Object for updating the FPorts information.
UpdateWirelessGatewayTaskCreate object.
UpdateWirelessGatewayTaskEntry object.
WCDMA local identification (local ID) information.
Network Measurement Reports.
WCDMA.
Wi-Fi access point.
The log options for a wireless device event and can be used to set log levels for a specific wireless device event.
Information about an import task for wireless devices.
The log options for wireless devices and can be used to set log levels for a specific type of wireless device.
Information about a wireless device's operation.
The log options for a wireless gateway event and can be used to set log levels for a specific wireless gateway event.
The log options for wireless gateways and can be used to set log levels for a specific type of wireless gateway.
Information about a wireless gateway's operation.
WirelessMetadata object.
Enums§
- When writing a match expression against
AggregationPeriod
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ApplicationConfigType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
BatteryLevel
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ConnectionStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DeviceProfileType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DeviceState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DimensionName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DlClass
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DownlinkMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Event
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EventNotificationPartnerType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EventNotificationResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EventNotificationTopicStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ExpressionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FuotaDeviceStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FuotaTaskStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
IdentifierType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ImportTaskStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
LogLevel
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
MessageType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
MetricName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
MetricQueryStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
MulticastFrameInfo
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
OnboardStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PartnerType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PositionConfigurationFec
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PositionConfigurationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PositionResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PositionSolverProvider
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PositionSolverType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PositioningConfigStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SigningAlg
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SummaryMetricConfigurationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SupportedRfRegion
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessDeviceEvent
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessDeviceFrameInfo
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessDeviceIdType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessDeviceSidewalkStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessDeviceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessGatewayEvent
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessGatewayIdType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessGatewayServiceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessGatewayTaskDefinitionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessGatewayTaskStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WirelessGatewayType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.