Trigger Condition
Triggered when a device receives a command message, executes the command, and sends a receipt message back to the cloud.
Note: A clientid ending with "test" is a client test account; such clients do not trigger any message push
Receiving Method
Go to your IoT console to enable or disable message push
After configuration, you can receive device messages reported by the platform via either the HTTP interface or MQTT subscription (choose one)
You are currently receiving messages via HTTP; MQTT is recommended (lower latency).
In addition to subscribing to api/{AppId}/message/#,
you can also subscribe to this type of message separately via api/{AppId}/message/0.
Messages are pushed in real time and only once; if your server cannot be reached within 5 seconds, no further push is made.
When the response status is HTTP 1.1 200 OK (only the HTTP status is checked), the push is considered successful, so there is no return value requirement.
After configuration, you can receive device messages reported by the platform via either the HTTP interface or MQTT subscription (choose one)
You are currently receiving messages via HTTP; MQTT is recommended (lower latency).
If MQTT push is configured
The platform pushes messages to the specified MQTT topic.In addition to subscribing to api/{AppId}/message/#,
you can also subscribe to this type of message separately via api/{AppId}/message/0.
If HTTP push is configured
The platform pushes messages to the interface URL you configured.Messages are pushed in real time and only once; if your server cannot be reached within 5 seconds, no further push is made.
When the response status is HTTP 1.1 200 OK (only the HTTP status is checked), the push is considered successful, so there is no return value requirement.