Last updated: 2022-03-11 18:29:12
Device Connection
|
Item
|
Description
|
Limit
|
|
Products
|
Maximum number of products that can be created under a single account
|
2,000
|
|
Devices
|
Maximum number of devices that can be added under a single product
|
1,000,000
|
|
Gateways and subdevices
|
Maximum number of subdevices that can be added under a single gateway
|
1,500
|
|
Device groups
|
Maximum number of parent groups and subgroups in total allowed for a single account
|
Unlimited
|
|
Maximum number of devices that can be added to a single group
|
Unlimited
|
|
Maximum number of groups that a single device can be added to
|
Unlimited
|
|
Remote configuration
|
Maximum size of the remote configuration file (supports JSON format only)
|
128KB
|
|
Cloud log
|
Storage period of cloud logs generated by device operations
|
7 days
|
|
File management
|
Maximum size of all files that can be stored in the IoT Hub server for a single account
|
1GB
|
|
Maximum number of files that can be stored for a single device
|
1,000
|
|
OTA update
|
Maximum size of a single update package file allowed
|
2,048 MB
|
|
Maximum number of devices that can be updated in a single batch update
|
100,000
|
Message Communication
|
Item
|
Description
|
Limit
|
|
Device connection
|
With the same device certificate information, only one connection can be established with the platform server concurrently.
|
Yes
|
|
Connection requests
|
Maximum number of MQTT connection requests per second allowed for a single device
|
1 request/5s
|
|
Device subscriptions
|
Maximum number of subscriptions allowed for a single device
|
Unlimited
|
|
Requests
|
Number of requests sent from the device side to the IoT Hub platform per second allowed for a single account
|
Unlimited
|
|
Number of requests sent from the IoT Hub platform to the device side per second allowed for a single account
|
Unlimited
|
|
Message communication
|
Maximum number of messages that a single device can report per second
|
30
|
|
Maximum number of messages that a single device can receive per second (subject to the network environment)
|
50
|
|
Bandwidth
|
Maximum throughput (bandwidth) per second allowed for a single connection
|
Unlimited
|
|
Message storage period
|
Maximum storage time of QoS1 messages
|
7 days
|
|
MQTT message size
|
Maximum size allowed for a single published MQTT message. If this limit is exceeded, the publish request will be rejected.
|
16KB
|
|
CoAP message size
|
Maximum size allowed for a single published CoAP message. If this limit is exceeded, the publish request will be rejected.
|
1KB
|
|
MQTT keepalive
|
MQTT connection heartbeat time. If the heartbeat time is not within this limit, the server will reject the connection request. |
900s
|
|
RRPC timeout period
|
Timeout period of device response to RRPC request
|
10s
|
|
Offline message
|
Number of offline messages
|
Up to 150 messages per device
|
|
Storage period of offline messages
|
Messages can be stored for up to 24 hours.
|
|
`KeepAlive` value
|
Value range of `KeepAlive`
|
0-900s
|
Topic
|
Item
|
Description
|
Limit
|
|
Custom topic classes
|
Maximum number of custom topic classes allowed for a single product |
100
|
|
Topic length
|
Maximum length of a topic allowed
|
255 UTF-8 encoded characters
|
|
Topic levels
|
Maximum number of hierarchical levels that can be contained in a topic, that is, maximum number of slashes in a topic |
10
|
|
Subscriptions
|
Maximum number of subscriptions allowed per subscribe request
|
1
|
|
Operation effective time
|
Effective time of a subscription or unsubscription operation
|
5s
|
|
Broadcast topic
|
Restrictions on the body of the message to broadcast
|
Max 8 KB. The original message must be converted into binary data and encoded with Base64 to generate the message body.
|
|
Message broadcasts by the server side to all devices per minute
|
A single product can perform only one task at a time.
|
Rule Engine
|
Item
|
Description
|
Limit
|
|
Rules
|
Maximum number of rules that can be set for a single account
|
1,000
|
|
Data forwarding destinations
|
Maximum number of data forwarding actions allowed in a rule
|
10
|
|
Messages processed by rule engine
|
The data processing capability of an account
|
Unlimited
|
|
Written message count
|
The data forwarding capability of an account when the performance of the target cloud product instance is sufficient
|
Unlimited
|
|
Requirements of data forwarding destinations
|
Data forwarding depends on the target product. Make sure that the instance of the target cloud product runs properly. Message forwarding fails in multiple scenarios. These scenarios include instance failure, overdue payments, parameter error, and configuration error.
|
The instance must run properly.
|
|
Message deduplication
|
When you forward a message, the message may be repeatedly sent until the client returns ACK or the message expires.
|
Unlimited. Each message has a unique ID.
|
Device Shadow and Server-Side Subscription
|
Item
|
Description
|
Limit
|
|
JSON levels
|
Maximum number of levels that can be specified in a device shadow JSON file
|
5
|
|
File size
|
Maximum size of a device shadow JSON file
|
16KB
|
|
Attributes
|
Maximum number of attributes that can be specified in a device shadow JSON file
|
Unlimited
|
|
Requests per second
|
Maximum number of requests per second per device |
Unlimited
|
|
Retry policy upon push failure
|
Due to the consumer client being disconnected and the slow consumption of messages, messages cannot be consumed in real time and instead enter the stacked queue. |
Unlimited
|
Yes
No
Was this page helpful?