Message Error Codes

Last Updated on : 2023-10-07 07:47:48download

This topic provides information and solutions about the error codes that are generated when a message fails to push.

Error codes

If you do not find the error code or message you are looking for here, you can submit a ticket to request technical support.

Error codes	Description
16011001	The message is filtered out by the rule when it is pushed to the production environment.
16011002	The device is not in the project’s device pool.
16011003	The associated data center is suspended.
16011004	The message is filtered out by the rule when it is pushed to the test environment.

Error description

The message is filtered out by the rule when it is pushed to the production environment.
Cause

Three possible causes:
- Messaging rules are not enabled for the production environment.
- No messaging rules are set for the production environment.
- Messaging rules set for the production environment do not include the type of the failed message.
Solution

See Set up Messaging Rules and perform the following steps:
- Set the messaging rules that include the required message type.
- Enable the messaging rules for the production environment.

Error description

The device is not in the project’s device pool.
Cause

The device is not linked with your cloud project.
Solution

See Link Devices and link the device with your cloud project. You can link the device by device ID, product, your app, your WeChat mini program, Tuya app account, or SaaS.

Error description

The associated data center is suspended.
Cause

The message service for this data center is not enabled.
Solution

See Enable the Message Service. Change to the target data center and enable the message service.

Error description

The message is filtered out by the rule when it is pushed to the test environment.
Cause

Three possible causes:
- Messaging rules are not enabled for the test environment.
- No messaging rules are set for the test environment.
- Messaging rules set for the test environment do not include the type of the failed message.
Solution

See Perform a Message Test and perform the following steps:
- Set the messaging rules that include the type of the testing message.
- Enable the messaging rules for the test environment.
- Turn on the test environment and add a testing device.
To push the messages for the testing device to the production environment, remove this device from the test environment.