Appearance
Limitations
This page primarily outlines the usage limitations of certain resources within the platform.
Product Management
Item | Description | Limit |
---|---|---|
Product | Maximum number of products that can be created under a single account | |
TSL Model | Maximum number of TSL models that can be added under a product | 300 |
Maximum number of enumeration members for ENUM type properties | 100 | |
Maximum number of parameters for STRUCT type properties | 50 | |
Maximum length of TEXT type properties | 10240 characters | |
Maximum number of elements for ARRAY type properties | 100 | |
Maximum number of input parameters in a single service | 100 | |
Maximum number of output parameters in a single service | 100 | |
Maximum number of output parameters in a single event | 100 | |
Maximum total number of input and output parameters across all services and events | 300 |
Connectivity & Communication
Item | Description | Limit |
---|---|---|
Device Access | Using the same device information (same ProductKey and DeviceKey), only one connection to the IoT platform server is allowed at a time | |
Maximum number of connection requests per minute for a single device | 7 | |
Maximum message length for MQTT publication. Requests exceeding this size will be rejected | 64 KB | |
Maximum message length for CoAP publication. Requests exceeding this size will be rejected | 64 KB | |
MQTT connection heartbeat interval between the device and the platform | (1~600)*1.5 seconds | |
Sending frequency of MQTT heartbeat packet | Heartbeat packets are included in 30 messages/second/device upload limit | |
A device can only publish and subscribe to its own topics |
App Development
Item | Description | Limit |
---|---|---|
SMS | Frequency of sending SMS to the same phone number using the same signature | |
Frequency of calling SMS sending interface | ||
SMS verification code validity | 5 minutes | |
Verification code expires after use | ||
Frequency of calling email sending interface | ||
Email verification code validity | 5 minutes | |
Verification code expires after use | ||
End User | Frequency of calling user registration, login, and password reset interfaces | |
Account locked for 20 minutes after 5 incorrect login attempts; login disabled during the lock period | ||
End User Message | Earliest message time that can be queried | 90 days |
Device Binding | Maximum number of devices that can be bound per end user | 10,000 |
Device Sharing | Maximum number of end users a bound device can be shared with | 250 |
Home | Maximum number of homes/rooms an end user can create | 500 |
Group | Maximum number of groups a device can join | 5 |
Maximum number of devices in a group | 50 | |
Maximum number of groups an end user can create | 500 | |
Scene | Scene names cannot be duplicated in the same home | |
Maximum number of scenes an end user can create | 500 | |
Maximum number of actions in a scene | 50 | |
Earliest scene log time that can be queried | 6 months | |
Automation | Automation names cannot be duplicated in the same home | |
Maximum number of trigger conditions in an automation | 10 | |
Maximum number of actions in an automation | 50 | |
Maximum number of automations an end user can create | 500 | |
Automation trigger method | Edge-triggered | |
Automation trigger limit | ||
Earliest automation log time that can be queried | 6 months | |
App | Maximum number of apps an enterprise user can create | 500 |
SaaS Development
Item | Description | Limit |
---|---|---|
Client Subscription | After establishing the connection, the client must immediately send an authentication request. If authentication is not successful within 15 seconds, the AMQP server will actively close the connection | 15 seconds |
After the client establishes a connection with the IoT platform, if no frame communication occurs after the heartbeat cycle, the AMQP server will actively close the connection | Heartbeat cycle: 30 seconds~300 seconds | |
If the AMQP server forwards a message to the client and does not receive an acknowledgment message from the client within 300 seconds, it is considered an ACK timeout | 300 seconds | |
Connection Frequency | A consumer group can request connections no more than 100 times per minute | Limit the number of connection requests per Access Key to 100 per minute |
Push Rate | A single connection is rate-limited to 1000 TPS. You can expand capacity by adding more connections, with a maximum of 128 connections | |
Push Failure Caching Strategy | If a message cannot be consumed in real time due to offline clients or slow message consumption, it enters the backlog queue | |
Maximum message size that can accumulate in a consumption queue | 500 MB | |
Message retention time | 6 hours | |
Maximum number of queues and subscriptions a single account can create |