Trigger condition
When the user operation device (usually through the device operation panel / button) to report the device status to the cloud, it triggers.
Note: Client IDs ending with "test" are test accounts for clients, and messages will not be pushed to such clients.
Reception method
Please go to your IoT console to enable or disable message push notifications.
After configuration, you can receive device messages reported by the platform via either an HTTP interface or MQTT subscription (choose one).
You are currently receiving messages via HTTP. We recommend using MQTT instead, as it has lower latency.
Besides subscribing api/{AppId}/message/# Besides,
You can also subscribe to this message by api/{AppId}/message/0 separately.
Messages are pushed in real time and only once. If your server cannot be connected within 5 seconds, the message will no longer be pushed.
When the return status is HTTP 1.1 200 OK (only judging the HTTP status), the push is considered successful, so no return value is required.
After configuration, you can receive device messages reported by the platform via either an HTTP interface or MQTT subscription (choose one).
You are currently receiving messages via HTTP. We recommend using MQTT instead, as it has lower latency.
If MQTT push mode is configured
The platform will push messages to the specified MQTT topic.Besides subscribing api/{AppId}/message/# Besides,
You can also subscribe to this message by api/{AppId}/message/0 separately.
If HTTP-based push is configured
The platform will push messages to the interface URL you set.Messages are pushed in real time and only once. If your server cannot be connected within 5 seconds, the message will no longer be pushed.
When the return status is HTTP 1.1 200 OK (only judging the HTTP status), the push is considered successful, so no return value is required.